I Didn't Build ShiftMate to Get Rich. I Built It Because Rosters Made Me Furious.

Nobody starts building a scheduling tool because they dream of scheduling tools. You start because something specific and unglamorous kept going wrong, over and over, and eventually the irritation outweighs the effort of fixing it properly instead of just living with it.

For me it was the gap between how simple a roster sounds and how much quiet chaos it actually produces — a spreadsheet edited by whoever's free that day, a WhatsApp message that gets buried under forty other messages, someone finding out about a shift change an hour before it starts. None of that is dramatic. All of it is exhausting in the specific way that only repetitive, avoidable friction is.

Why "just use a spreadsheet" never sat right

A spreadsheet works fine right up until it doesn't — until someone's on leave and gets scheduled anyway, until the same person closes five nights running because nobody was tracking the pattern, until the file that got shared last week wasn't actually the final version. Small errors, individually forgivable. Compounding weekly, they're the reason scheduling has a reputation for being a headache nobody wants to own.

Built by one person who got tired of building rosters by hand.

That's the honest origin story, not a polished founder-myth version of it. I wasn't chasing a market opportunity when I started — I was chasing the end of a specific annoyance, and it turned out enough other people shared it that the annoyance was worth solving properly.

What kept it going after the irritation faded

• ■Seeing the fairness score catch an imbalance I would have missed manually — that's when it stopped feeling like a side project and started feeling like a real tool.
• ■Realising staff never had to download anything to get their schedule — that constraint forced better design decisions than convenience would have.
• ■Getting the first message from someone who wasn't me, using it for their actual team, for a problem I'd only ever solved for myself before.

Getting rich was never the starting engine. Getting the roster to stop being a weekly source of low-grade dread was. If it makes money along the way — and it is, slowly, honestly, without outside funding — that's the result of solving the actual problem well, not the reason I started solving it.