You need software that solves a specific problem. You’ve looked at off-the-shelf options, and nothing fits quite right. Now you’re wondering whether to pay for something custom — or just make the existing tool work.

This is the build vs. buy question, and most of the advice out there is written for companies with a full IT department, a six-month runway, and a CTO who enjoys reading API documentation. That’s not most businesses. This post is for the owner or ops lead at a $1M–$20M business who needs to make a smart call, fast, without a dedicated dev team to back them up.

Here’s a plain-English framework for getting it right.

Start with the constraint, not the feature list

The mistake most SMBs make is comparing features first. You open five browser tabs, compare pricing tiers, watch demo videos, and try to figure out which product does the most. That process takes weeks and usually ends in a subscription you outgrow in a year.

Start here instead: what’s the actual constraint?

There are four common ones:

Time. You need something running in weeks, not months.
Budget. You have a real ceiling and you can’t absorb a failed experiment.
Fit. Your process is genuinely unusual and off-the-shelf tools keep forcing workarounds.
Integration. You already have systems in place and you need new software to connect to them.

Your constraint should drive the decision. If time is your binding limit, a SaaS tool you can configure in an afternoon beats a custom build every time — even if the custom build would be better in year two. If fit is your constraint, no amount of configuration is going to make a tool designed for a different type of business work cleanly for yours.

When off-the-shelf wins

Off-the-shelf software is the right call when your problem is common enough that someone has already solved it well. Scheduling, invoicing, basic CRM, email marketing — there are mature tools for all of these. Buying one means you get a proven product, ongoing updates, and a support team you can call.

Buy off-the-shelf when:

The problem is generic. If hundreds of businesses like yours need the same thing, the market has probably built it already.
You need it working immediately. Configuration takes hours or days. Custom software takes weeks.
Your process can flex. If you’re willing to adapt how your team works to match how the tool works, off-the-shelf is usually cheaper in total.
Volume is low. Paying $100/month for a tool you use lightly is almost always better than paying to build something custom.

The honest version: when a spreadsheet or an existing SaaS tool would solve your problem, that’s what we’ll tell you. Custom software isn’t the right call for every situation.

When custom wins

Custom software earns its cost when the problem is specific enough that generic tools keep leaving gaps — and those gaps are costing you real time or real money.

The clearest signal: you’re doing manual work to compensate for what the tool can’t do. If your team exports a CSV every morning and pastes it into another system, that’s a gap. If you’re managing a workaround spreadsheet alongside your “main” software, that’s a gap. If a new employee takes two weeks to learn all the exceptions in your process, that’s a gap that software can close.

Build custom when:

Your workflow is genuinely different. Not “we have our own terminology” different — actually different, with steps or logic that no generic tool handles cleanly.
You need two systems to talk to each other. A custom integration — which is just software that moves data between two existing tools without you touching it — is often cheaper than switching to a new platform.
You’re doing the same manual task every week. If your team runs the same report, sends the same emails, or copies the same data on a schedule, that’s automatable. The cost of building it is usually recovered in months.
Off-the-shelf has failed you before. If you’ve already tried two or three tools and they all needed workarounds, the problem isn’t you — it’s that your process doesn’t fit the product.

The three questions that cut through the noise

If you’re still stuck after reading the above, run your situation through these three questions.

1. What does it cost to keep doing this manually?

Add up real time. If two people spend three hours a week on a manual process, that’s six hours of labor every week. Over a year, that’s a meaningful cost — and it often surprises people when they actually calculate it. Compare that number to what custom software would cost to build. In many cases, the custom build pays for itself inside a year.

2. Would this tool still fit in two years?

Off-the-shelf tools are built for the average customer. If your business is growing or your process is evolving, a tool that fits today might be too rigid in 18 months. Custom software is scoped to fit your business now and can be extended as you grow.

3. What breaks if this doesn’t work?

If you pick the wrong tool, what’s the blast radius? If the answer is “we lose a few hours of productivity while we switch,” buy off-the-shelf and move on. If the answer is “our whole operations process stalls,” you want something built to spec.

What this looks like in real businesses

Sometimes the right answer is mostly off-the-shelf with a custom piece layered on top. That’s actually the most common pattern.

Take The Worxshop Athens, a coworking space in Athens, GA. Their core operations — bookings, billing, member management — ran on standard tools. The gap was lead generation: finding and reaching potential members was entirely manual, burning hours on Instagram, Facebook, and Google. The fix wasn’t replacing their whole stack. It was building a custom lead-gen pipeline that automated the specific task their existing tools couldn’t handle.

Bubble Bath Car & Cart Wash in Peachtree City had a different kind of gap. Customers were driving to the wash not knowing how busy it was, then leaving frustrated. No off-the-shelf app solved that specific problem cleanly for a single-location car wash. The answer was a custom website with a live bay-view feed — a narrow custom build that addressed the exact friction point.

In both cases, “build or buy” wasn’t an all-or-nothing question. It was “what specifically needs to be built, and what can we leave alone?”

The SMB constraint that changes the math

Here’s the one thing most build vs. buy frameworks ignore when they’re written for enterprise: you don’t have a dev team.

That changes the calculation in two ways.

First, “build” is only an option if you have a partner who builds it for you. If you’re evaluating this and thinking you’ll hire a freelancer off a job board and manage the project yourself, factor in that project management cost. It’s not zero.

Second, the ongoing maintenance question matters more for SMBs than it does for enterprises. Enterprise buys custom software and has an internal team to maintain it. You don’t. Make sure any custom software you commission includes a clear conversation about what happens when it needs updates — and who handles that.

When we build custom software at SetSoar, we build it as real software — not no-code workarounds that hit a wall when your business grows. And we stay in the conversation when things need to change.

The short version

Buy off-the-shelf when your problem is generic, your timeline is short, or your process can adapt. Build custom when your process has gaps that cost real time, when you need systems to connect, or when you’ve already tried the off-the-shelf route and it hasn’t worked.

The most expensive mistake is spending months trying to make the wrong tool fit instead of building the right one. The second most expensive mistake is commissioning custom software for a problem a $30/month SaaS tool already solves.

If you’re not sure which category your problem falls into, that’s exactly the kind of question worth bringing to a free 30-minute call. Book one at /contact and we’ll tell you honestly what we’d recommend — including if the answer is something you already own.

Build vs. Buy Software: A Decision Framework for SMBs Without an IT Department