“Should we build something custom?” is one of the most expensive questions a growing business can get wrong. Build too early and you take on software you now have to maintain forever. Buy when you should have built, and you spend years forcing your operation to fit a tool that was never designed for it. The honest answer is that custom software is the right call far less often than vendors suggest — and when it is right, it’s worth far more than the quote.
Start by assuming you should buy
For most needs, an established product exists, is cheaper than building, and is maintained by someone else. Accounting, email, payroll, basic CRM, e-commerce, scheduling — these are solved problems with mature, competitive tools. Building your own version of a commodity is almost always a mistake: you inherit all the cost and none of the economies of scale.
So the useful question isn’t “could we build this?” — you almost always could. It’s “is this one of the few things where building is genuinely better than buying?”
The four signals that building might be right
Custom software tends to pay off when several of these are true at once:
- The workflow is your actual advantage. If the way you operate is part of why customers choose you, forcing it into a generic tool can erode the very thing that works.
- No product fits without painful compromise. You’ve genuinely looked, and every option needs heavy customisation, manual workarounds, or three tools stitched together.
- The cost of the current friction is real and recurring.Hours lost every week, errors that reach customers, decisions made blind because no one can see the data. You can describe it in specifics, not frustration.
- You’ll still want it in three years. The need is structural, not a temporary gap a vendor will close in their next release.
One signal on its own usually isn’t enough. Several together is a strong case.
Count the whole cost, not just the build
The quote to build is the smallest number in the conversation. Custom software also carries hosting, maintenance, security updates, the occasional fix, and the eventual change when your business moves on. A responsible estimate includes the cost of owning the thing, not just creating it. If a project only makes sense when you ignore its running cost, it doesn’t make sense.
The middle path most people miss
Build-versus-buy is rarely all-or-nothing. Often the best answer is to buy the commodity parts and build only the thin layer that’s genuinely yours — the integration that connects your tools, the dashboard that finally shows the whole picture, the one workflow no product handles well. This keeps your maintenance surface small while still fixing the real problem.
A simple way to decide
Before committing to custom work, you should be able to answer, in plain terms:
- What specific friction are we removing, and what does it cost us now?
- What have we tried to buy, and exactly where did it fall short?
- Who will own and use this once it’s live?
- Can we afford to maintain it, not just build it?
- What’s the smallest version that would prove this is worth it?
If those answers are clear, custom software can be one of the best investments a business makes. If they’re vague, that’s not a reason to rush — it’s a reason to spend a little more time understanding the problem first. That understanding is where we’d start too.