Build vs Buy Software: How to Decide

The short answer

Should you build or buy software?

Buy off-the-shelf for generic, commodity needs. Build custom when your business has real nuance that packaged tools force you to work around. I used to say buy at 80% fit. I'm a lot more skeptical of that now.

Buy off-the-shelf software for generic, commodity needs. Build custom when your business has real nuance that off-the-shelf tools force you to work around.

That is not the answer I used to give. For years, I told owners, “If off-the-shelf covers 80% or more of what your business actually needs, use it.” I wrote that the default is off-the-shelf, and I told businesses in commoditized fields to buy and move on. I’m a lot more skeptical of that advice now, because that last 20% is usually the part that makes your business yours.

I’m Robert Kehoe, Founder & CEO of Active Logic, a 100% U.S.-based custom software company with 200+ projects delivered since 2014. I run a company that builds custom software, so weigh what I say here with that in mind. I will also tell you where buying is the right call, because there are plenty of places it is.

What does build vs buy software mean?

Build vs buy software is the choice between licensing a packaged product that many companies use the same way, and having software built around how your company works, which you own. Off-the-shelf usually means a subscription product. Custom means software designed for your workflows, your rules and the way you serve your customers. There is also a middle path: keep the packaged tools you like and build the custom layer that connects them.

If you want the longer definition first, start with what custom software is.

When is off-the-shelf software the right call?

Buy when the need is generic. “Off-the-shelf software is great for generic businesses. If you run a dog walking business, buy the dog walking app.” When most companies in a field do the work the same way, someone has already built a product for it, and paying a subscription is the sensible move.

The same goes for generic functions inside a business that is anything but generic. Accounting is the clearest example. Tax and reporting rules shape that process far more than your own preferences do, and we run our own books on packaged accounting software.

Off-the-shelf is probably right when all of these are true:

  • Your team uses the product the way it was designed, without side processes to fill gaps.
  • Nothing about how you do this work is why customers pick you.
  • You would not need heavy customization to make it fit.
  • You can export your data if you ever leave.

When should you build custom software?

Build when the business has real nuance. “The second your business has real nuance to it, custom is the better way to go. 100%,” is how I put it now. Any business with nuance should have custom software, almost 100% of the time.

Nuance means the parts of the operation that differ from your competitors and carry real money: how you quote, price, schedule, produce, deliver or serve. Software should adapt to the business, not the other way around. When a packaged product forces you to mold the business around it, you are paying for software that is working against the thing that sets you apart.

Industry is the wrong test. We have seen two businesses in the same landscaping trade land on opposite answers. One ran a standard, single-market service operation that packaged scheduling and invoicing tools covered well. The other ran a franchise model with non-standard service tiers and pricing that varied by region. It had been held together with three separate subscription tools, a homegrown tracking layer and an automation that broke quietly. We built them a custom operations platform that replaced that patchwork. Same industry, different process, different answer.

The harder part is that people who have worked inside the same software for years often cannot see the nuance anymore. “They’ve been working in the same software for so long, they don’t know that there’s a whole ocean out there,” I said recently about this exact pattern. “They’re trying to accomplish what they actually need within the constraints that they’ve been already given.”

Why I stopped trusting the 80% rule

The old rule counted features, and features are the wrong thing to count. A product can check almost every box on a feature list and still miss the part of the workflow that matters most.

A company that sells and installs IT and audio-visual systems used a packaged proposal tool that technically did everything they asked of it. Salespeople could quote anything. The software just did not make them quote completely, and on hardware-heavy jobs, people forgot line items. The contract would get signed, and only then would the team find out the job was under-quoted. A feature count would have said buy. We built them a custom estimating tool that compares a new quote against similar past jobs and flags what is probably missing, so the knowledge that used to live in a few people’s heads now lives in the software.

That gap was a small slice of the feature list and a large slice of the money. Most of the 20% I used to tell owners to live with looks like that.

Custom is also more attainable than it has ever been. Our developers get about 30% more done with AI tooling, and we pass that to clients as faster delivery and lower cost. The math that made “just buy it” the safe default has moved.

How do the costs compare over time?

Off-the-shelf costs less on day one and keeps costing for as long as you use it. Custom costs more up front, and what you pay for becomes something you own. Comparing only the first-year price tag gets the decision wrong in both directions.

When you compare, count everything on each side:

  • Off-the-shelf: the subscription every year, the services or in-house time spent configuring and customizing the product, and the workarounds your people run between systems, measured in hours and in mistakes.
  • Custom: the build, plus the ongoing maintenance and upgrades every real software product needs.
  • The cost of leaving: the more business logic you build on top of a platform you do not own, the more it costs to get out later.

Heavily customizing a packaged platform deserves its own warning. Once you are paying people to bend a product until it fits, you are doing custom work. You just do not own the result.

I am not going to put a dollar figure on this comparison here, because it depends entirely on the business. Any vendor who quotes you a universal break-even number without looking at your operation is guessing.

Should you trust a vendor’s build vs buy advice?

