Buy off-the-shelf when the software runs a process that works the same way at your shop as it does everywhere else, and build custom when the process is the thing that makes you money. That's the whole decision in one sentence. Everything below is just how to tell which side of that line you're standing on.
I build custom software for a living, so you'd expect me to tell you to build. I won't. Most of the tools you run should be off-the-shelf, and I'll say so to a prospect's face. The trick is knowing the handful of places where a subscription quietly costs you more than a build ever would.
Start with what the software actually touches
Forget features for a minute. Ask what the software touches and how weird your version of it is.
Accounting is accounting. Payroll is payroll. Email is email. These are solved problems, regulated, and identical across ten thousand businesses. Buy them. Nobody should be writing a custom general ledger, and if a vendor tries to sell you one, run.
Now look at the stuff in the middle of your business. How you turn a lead into a quote. How a quote becomes an order, an order becomes a build, a build becomes an invoice. How you split commissions across a dealer network. How you reconcile what your system says you have against what's actually on the yard. That middle layer is usually where a company is genuinely different from its competitors, and it's exactly where off-the-shelf software starts making you bend.
If a tool forces you to change how you do the thing you're good at, that's a cost. It just doesn't show up on the invoice.
The real cost of off-the-shelf isn't the subscription
Everybody compares the monthly SaaS fee to a build price and concludes the subscription is cheaper. That comparison is wrong because it leaves out the parts that actually hurt.
Here's what a subscription really costs you:
- The subscription, times every seat, forever, going up every renewal.
- The workarounds. The spreadsheet that lives next to the tool because the tool can't do the one thing. The double data entry. The person whose job is partly "babysit the software."
- The integration gap. Off-the-shelf tools don't talk to your other off-the-shelf tools. So somebody re-keys numbers from one system into another, and every re-key is an error waiting to happen. A big chunk of the custom work I do is an integration engine sitting between systems that were never designed to cooperate.
- The ceiling. When you need the tool to do something it doesn't, the answer is "submit a feature request" and wait, maybe forever. You don't own the roadmap. You're renting someone else's priorities.
A custom build flips that. Bigger cost up front, then it's yours. No per-seat tax as you grow. It does exactly your process because it was shaped around your process. And when the business changes, you change the software.
I've watched a business-management platform replace six subscriptions and four spreadsheets. The monthly SaaS spend it killed didn't pay for the build in month one. It paid for it over a couple of years and then just kept paying.
When off-the-shelf is the right call
Buy it when:
- The process is standard and you have no reason to do it differently.
- A mature product already exists with real support behind it.
- You need it working next week, not next quarter.
- The volume is low enough that manual workarounds don't hurt.
- It's not close to what makes your business yours.
If you're a 12-person operation and you need to send invoices, buy the invoicing tool. Don't call me. I'm serious. Spending a build budget to save fifty bucks a month is a bad trade, and any developer who tells you otherwise is selling you something.
When custom actually pays off
Build it when:
- Your process is a real competitive edge and the tools make you dumb it down.
- You're paying for three or four subscriptions that half-overlap and none of them fit.
- Your people are doing hours of manual work every week that a machine should do. Commission calculations are the classic one. If someone spends the last three days of every month in a spreadsheet splitting payouts across reps and dealers, that's not an accounting problem, it's an automation you don't have yet.
- Nothing on the market talks to your other systems, so you've become the integration layer, by hand.
- The off-the-shelf answer to your core question is a hard "no."
The pattern under all of these: the software is close to how you make money, and the friction is recurring. One-time annoyance, live with it. Weekly friction that scales with your growth, that's where a build earns its keep.
The honest middle ground
Most companies aren't all-or-nothing, and you shouldn't be either. Buy the commodities. Build the differentiator. Wire them together so they stop making each other's jobs harder.
Quote-to-cash is a good example. You don't need to build accounting. You need the thing that takes a customer from quote to signed order to production to invoice to be smooth and yours, then hand the clean numbers to whatever accounting package you already bought. Custom where it matters, off-the-shelf where it doesn't, an integration in between.
How to actually decide
Two questions cut through most of it. First: is this process standard, or is it mine? Second: does the friction happen once, or every week and getting worse as I grow? Standard and one-time means buy. Yours and recurring means build. Everything else is a judgment call, and that's fine.
If you're staring at a stack of subscriptions that don't fit and a spreadsheet holding it all together, that's usually the tell. I'll look at what you've got and tell you straight whether a build makes sense or whether you should keep your subscription and save your money. The quote's free either way.