When to build custom software (and when not to)
Short answer
Buy off-the-shelf when your problem is common and the software mostly fits — you'll get there faster and cheaper, and someone else maintains it. Build custom when the way you work is the thing that makes you money, when no tool fits without ugly workarounds, or when the ongoing cost and lock-in of stitching tools together has quietly grown larger than a focused build. Most businesses should buy first and build only where they've clearly outgrown buying.
Start by assuming you should buy
This is not what a software studio is supposed to tell you, but it's true: for most problems, off-the-shelf software is the right answer. Accounting, scheduling, email, payments, basic CRM — these are solved problems. Someone has already built a good tool, fixed the bugs, and will keep maintaining it for less than you'd spend building your own.
If a category tool fits your work with only minor compromises, buy it. Building custom to save a few clicks is how businesses end up owning software they now have to maintain forever. The honest default is: buy, unless you can clearly articulate why buying fails.
The signs you've actually outgrown off-the-shelf
Buying stops being the right answer when specific, recognizable symptoms show up. Not one of these alone — but when several stack up, a build starts to pay for itself:
- You pay for five tools that don't talk to each other, and a person spends their day carrying data between them.
- Your team runs on a spreadsheet with a dozen tabs that only one person understands — that spreadsheet is already your custom software, just fragile and un-owned.
- You're paying per-seat for features you don't use, and the price climbs every time you add a person.
- The way you deliver your work — the exact sequence that wins you business — doesn't fit any tool, so everyone works around the tool instead of with it.
- You keep asking a vendor for a feature and waiting. Their roadmap isn't your roadmap.
- "Shadow IT" has appeared: glue scripts, manual exports, copy-paste rituals people invented to make the tools cooperate.
The tell
If the way you work is what makes you money, and no tool lets you work that way without a pile of workarounds, that's the strongest case for custom. You're not buying software — you're removing the tax you pay every day to make generic tools behave.
The option most people miss: don't rebuild, connect
Build-vs-buy is a false binary. The highest-value work is often neither — it's a small amount of custom software that sits between the tools you already pay for and makes them behave like one system. You keep your CRM, your accounting, your scheduling. You add the connective tissue that carries the right information between them automatically.
This is usually cheaper than a full custom build, faster to deliver, and lower-risk than ripping out tools your team already knows. It's also where the biggest daily friction actually lives.
What custom really costs (the part vendors skip)
Custom software is not a one-time purchase. It's something you now own. That means it needs an owner, occasional changes when your business changes, and someone to call when something breaks. Any honest partner will price the life of the thing, not just the build.
The flip side: off-the-shelf has hidden ongoing costs too — per-seat pricing that scales with your growth, the labor of working around its gaps, and the risk that the vendor changes direction, raises prices, or shuts down. "Buy" isn't free of ownership cost; it's just someone else's ownership, rented to you.
How to make the call
Decide problem by problem, not all at once. For each painful area, ask honestly which column it belongs in:
- Name the problemone area at a time
- Is it common?does a good tool exist?
- Does a tool fit?without workarounds
- Buy itcommodity work
- Connect what you havethe middle path
- Build only what's yoursyour advantage
Run each painful area through this. Most businesses land on a mix: buy the commodity, connect the tools, build only the part that's genuinely theirs.
Making the call
Off-the-shelf is the right answer when…
- The problem is common and well-solved (accounting, scheduling, payments).
- A category tool fits with only minor compromises.
- You need it working in days, not months.
- You don't want to own maintenance, security, or uptime.
- The process isn't a competitive advantage — it just needs to work.
Custom (or connective) software earns its cost when…
- The way you work is the thing that makes you money.
- No tool fits without a pile of daily workarounds.
- You're paying for several tools a person manually keeps in sync.
- Per-seat pricing now costs more than a focused build would.
- You're stuck waiting on a vendor's roadmap for something core.
Questions people ask
How much does custom software cost for a small business?
There's no honest single number — it depends entirely on scope, and anyone who quotes a figure before understanding your problem is guessing. What matters more than the sticker price is the shape of the cost: a focused build that connects tools you already use is a fraction of a full ground-up system, and both carry ongoing ownership cost. A good partner will scope the smallest version that solves the real problem, not the biggest one they can sell.
Isn't building custom software risky compared to buying?
It can be, which is exactly why you should build narrowly and only where buying has clearly failed. The lowest-risk path is usually to keep your existing off-the-shelf tools and add a small, focused piece of custom software between them, rather than replacing everything at once. Risk comes from scope, not from the word "custom."
How do I know if we've outgrown our current tools?
Look for the symptoms: paying for tools that don't talk to each other, a person whose job is moving data between systems, a critical spreadsheet only one person understands, per-seat costs climbing faster than value, or waiting on a vendor's roadmap for something central to how you work. When several of those stack up, you've outgrown buying for that specific area.
Related reading
Not sure which of these applies to you?
That's exactly what a Business Technology Review is for. Tell us how your business actually works, and we'll find where technology could remove friction or unnecessary work — and, just as often, where it shouldn't. A clear recommendation, not a sales pitch.
Written by Artifex Labs · Last reviewed August 13, 2026