A 2026 decision framework for established businesses

Build it. Buy it. Own it. Or wait.

Most software decisions come down to two options: buy a vendor's tool and bend your processes to fit it, or build something internal that solves the problem properly. Both carry real costs that rarely appear in the original business case. This framework runs in two stages — first whether building and owning is the right strategic call, then whether your organisation is actually equipped to do it.

Stage 1

Is ownership the right call?

Build · Buy · Extend · Wait

→

Stage 2

Are you ready for it?

Only if Stage 1 points to ownership

Run the framework →

What most software decisions get wrong

The real cost of SaaS isn't the licence fee. It's the process changes, the workarounds, the staff time spent compensating for what the tool doesn't do — and the contract you're locked into when the vendor reprices.
Off-the-shelf software is built for the average business in your sector. The more your operations differ from average — and in most established businesses, the differentiating parts do — the more you pay in friction every day.
Internal builds fail for the same reason, every time. Not because the software was badly written. Because no one owned it after it launched. The question isn't whether you can build it — it's whether you can run it.
Ownership means more than having the source code. Infrastructure, security, someone who holds the backlog, a team that can maintain and extend it. Handing over code is the beginning of ownership, not the end.
Where you are in your vendor contract changes everything. Starting fresh, mid-contract, and approaching renewal are three different decisions with three different sets of options. This framework accounts for where you actually sit.

Is ownership the right strategic call?

Ten questions, four areas. Stage 1 works out which direction the evidence actually points — build it yourself, buy off-the-shelf, extend a vendor platform with your own layer, or wait. If it points to ownership, Stage 2 checks whether your organisation is ready to take it on.

01Strategic — does this need to be yours?3 questions

Q1How much does this capability differentiate you from competitors?

Is this where you actually win — or commodity infrastructure that just needs to work?

Core differentiator — this IS our edge

Important strategic enabler

Operational necessity, not differentiating

Pure commodity infrastructure

Q2How much does your workflow diverge from the industry standard?

Vendors design for the median customer. How much does the median tax you?

Highly unique — vendor workflows distort our ops

Notably different — heavy customisation needed

Roughly aligned with industry norms

Identical to standard practice

Q3Would your proprietary data and processes give you a lasting competitive advantage if they powered this software?

Think about operational data, process knowledge, and customer insight that competitors can't easily replicate.

Yes — our data and processes are genuinely distinctive

Somewhat — moderate advantage, not decisive

Limited — others in our sector have similar data

No — our data wouldn't add meaningful differentiation

02The vendor reality — what's actually on offer?2 questions

Q4How well do available vendors actually solve your specific problem?

Be honest about fit — not their marketing, but how much the product actually matches your workflow as it stands today.

Excellent — minimal gaps, solves the problem cleanly

Decent — workable gaps, we could make it fit

Partial — significant gaps even after configuration

No real fit — we'd be forcing a square peg into a round hole

Q5How concerned are you about vendor lock-in and pricing increases over the next renewal cycle?

Think about switching costs, data portability, and where you expect the contract price to be in two to three years.

Very concerned — already locked in, prices already rising

Concerned — real switching cost, pressure building

Moderate — manageable for now, pricing is stable

Low — easy to switch, pricing is predictable

03Build reality — can you actually do it?2 questions

Q6What is the realistic build effort for this, given what's available today?

Be honest about scope. A focused internal team with modern tools can move faster than most organisations expect — but not for every problem.

Small team, 6–8 weeks

Focused team, 3–6 months

6–12 months, substantial investment

12+ months or genuinely uncertain

Q7Do you have the technical team to build and maintain this?

Less about headcount, more about whether you have people who can own a codebase, make architecture decisions, and keep it running.

Yes — experienced team with capacity available

Capable team, would need some upskilling

Limited engineering bandwidth

No relevant in-house capability

04Risk & timing — what if you're wrong?3 questions

Q8What's the regulatory burden + downside if a build underperforms?

Specialised compliance can favour mature vendors who've already invested.

Heavily regulated, severe failure consequences

Moderate compliance, real but manageable downside

Light regulatory load, recoverable failure

No regulatory considerations

Q9How mature are the technical foundations needed to run AI-powered software in your environment?

This covers the basics: the ability to deploy, monitor, and maintain software that includes AI components. It's often the real constraint — more than the cost of building.

Mature — we can deploy, monitor and maintain AI software today

Building — some foundations in place, actively developing

Early — limited experience, fragile starting point

Starting from scratch — no experience running AI software

Q10Where are you in the vendor lifecycle for this capability?

Greenfield, at-renewal, mid-contract, and just-signed are very different decisions.

Greenfield — no incumbent vendor

At renewal — actively considering switching

Mid-contract — switching expensive but possible

Just signed — locked in for 2–3 years