Shift Workflow
Clock in/out, plate selection, vehicle assignment, earnings, status, and driver-specific controls.

4 HORSEMENDEVELOPMENT STUDIOS
INTERACTIVE AUTOMATION CASE STUDY
Alpha Mail is one of the projects that taught me how quickly a small Discord bot can grow into something a whole team depends on. This demo shows the driver, vehicle, dues, support, and management workflows I built around that idea.
THE PROBLEM
I originally built Alpha Mail for a FiveM roleplay courier company that already lived in Discord. Instead of asking everyone to learn another tool, I brought the repetitive management work into the place they were already using.
Clock in/out, plate selection, vehicle assignment, earnings, status, and driver-specific controls.
Managers could look up drivers, review earnings, handle dues, manage vehicles and teams, and pull the information they needed without digging through old messages.
Each driver had a consistent place to ask for help, while managers could keep support organized instead of losing issues in general chat.
The bot handled recurring dues reminders, unpaid reports, and other routine checks so managers did not have to remember every repetitive task themselves.
TRY IT
Switch between Driver, Manager, Owner, and Staff. Open channels, use controls, and move through the sample workflows. Everything below is fictional demo data; no live Discord server or production account is connected.
BEHIND THE BUILD
The biggest lesson from Alpha Mail was that the code was not the hard part. The hard part was understanding how people already worked, then making the bot fit that routine instead of making the routine fit the bot.
I built the original bot in Java with JDA and used Google Sheets for shared records. The technical pieces matter, but I tried to keep them invisible to the people actually using the bot.
This public showcase uses fictional names and sample values, so you can explore the workflow without exposing a live Discord server, private accounts, or production data.
READ THE DEVLOG ↗