← Build, buy and runFree decision tool · Build, buy and run

Build, buy, or partner?

Seven inputs covering your use case, data sensitivity, team capability, and timeline. A weighted algorithm returns a clear recommendation with rationale and risk flags, or a named hybrid path when your inputs don't clearly favour one option, reflecting Gartner's 2026 estimate that roughly 70% of enterprise AI workloads now run on hybrid build-and-buy architectures rather than a single approach.

Listen to this briefing

The AI Build, Buy, or Partner Tool

0:00

How the scoring works

Each of the seven inputs pushes one or more of the three options up or down by a fixed weight. Set all seven, read the recommendation and the risk flags, then move the inputs you are least sure of to see whether the call holds.

How the recommendation is scored

What each input weighs in the build, buy and partner scores

InputBuildBuyPartner
Use case specificity↑ ×2↓ ×2↑ ×1
Data sensitivity↑ ×2↓ ×1not used
Internal AI capability↑ ×1.5↓ ×1↓ ×1.5
Available budgetnot used↑ ×1↓ ×1.5
Timeline urgencynot used↑ ×2↑ ×1
Competitive differentiation↑ ×1.5not usednot used
Maintenance appetite↑ ×1↓ ×1↓ ×1
A higher answer raises this option's scoreA lower answer raises this option's score

Each option's weighted total is scaled to a score out of 100 and the highest score wins. When the top two scores are within 8 points, the tool returns the named hybrid path for that pair instead.

Weights as used by this tool's scoring model. Partner counts use case specificity with a floor of 3, so answers of 1 or 2 score the same as 3.

Your decision inputs

0 of 7 inputs set. Drag or tap each slider, including any you would leave at 3.

Not set

How unique or proprietary is this AI use case to your business?

Not set

How sensitive is the data this AI system will process?

Not set

How strong is your internal AI and technical delivery team?

Not set

What is your implementation and first-year operating budget?

Not set

How quickly do you need to be live and delivering value?

Not set

Is this AI capability a genuine competitive differentiator for your business?

Not set

How willing is your organisation to own and maintain this solution long-term?

Your recommendation

Answer to start. Set any input and the three scores appear here. The recommendation firms up once all seven are set.

The three options

Build

When it applies

Your use case is proprietary, the data is too sensitive to share with a vendor, your internal team has AI engineering capability, and this is a long-term competitive differentiator that justifies the investment.

Typical profile
  • Timeline: 6–18 months to production
  • Budget: High upfront, lower marginal cost at scale
  • Risk: Execution risk. Needs strong delivery governance
  • Upside: Maximum customisation, full IP ownership, no vendor lock-in

Buy

When it applies

The use case is relatively standard, you need results quickly, your internal team doesn't have AI engineering capacity, and the function is not a primary competitive differentiator. The market already has good solutions.

Typical profile
  • Timeline: 4–12 weeks to go-live
  • Budget: Predictable SaaS/platform licensing costs
  • Risk: Vendor lock-in, data governance, customisation ceiling
  • Upside: Proven, fast, low internal overhead

Partner

When it applies

The use case is specific enough to need customisation but your internal team doesn't have sufficient AI expertise, budget is constrained, or you need to move faster than a full build allows. A systems integrator or specialist vendor brings the expertise while you retain ownership.

Typical profile
  • Timeline: 8–20 weeks depending on scope
  • Budget: Project-based; moderate upfront, ongoing support cost
  • Risk: Partner dependency, knowledge transfer critical
  • Upside: Faster than build, more custom than buy, builds internal capability over time
Terence Kok
Before You Go

This tool exists because build versus buy versus partner usually gets decided by whichever vendor reached the team first, before anyone has looked at the situation properly. Seven inputs, things like data sensitivity and how much your team can realistically maintain, and the algorithm gives you a weighted answer along with the risk flags most vendors won't volunteer. I've watched capable teams choose build when they had neither the budget nor the appetite to maintain it. This tool makes that mismatch visible before you commit.

Terence Kok

Last updated 29 Sept 2026

More in Build, buy and run

Next in this group · AssessmentAI Vendor Evaluation ScorecardWhich of these two vendors should we sign with?Compare vendors →
← All 8 in Build, buy and run