Be skeptical of any vendor, including us. A custom software company has reasons to say build. A platform’s sales team has reasons to say buy. The same skepticism I tell owners to bring to a vendor pitching a rebuild belongs here: ask for the reasons in business terms, and check them against how your company actually works.

On first calls, I often tell people, “I don’t actually have a product to sell you.” The job is to figure out what the business needs before anyone recommends a build, a purchase or a mix. If the honest answer is to buy, we will say so.

The middle path: keep the tools you like and connect them

You do not have to choose between buying everything and building everything. Many companies are happy with the core platforms they run and are frustrated that those platforms do not talk to each other. In those cases, we write software that links the systems a company already owns, so the data is in sync and people get the information they need. Ripping out a working system is unreasonable in most cases.

When that connecting layer grows into the center of the operation, build it properly. The pattern we keep coming back to is an API-first single source of truth that the other systems talk to as clients. We walked through a full example of that, one built in small parts rather than all at once, in our guide to legacy system modernization. If an older system is part of the picture, that is where our application modernization services come in.

Who owns the code and the data?

You should. I want clients to own their data, their code and their own product, and that belief is a big part of why I favor custom software.

Ownership looks different on each side of the decision:

  • With off-the-shelf, you never own the code. Make sure you can export your data in a usable form, and find out what that costs before you sign.
  • With custom, put ownership of the code, the data and the product in the contract. We have met companies whose custom software is owned by the firm that built it, and they are worried they cannot even get their data out without paying a large sum. A vendor owning a client’s custom software is absurd.

How to decide: questions to answer before you talk to anyone

Start with business questions. The technology comes second.

  1. Is this need generic? If most businesses like yours do it the same way, lean buy.
  2. Does the way you do this work make you money or set you apart? If yes, lean build.
  3. What workarounds is your team running today? Write them down, along with who runs them and how often.
  4. Would the product need heavy customization to fit? If so, you are already paying for custom work without the ownership.
  5. Can the tools you like be connected instead of replaced?
  6. Who owns the code and the data, and can you get the data out?
SituationLeanWhy
Generic need, most companies do it the same wayBuySomeone already built the product; a subscription is the sensible move
Real nuance that drives revenue or sets you apartBuildPackaged tools make you work around the part that matters
Good core platforms that do not talk to each otherConnectA custom layer keeps the data in sync without ripping anything out
Heavily customized platform you do not ownRethinkYou are paying for custom work without the ownership

If you are weighing build vs buy for a part of your business, we are happy to talk it through as your custom software development partner. We will tell you if the answer is to buy.

Frequently asked questions

When should you buy off-the-shelf software?

Buy off-the-shelf when the need is generic and most companies handle it the same way, like a dog walking business buying a dog walking app, or any company running its books on packaged accounting software. It fits when your team can use it as designed, without heavy customization or side workarounds.

When should you build custom software?

Build custom when your business has real nuance: the way you quote, price, schedule, produce or serve customers differs from competitors and carries real money. Any business with nuance should have custom software almost every time, because packaged tools force you to work around exactly those parts.

How do the costs compare over time?

Off-the-shelf costs less up front but charges a subscription for as long as you use it, plus customization and the time your team spends on workarounds. Custom costs more up front plus ongoing maintenance, and you own what you paid for. Custom pays for itself once the problems are big enough: when employee turnover, inefficiency killing productivity, or invoices slipping through the cracks become real issues. One client's people kept forgetting to put items on invoices, so they were leaving money on the table, and they could see it. Another was sending hundreds and thousands of texts a day to their drivers to schedule and confirm things. You can't put a number on the ROI for that, but we fixed it and they're thriving now.

Can you start with off-the-shelf and move to custom later?

Yes, and the signs that it is time are easy to spot. The first one, and a huge flag, is using multiple systems to handle your core business objectives and core business workflows. That usually shows up as manual work outside the main system because people feel they can track things better there. Excel spreadsheets are the most common, but Google Docs, Smartsheets or another piece of software doing something the main system doesn't count too. The second sign is workarounds: using the software differently than it was meant to be used. A lot of people discount the value of keeping everything in one place, but it can be extremely helpful. To prepare for the move, don't just collect data, because data always changes. Collect workflows too. Figure out how the data will come out, whether through Excel exports, an API or scraping, and document the workflow of each process, including how the spreadsheets fit in. If you don't know how to do that, talk to a company like ours about how we would approach it. This is also the time to think about AI: what you think you can get out of it and what works best for you, so you come to the table with options. Then make the move in small parts rather than switching everything on one day.

What about a hybrid, with SaaS tools connected through a custom API layer?

A hybrid often makes the most sense when you like your core platforms but they do not talk to each other. Keep them and build a custom layer that keeps the data in sync. If that layer becomes the center of the operation, build it as an API-first single source of truth.

Who owns the code and data?

With off-the-shelf software, the vendor owns the code, so confirm you can export your data before you sign. With custom software, you should own the code, the data and the product, in writing. A development firm owning a client's custom software is absurd.

Have a Project in Mind?

Let's talk about what you're building and how we can help.