Every studio has an incentive to say your process is special. Most processes are not, and the honest answer costs the studio a project. Here is how we decide, and you can run it yourself before making any calls.
The test
Write down the three things that make your business better than its competitors. Now ask, for each: does the software touch it?
If your advantage is a relationship, a location, a licence or a price, then software is plumbing. Buy the boxed product, accept its assumptions, and spend the difference on the thing that actually wins you work.
If your advantage is *how* something gets done — a routing rule nobody else has, a way of matching supply and demand, a production sequence built over fifteen years — then the boxed product will fight you on exactly that, every day, forever.
Three cases where buying wins
Accounting, payroll, email. Regulated, commoditised, and someone else keeps up with the law changes. Building here is a hobby.
A process you are willing to change. If adopting the tool's way of working would be fine, or even an improvement, that is the cheapest project available: no build, no maintenance, and someone else's roadmap.
Anything you cannot describe yet. If nobody can write down the rules, nobody can build them. A spreadsheet is a legitimate way to discover what the rules are, and enormously cheaper than discovering them in code.
Where buying quietly fails
The failure mode is not dramatic. Nothing crashes. Instead the workarounds accumulate: an export into a spreadsheet, a status kept in a chat, a person who "just knows" which orders to check. Six months later the real system is the workaround and the software is a filing cabinet nobody trusts.
The tell is measurable. Count the hours per week your team spends moving data between systems, and the number of decisions made from a spreadsheet rather than from the software. When that becomes a job's worth of time, the boxed product has stopped being the cheap option.
The middle path most people miss
It is rarely all or nothing. The shape that usually works: keep the boxed product for the commodity parts, build one small system for the part that is genuinely yours, and connect them. Far smaller than replacing everything, and it puts the custom work exactly where it earns its cost. That small system is exactly the size we build first: one journey, eight weeks, $16,000, connected to whatever you keep. Two shapes of it come up often enough to be priced on their own: a CRM built around your pipeline when the part that does not fit is how you sell, and a client portal when it is what your customers keep emailing you for.
The question before this one: why two studios quote the same project three times apart.