Building Capability

Tool: The Build / Buy / Borrow Decision Guide

Chapter: 8 — Technology Is the Last Decision, Not the First
Purpose: For each capability on your roadmap, make a clear, defensible decision about whether to build custom, buy off-the-shelf, or use a hybrid — based on where your competitive advantage actually lives.

How to Use This Tool

Work through this tool for each significant capability on your roadmap. It won’t make the decision for you — but it will make the criteria explicit so the decision is made for the right reasons rather than by default, budget instinct, or vendor preference.

Before you begin: Look at the systems column of your Business Landscape Map from Chapter 2. For each system currently shown — software platforms, data sources, integrations, shared drives — ask: is this fit for a future that’s significantly more capable than today? Is it flexible enough to connect with what you’d want to build? Or is it already a constraint you’ll need to design around? The build/buy/borrow decision starts with what you already have.

Allow 30 minutes per capability.

Part 1: Locate the Competitive Advantage

Before any technology decision, answer the question that matters most.

1. Is the process or capability you’re building a source of competitive advantage for your organisation?

A source of competitive advantage means: the way you do this is genuinely different from how your competitors do it, and that difference matters to your customers. It reflects specific knowledge, a specific way of operating, or a specific depth of understanding that a generic tool would flatten or ignore.

Capability being assessed:
Is it a source of competitive advantage? (Yes / No / Partly)
Explanation:

2. If you used off-the-shelf software for this, what would you lose?
Be specific. Would you lose nuance in how the process works? Specific customer data structures? Particular decision logic? Or would you lose nothing meaningful — because the process is genuinely generic?

What you'd lose with off-the-shelf:
Whether that loss matters:

3. If a competitor bought the same off-the-shelf tool, would they then be able to match you on this capability?
If yes, this capability is probably not a source of competitive advantage — and off-the-shelf is a reasonable choice. If no, it’s worth protecting.

Could a competitor match you by buying the same tool? (Yes / No)
Why:

Part 2: Assess the Options

4. Is there an off-the-shelf solution that genuinely fits this process?
Not “could we make it work with some configuration” — but “does it actually fit how we operate, without bending our process to fit the tool?”

Off-the-shelf options considered:
Whether any genuinely fit (and why / why not):
Approximate cost:

5. What would a custom build give you that off-the-shelf can’t?

Custom build advantages:
Approximate cost and timeline:
Ongoing maintenance consideration:

6. Is a hybrid the right answer?
Many good solutions use off-the-shelf infrastructure for the generic parts (authentication, billing, storage, notifications) with a custom layer for the proprietary logic that makes the capability distinctive.

What could be off-the-shelf (generic / commodity):
What should be custom (where your advantage lives):
Whether a hybrid approach is viable:

Part 3: The Nucleus Check

Map this capability to the nucleus model from Chapter 8:

Where does this capability sit in your nucleus model?

[ ] Core nucleus — the expert knowledge itself (almost always custom)
[ ] Guided by experts — custom layer that supports expert judgement
[ ] Done by juniors — systematised enough for less experienced staff (often hybrid)
[ ] Given to customers — customer-facing tools (hybrid or custom, depending on differentiation)
[ ] Infrastructure — generic plumbing (almost always off-the-shelf)

Does your decision (build / buy / hybrid) match where this sits in the model?

Decision: Build / Buy / Hybrid
Consistent with nucleus position? Yes / No
If not — what needs to change:

Part 4: The Decision

My recommendation for this capability:

Decision: Build custom / Buy off-the-shelf / Hybrid
Primary reason:
One-line rationale:

What would change this decision?
(e.g. if the off-the-shelf cost dropped significantly, or if the custom build proved more complex than expected)

What would change it:

Online Version

Want to go deeper?
The online version of this tool includes a full technology options assessment matrix, a guide to evaluating specific platform categories (CRM, workflow, data, AI tools), and a worked example of the nucleus model applied to a professional services business.
Available in the members area at [website]