What Shipping My First SaaS Solo Actually Taught Me

Before ShiftMate, TFLYX was websites and video edits — real work, but work I was doing for other people's businesses. ShiftMate was the first time I built something that was entirely mine to be wrong about. No client brief to hide behind. If the product didn't work, that was on me.

The scope problem nobody warns you about

The hardest early decision wasn't the algorithm or the design — it was what to leave out. A roster tool could reasonably grow into payroll, time tracking, HR compliance, messaging, a dozen other adjacent problems. Every one of those is a legitimate feature. None of them were the reason ShiftMate needed to exist. The discipline was staying focused on one job — build the roster, get it to the team, fairly — and resisting the pull to build a bigger, vaguer product that solved everything a little.

Everything you need to run your roster. Nothing you don't.

That line ended up on the site because it's the actual design principle, not just good copy. No bloat, no complexity most small teams will never touch.

Building for people who will never read a changelog

Client website work teaches you to think about one audience: the business owner paying the invoice. Building ShiftMate meant designing for two audiences at once — the owner setting up the roster, and the staff member who just wants to know their Tuesday shift without downloading anything. That second audience never logs in, never sees a settings page, and has zero patience for friction. One-click Excel export and copy-paste messages exist because of that second audience, not the first.

What actually changed after it went live

• ■Support requests are a different kind of pressure than client feedback — a client project has an end date; a live product has users depending on it every single week, indefinitely.
• ■Pricing a SaaS is a different problem than pricing a website. A website is a fixed scope you deliver once. A subscription has to keep earning its cost every single month, for as long as the customer stays.
• ■"Done" stopped being a real state. A website project ships and is finished. A product never really is — it's a series of decisions about what to fix, build or leave alone next.

Why this mattered beyond the product itself

Shipping ShiftMate solo is what makes "software shipped solo" a fact about TFLYX instead of a slogan. It's also what changed how I scope client website work — every TFLYX build now gets asked the same question ShiftMate forced on me: what's the one job this actually has to do well, and what's just scope creep dressed up as ambition.