Buy vs. Build: When Off-the-Shelf Software Stops Working for a Growing Business
Every business we've worked with started the same way: a spreadsheet, a generic accounting tool, maybe a free CRM. That's the right call early on — bespoke software for a five-person company is a solution looking for a problem. The question isn't whether to start generic. It's recognising the point where generic tooling starts actively costing you money, and most businesses notice it about two quarters after it started.
The signs you've outgrown generic tools
- Someone on your team has an unofficial job title: "the person who fixes the spreadsheet." If a single person's absence puts a process at risk, that process has outgrown its tool.
- You're running the same data through three systems by hand — sales in the POS, stock in a spreadsheet, invoices in a separate accounting tool — and reconciling them manually every month.
- Reports take a day to produce because someone has to pull, clean, and merge data from multiple exports before anyone can read them.
- You've added a "workaround" step to a process more than once. Workarounds are a business logic requirement your current tool can't express.
Buy, customise, or build: how to actually decide
This isn't a binary choice, and the right answer depends on how close a category-specific product gets you, not on company size alone.
- Buy a focused product (like a POS, payroll, or SACCO system) when your operation matches a well-understood category — restaurants, retail, payroll, member-based lending. Someone has already solved this problem well; paying for that is cheaper than re-solving it.
- Customise when a strong product gets you 80% of the way and the remaining 20% is genuinely specific to how you operate — not a preference, a real structural difference.
- Build custom when your operation doesn't match any existing category cleanly, or when the workflow itself is your competitive advantage and you can't afford for a competitor to buy the same system you're using.
The mistake to avoid in either direction
The expensive mistake isn't choosing "buy" or "build" — it's choosing without being honest about which one you actually need. Businesses that force a custom build for a problem a focused product already solves end up paying enterprise prices for something with a lower price tag and a faster timeline. Businesses that force a generic tool to do something structurally custom end up with the spreadsheet problem all over again, just inside a nicer interface.
We build both ends of this: focused products — Core POS, PayDesk, Sacco Suite, Astra ERP — for the operations that match a known category, and custom platforms for the ones that don't. The first conversation is always about which one you actually need, not which one we'd rather sell you.
Not sure which side of that line you're on? Talk it through with an engineer, not a salesperson.
Book a discovery call