Build vs. buy: when off-the-shelf stops fitting your business
We turn down build work regularly
Often by telling people to stay on the platform they’re already using. Custom software is a commitment: it needs maintenance, it needs someone to own it, and it competes for attention with the actual business.
The bar for crossing that line should be high. These are the four signals we look for — and ordinary friction with a tool is not one of them.
Signal one: you’re paying for overlap
Count the subscriptions that each solve part of one workflow. When four tools plus a person with a spreadsheet are needed to complete a single process, you’re already paying for custom software.
You’re just paying in fees and hours instead of engineering, with none of the ownership and none of the fit.
Signal two: the platform charges you for your own model
Per-transaction fees on a business model the platform never anticipated, or per-seat pricing that punishes the exact growth you’re chasing.
Model both curves at three times your current volume. If the lines cross inside eighteen months, building starts being the cheaper option rather than the ambitious one.
Signal three: your differentiator lives inside the tool
If the thing customers choose you for lives inside software you rent, you’re renting your moat. That’s the strongest argument for building there is.
The inverse is just as useful: if a workflow isn’t differentiating, it’s the strongest argument for continuing to buy. Nobody wins by building their own payroll.
Signal four: the workaround has become the process
When new staff are trained on the workaround rather than the tool, the tool has stopped being the system of record.
That’s usually the point where data quality quietly collapses and reporting becomes fiction — expensive, and invisible until a decision gets made on bad numbers.
The middle path most people miss
Build vs buy isn’t binary. The best answer is often to keep buying the commodity parts — email, accounting, payments — and build only the thin layer where your business is genuinely different, integrated with the rest.
That’s a fraction of the cost of a platform replacement, and it’s most of the work we do.
Weighing a build-vs-buy decision? See API & systems integration for the thin-layer approach, or start a conversation.
Tags
About the Author
Next Mountain Development
A contributor to this blog.