Almost every growing business hits the same fork: the off-the-shelf tool you started with no longer fits how you actually work, and someone floats the idea of building something custom. Both directions can be right. Both can also quietly cost you a year and a budget you never planned to spend.
This is the framework we use with clients before a line of code is written. It is deliberately unromantic — the goal is to make the cheaper, more reversible decision until the evidence says otherwise.
Start by assuming you should buy
Off-the-shelf software is the default for a reason: someone else already paid to build it, maintains it, secures it, and supports it, and you split that cost with thousands of other customers. For anything that is not a genuine competitive differentiator — accounting, email, payroll, CRM, scheduling — buying is almost always the right call.
The mistake here is not buying too much; it is buying too many disconnected tools and then paying people to move data between them by hand. If your pain is 'we have six tools that don't talk to each other,' the answer is usually integration, not a from-scratch rebuild.
Build when the process is the product
Custom software earns its cost when the workflow itself is how you win — when the way you quote, route, price, fulfil, or report is a real advantage over competitors, and no vendor models it the way you do. Bending your best process to fit a generic tool is where you leak the advantage.
The second strong case is leverage: a repetitive, high-volume task that a purpose-built tool or an automated agent can absorb, freeing senior people for work only they can do. If you can name the hours it saves each week, the build has a defensible payback.
The costs nobody quotes you
The build price is the smallest number in the room. Custom software has to be hosted, monitored, patched, and evolved as the business changes — a total cost of ownership that runs for as long as the software lives. A quote that ignores maintenance is not a real quote.
Off-the-shelf has its own hidden bill: per-seat pricing that scales faster than headcount, the switching cost when you outgrow it, and the data you can't easily get back out. Compare the five-year picture, not the sticker.
A cheaper middle path usually exists
Most 'we need to build' conversations resolve into something smaller: a thin custom layer over tools you already pay for, an integration that removes manual re-keying, or a single automated workflow. These ship in weeks, not quarters, and they are reversible if you are wrong.
Prove the value with the small version first. If the thin layer is heavily used and the constraints are real, you have earned the case for the larger build — and you will scope it far more accurately for having lived with the small one.
How to decide in one sitting
Write down the workflow. If a credible off-the-shelf tool models it within about eighty percent, buy and adapt. If the missing twenty percent is exactly the part that makes you money, build that part and buy the rest. If you cannot describe the workflow precisely, you are not ready to build anything yet — that clarity is the first deliverable, and it is cheap.
We do this scoping as the first step of every engagement, and we will tell you to buy off-the-shelf when that is the honest answer — we would rather earn the build you actually need than sell you one you don't.