Most firms should buy off-the-shelf software for most things. Email, accounting, document storage — these are solved problems, and building your own would be a waste. So the honest version of this question isn't "custom or off-the-shelf" in general. It's: for the thing that makes your firm your firm, which one costs less to run?
When off-the-shelf is the right call
- The process is generic — you do it much like everyone else, and being different would be a liability, not an advantage.
- A mature product already fits most of the need, and the gaps are minor.
- You value being able to start today over fitting perfectly.
If that's you for a given need, buy it. Don't let anyone talk you into building a worse version of a solved problem.
When you've outgrown it
The tension shows up when the tool is generic but your firm isn't. The signs are consistent across industries:
- Your real process lives in spreadsheets and people's heads, not the system you pay for.
- You run several tools that don't agree with each other, and someone reconciles them by hand.
- You can't see capacity, work-in-progress or margin without rebuilding a report each time.
- Growth means more workarounds, not less friction.
- The tool dictates how you work, rather than the other way around.
Off-the-shelf is cheap until you're paying for it twice — once in licence fees, and again in the workarounds it forces.
The comparison that actually matters
Compare total cost to run, not sticker price. Off-the-shelf wins the sticker every time because its build is spread across thousands of customers. But add the per-seat fees over several years, the hours lost to shadow spreadsheets and re-keying, and the opportunities you can't take because the tool won't bend — and for a firm whose structure is a genuine advantage, the total often favours custom sooner than expected. We break the money down in how much custom software costs.
A third option most people miss
It isn't all-or-nothing. The strongest setups keep off-the-shelf for the generic parts and build custom only for the part that is genuinely yours — with the two connected so data flows instead of being re-keyed. The way to get there without over-building is to model how the firm actually works first, then decide, entity by entity, what to buy and what to build. That's the whole idea behind building from an operating model.
So, should you build?
Build when the process is a source of advantage, when the generic tools have become a ceiling, and when you can articulate how your firm works precisely enough to engineer it. If that sounds like you, the best next step isn't a quote — it's mapping your model, which is also what tells you how much (if any) you actually need to build. See how this plays out in your industry.