Build vs Buy: A Practical Decision Framework for SMBs
Every growing business hits the same fork in the road over and over: a process is painful, and you have to decide whether to buy a tool, build one, or wire existing tools together. Here's a framework you can apply in ten minutes instead of agonizing for weeks.
Step 1: Is this core or context?
Borrowing a useful distinction: core is the work that makes you money and sets you apart; context is everything else that simply has to happen.
- Context (payroll, email, accounting) → buy. Never build what isn't your edge.
- Core (the workflow your customers pay for, your secret sauce) → strongly consider building.
If you build your context and buy your core, you've got it backwards.
Step 2: Does a tool actually fit?
For context work, check whether an off-the-shelf tool fits your process with minor adjustment. If you'd have to contort your business to fit the tool, or run three tools plus a spreadsheet to cover one process, the "buy" option is quietly costing you in labor and errors.
Step 3: What's the cost of being wrong?
- Reversible and low-stakes? Buy the quickest option and move on.
- Hard to reverse, or central to operations? Slow down. This is where a tailored build pays off, because switching costs later are brutal.
Step 4: Run the real math
Compare total cost over three years, not month one:
- Buy: subscription × seats × growth, plus the labor spent working around gaps.
- Build: upfront development, plus ongoing maintenance and hosting.
- Hybrid: buy the commodity pieces, build the thin layer that connects them.
The hybrid wins more often than people expect, because it avoids both rebuilding solved problems and paying forever for a poor fit.
A cheat sheet
| Situation | Lean toward |
|---|---|
| Common, standard process | Buy |
| Your competitive advantage | Build |
| Good tools exist but don't connect | Hybrid (build the glue) |
| Need it next week, low stakes | Buy |
| You'll run it for years, high stakes | Build |
The trap to avoid
The most expensive outcome isn't building or buying, it's drifting: adding one more subscription, one more spreadsheet, one more manual handoff until your "system" is a fragile web nobody fully understands. If that's where you are, the fix is usually a small custom layer that ties things together, not another tool.
Not sure which way a specific decision should go? Walk me through it, I'll give you a straight build/buy/hybrid recommendation based on your actual situation, even when the answer is "don't build anything."
Have a project in mind?
Let's turn it into custom software that moves your business forward.