Every few weeks we get the same email: “We’ve outgrown our tools. Should we build something custom?” It’s a good question, and the honest answer is usually not yet. But sometimes the answer is “yes, and you should have done it a year ago.”
This post is the framework we use in discovery calls to tell the difference. No sales pitch — if a $49/month tool solves your problem, we’ll tell you.
Start with the 90% rule
If an existing product does 90% of what you need, use it. The remaining 10% is almost never worth the cost of building and maintaining your own system. Off-the-shelf software comes with things you don’t see on the pricing page: years of bug fixes, security patches, mobile apps, integrations, documentation and a support team.
Custom software makes sense when the gap is bigger than that — when you’re spending real money and time fighting the tool rather than using it.
Add up the cost of your workarounds
The cost of “making do” is invisible because it’s spread across people and weeks. Make it visible. For one week, have your team note every time they:
- re-type the same information into a second system;
- export to a spreadsheet to do something the tool can’t;
- wait for someone else to do a step manually;
- apologise to a customer because two systems disagreed.
Multiply the hours by a loaded hourly rate, then by 50 weeks. We regularly see businesses spending the equivalent of a full-time salary on workarounds for a tool that costs $200 a month. At that point, custom software isn’t an expense — it’s the cheaper option.
Five signals that custom is the right call
1. Your process is your competitive advantage
If the way you work is why customers choose you, forcing it into a generic tool quietly erodes that advantage. A logistics company with an unusual dispatch model, a clinic with a specific intake flow, an agency with a distinctive delivery process — these are cases where the software should fit the business, not the other way round.
2. You’re paying for three tools to do one job
A CRM, a project tool and a billing app, stitched together with Zapier and hope. Each one is fine alone. Together they create gaps where leads, tasks and invoices fall through. One system designed around your actual workflow often replaces all three and the glue.
3. Your data is scattered and nobody trusts the numbers
When the sales figure in the CRM, the spreadsheet and the accounting system are all different, decisions get made on gut feel. A single source of truth is one of the most common — and most valuable — outcomes of custom software.
4. The tool is shaping decisions you’d rather make yourself
“We can’t offer that pricing because the platform doesn’t support it.” “We don’t take that kind of booking because the form can’t handle it.” If you’re saying no to customers because of software limits, the software is costing you revenue, not just time.
5. You’re about to scale
Workarounds that are tolerable at 5 staff become chaos at 25. If growth is on the horizon, fixing the foundation before the rush is far cheaper than during it.
Three signals that you should stay off-the-shelf
- The problem is common. Email marketing, accounting, HR, help desks — mature products exist and they are very good. Building your own is almost always a mistake.
- You haven’t tried configuring the tool properly. A surprising number of “we need custom” conversations end with us setting up the existing tool correctly in an afternoon.
- You can’t name the owner. Custom software needs someone inside the business who owns it — decides priorities, tests changes, trains the team. If nobody will own it, it will rot.
The middle path most people miss
It’s rarely all-or-nothing. The most cost-effective pattern we build is off-the-shelf at the edges, custom in the core: keep HubSpot or Xero or Shopify for what they do well, and build a custom layer in the middle — an operations app, a customer portal, an automation engine — that connects them and handles the parts that are uniquely yours.
You get mature tools where it doesn’t matter and a perfect fit where it does, at a fraction of the cost of replacing everything.
How to decide this week
- Write down the three most painful things your current tools can’t do.
- Estimate the weekly hours lost to workarounds for each (be honest).
- Check whether a configuration change or a different tool solves any of them.
- For what’s left, ask: is this a unique-to-us problem or a common one?
- If it’s unique and expensive, that’s a custom software conversation worth having.
If you’d like a second opinion on where you land, tell us about your setup. We’ll give you a straight answer — including “don’t build this” when that’s the right one.