The choice between build, buy, and borrow rarely comes down to technical capability. It comes down to which risk you’re willing to own: loss of control, delay in value, or dependency on an external provider.

Score your initiative against the four factors below, then check which path your scores point toward.

Rate Your Initiative (1–5 each)

1. Security & Data Sensitivity How sensitive is the data or capability involved? 1 = Low sensitivity, comfortable with external providers · 5 = Extremely sensitive, must stay fully in-house

Score: [ ]

2. Ownership & Competitive Advantage Is this capability core to your competitive edge, or a supporting function? 1 = Not a differentiator, commodity capability · 5 = This is the competitive advantage

Score: [ ]

3. Speed & Time-to-Value How urgently do you need this live and working? 1 = We can afford to build it properly over time · 5 = We need this operational now

Score: [ ]

4. Long-Term Cost & Maintenance Burden How much ongoing internal cost and maintenance can you absorb? 1 = Comfortable owning ongoing build/maintenance cost · 5 = Need to minimize ongoing internal burden

Score: [ ]

🧭 Tally Your Scores

Control Score = Security & Data Sensitivity + Ownership & Competitive Advantage Control Score: ___ / 10

Velocity Score = Speed & Time-to-Value + Long-Term Cost & Maintenance Burden Velocity Score: ___ / 10

🚦 Decision Gate

Control Score Velocity Score Verdict Action
7–10 2–6 Build You need ownership and control more than speed. Invest in building this internally — the cost is justified by the strategic value of owning it.
2–6 7–10 Buy Speed and minimizing internal burden matter more than ownership here. License an existing solution rather than building or customizing one.
7–10 7–10 Borrow You need both control and speed — a pure build will be too slow, a pure buy won’t give you enough ownership. Use a vendor’s underlying capability, but layer your own governance, data controls, and customization around it.
2–6 2–6 Borrow Neither factor is a strong driver here. Default to the lowest-commitment option — borrow or buy — and revisit if the stakes change.
Within 2 points of each other Borrow No dominant factor. This is exactly the profile where blending vendor capability with your own safeguards outperforms picking a single path.

The Real Question

Whatever your scores say, the decision ultimately comes down to one question: which risk are you choosing to own — loss of control, delay in value, or dependency on someone else’s roadmap? There’s no universally right answer, only the one that matches what your organization can actually tolerate right now.


For the full thinking behind this framework, read Build, Buy, or Borrow: The Wrong Question.