Software advice for small shops usually arrives in two equally wrong extremes: “get the most complete one, might as well” (then drown), or “a small shop just needs a notebook” (then grow without a foundation). The middle path isn’t a compromise — it’s an order: the right feature at the right phase.
Phase 1 — The only must-have: repair flow + receipts
For a one-or-two-person shop, 80% of a system’s value sits in one flow: units recorded on intake → clear statuses → tidy receipts with tracking codes → handover with a written warranty. That flow erases the most expensive small-scale problems: forgotten units, vanished receipts, warranty debates.
The pleasant part: this phase is also the cheapest — in Automan, this core flow lives on the free tier (Lite), not a trial, and covers the repair shop’s core workflow (details and limits on the pricing page). A small shop shouldn’t pay for needs that haven’t arrived.
Phase 2 — When parts become serious money: stock
The sign is unmistakable: you start stocking parts (instead of buying per job) and start wondering “how much money is sitting on that shelf?” That’s when stock and purchasing deserve records: stock cards, per-purchase costs, and repair-consumed parts deducting from stock. Before that sign appears, forcing full inventory management just adds work.
Phase 3 — When a second person arrives: accounts & roles
The moment someone besides you touches the app, two things must switch on: accounts per person and right-sized roles. This isn’t a “big shop feature” — small shops making their first hire are the most vulnerable, because trust is still being calibrated. Clear trails protect both directions from employee number one.
Phase 4 onward — following needs, not the catalog
Automatic WhatsApp when customers start asking for status; promos & points when repeat business gets competitive; commissions when a commissioned technician joins; accounting when a bank or the tax office asks. The pattern never changes: the need shows up first, then the module gets enabled.
Why this order beats brand-shopping
Because what kills software adoption in small shops isn’t picking the wrong brand — it’s front-loading the burden. Any system forced whole onto a two-person shop feels bloated; a system started from one flow feels helpful on day one.
There’s just one condition — and it’s your real selection criterion: make sure the system you start small with has its continuation in the same place, so a growing shop isn’t punished with an app switch. The full comparison lives in simple app vs operations system.
Start phase 1 today — the first 30 minutes — and let the later phases arrive when their time comes.