Custom software vs. off-the-shelf: how to actually decide

Somebody builds custom software for a living should probably tell you custom is always the answer. It isn’t, and pretending otherwise is how you end up with a $40,000 tool that does what a $30-a-month subscription would have done.

But the opposite mistake is just as expensive and much more common: renting software that half fits, forever, and slowly bending your business around its opinions. So here’s the honest version of the build-vs-buy decision — including the cases where I’d tell you not to hire anyone like me.

When off-the-shelf wins, full stop

Some problems are the same for every business on earth. Accounting. Payroll. Email. Calendars. Document storage. These are solved problems, polished by decades of competition, wrapped in compliance rules you don’t want to own. Nobody should ever build their own QuickBooks, and anyone who offers to is a red flag all by themselves.

The test: if your version of the problem is the same as a million other businesses’ version, buy the thing. You get years of other people’s bug fixes for a monthly fee, and the vendor’s roadmap mostly points where you’re going anyway.

Off-the-shelf also wins when you’re still figuring out what you do. A new business changing its process every month shouldn’t freeze that process in custom code. Rent something cheap, learn what you actually need, build later — if it turns out you need to at all.

When custom starts winning

Custom earns its keep when the workflow is your business — the thing you do differently that makes customers pick you. Squeezing that into generic software means sanding off the exact edge you compete on.

You can usually feel this one before you can articulate it. The tells:

Your team says “we do it that way because the software makes us.” That’s backwards, and everyone knows it’s backwards, and it costs you a little every day.

Somebody exports to a spreadsheet and “fixes it up” before the real work happens. That spreadsheet is a custom tool — an unpaid, fragile one that lives in one person’s head.

You’re paying for three subscriptions that each do 80% of a job, plus the manual work of carrying data between them. The duct tape has become a part-time job.

The seat math stopped making sense. I ran the numbers on this in the cost post — a per-user subscription across a growing team quietly turns into custom-software money every few years, paid forever, for something you’ll never own.

The answer nobody sells: both

The framing of “custom vs. off-the-shelf” suggests you pick a side. Almost nobody should. The businesses that get this right buy the commodity and build the difference.

Keep the accounting package. Keep the email. Then build the small, specific tool that connects them to how you actually work — the quoting system that knows your pricing logic, the job tracker that matches how your crew really operates, the glue that moves data between subscriptions so a human doesn’t have to.

Some of the most useful projects I take on are exactly this: not replacing off-the-shelf software, just fixing the seams between it. Small builds, cheaper than people expect, and they pay for themselves in un-duct-taped hours.

The one question that decides it

Strip everything above down and the decision comes to this: is this workflow the same as everyone else’s, or is it yours?

Same as everyone else’s — buy it, and buy the boring market leader, not the clever newcomer.

Yours — that’s when custom deserves a look. Not “digitize the whole business,” just the one workflow where the fit matters most. Scope it small, get a real number, and compare it to three years of subscription-plus-workarounds instead of one month.

If you’re not sure which side of the line your workflow sits on, ask me and describe it. Sometimes the answer is a build. A good chunk of the time the answer is “the software you want exists, here’s its name” — which costs you nothing and tells you what kind of company you’re talking to.