The answer is almost never obvious — and that's the point.
Plenty of build-vs-buy advice comes from someone with software to sell — and it shows. Five factors actually move the needle. Score them honestly, from a vendor-neutral starting point, and your lean becomes clear without anyone's sales quota shaping the answer.
By Joe Perone, Senior Principal Last updated
What we talked through
First, a reframe: build vs. buy is usually really buy vs. buy-and-integrate. Pure custom builds are rare and, for common workflows, often unnecessary. And a "bought" tool that doesn't talk to your CRM or case-management system isn't free — it just moves the labor from building to babysitting. Five factors actually shift the answer:
- Uniqueness. Build what's highly specific to your mission or process. Buy what's common and industry-standard — custom-building a commodity is wasted budget.
- Vendor fit. If a product already exists and covers 90% of the need, building the last 10% yourself is usually a bad trade.
- Integration complexity. How hard is it to connect to what you already run? High complexity erases much of "buy's" head start.
- 3-year total cost. Not the sticker price — the full cost of ownership over three years (use the TCO map). And watch the other direction: "buy" can quietly become riskier through lock-in, data portability, and price hikes once you depend on it.
- Capacity to maintain. Building without the team to sustain it post-launch is buying a liability, not an asset.
One more thing, said plainly: this advice matters most when it's vendor-neutral. Balboa doesn't sell software, so we have no stake in the answer — if the honest read is "buy," we'll say buy. Score the five factors together and a lean emerges, but no single factor should decide it alone. If you're leaning Build on the strength of just one "5," pressure-test that before you commit budget.
Interactive · ~60 seconds
The Build/Buy Decision Scorecard
Slide each factor toward Buy (1) or Build (5) for your situation. The gauge shows your overall lean — but read the caveat below it before you treat the number as an answer.
Your lean
Balanced
3.0 of 5 · 1 = Buy, 5 = Build
No single factor should decide this alone. If you're leaning Build on the strength of just one strong "5," pressure-test that before committing budget. Use the gauge to start the conversation, not to end it.
Take it with you
The five-factor scorecard
| Factor | Leans Buy | Leans Build |
|---|---|---|
| How unique is this workflow to us? | Common, industry-standard. | Highly specific to our mission or process. |
| Does a vendor solution exist and fit? | Yes — a close fit. | No, or a poor fit. |
| Integration complexity | Low. | High. |
| 3-year total cost (see TCO map) | Buying is cheaper. | Building is cheaper. |
| Internal capacity to maintain it | Low. | High. |
Reminder: score all five, then let a genuine non-negotiable override the average where it should.
High-intent? Let's talk it through
Facing a real build-vs-buy call? Get a senior read on it
Score your factors above, then send your email — your scorecard comes with it. We'll give you an honest take, including when we think you shouldn't hire anyone at all. No deck, no junior gatekeeper.
No spam, no drip sequence. We use your email to send what you asked for and, at most, one follow-up. Prefer to talk? Book a 30-minute strategy call — no deck, no junior gatekeeper.