The question behind the question
Build-versus-buy is rarely a technology decision. It is a decision about where your business wants to be different. Software that supports a commodity process — payroll, email, general ledger — should almost always be bought. Software that embodies how you win customers or run operations better than competitors is a candidate for building.
Most organizations get into trouble at the edges: buying a product for a differentiating process and then spending years fighting its limitations, or building something a mature product already does well because the team enjoys building.
Five questions that decide most cases
- 01
Is this process a competitive differentiator?
If customers choose you partly because of how this works, owning the software has strategic value. If not, buying is usually right.
- 02
How much of the need does the best product cover?
If a product covers most needs with configuration, buy it. If critical workflows require workarounds, the gap has a cost every day.
- 03
How will costs scale?
Per-seat or per-transaction pricing can grow faster than value as you hire or grow volume. Model three to five years, not one.
- 04
How many systems must it connect to?
Products with weak APIs can trap data. Custom software can be designed around your integrations from the start.
- 05
Can you sustain it?
Building means owning maintenance, security updates and a roadmap — through an in-house team or a partner. Be honest about that commitment.
A quick comparison
| Consideration | Buy | Build |
|---|---|---|
| Time to value | Days to weeks | Months for a first release |
| Fit to process | You adapt to the product | The software adapts to you |
| Cost profile | Low start, recurring fees that scale | Higher start, lower marginal cost |
| Control of roadmap | Vendor decides | You decide |
| Risk | Vendor price changes, discontinuation, data portability | Delivery risk, maintenance commitment |
Run the total cost comparison properly
For the buy option, include subscription fees at your projected user count for each year, paid add-on modules, integration middleware, implementation and configuration services, and the staff time spent on manual workarounds.
For the build option, include discovery, design, development and testing, hosting, third-party services, and ongoing maintenance — a common rule of thumb is roughly 15–25% of the initial build cost per year. Then compare cumulative cost by year. The crossover point, if there is one, tells you how long you must use the system for building to pay off.
The hybrid options most teams overlook
The choice is rarely all-or-nothing.
Buy the core, build the edge
Use a commercial platform for standard functions and build custom applications for the differentiating workflow, connected through APIs.
Extend a platform
Many CRMs, ERPs and commerce platforms support custom apps and extensions. You get the core for free and own only what is unique.
Compose from services
Assemble custom software from managed building blocks — authentication, payments, search, messaging — so you build only the business logic.
Signs you bought when you should have built
- Critical work happens in spreadsheets exported from the product
- You pay for multiple add-ons to approximate one workflow
- Staff keep a list of “things the system can’t do”
- Integration middleware costs are growing every year
- Customers notice the limitations of your tools