know.2nth.aiCEO Briefing
← All briefings
Board Briefing · Who owns what you run on

Do you own your business — or rent it back from your vendors?

The software, settings, customisations and data your organisation runs on are valuable assets — as real as a building or a brand. The question most boards never ask is a simple one: if you walked away from a vendor tomorrow, what could you actually take with you? This is a five-minute, jargon-free look at the answer, and why it matters to the bottom line.

5-minute read For CEO & CFO No technical knowledge needed
The bottom line, up front

Right now, the things that make your business yours — your configurations, customisations, specifications and data — may be living inside systems you don't control. That isn't a technology problem; it's an ownership and risk problem. The fix is straightforward and inexpensive: keep the assets that matter in a vault you hold the keys to, so changing vendors is a decision you make — not a hostage situation you're trapped in.

01 · The one question that matters

If you left every vendor tomorrow, what could you take?

Most assets fall cleanly into one of two columns. The trouble is that the most valuable, hardest-to-rebuild ones — the bespoke configurations and the data — quietly end up on the wrong side.

Theirs — you'd lose it
Locked inside a vendor's system, on their terms
  • × The customisations you paid to have built
  • × The settings that make the system fit your business
  • × Specifications and know-how held in a vendor's tool
  • × Data you can only export the way they allow
  • × The record of who changed what, and why
Yours — you'd keep it
In a vault your organisation controls
  • A complete master copy you can move anywhere
  • Every change recorded, dated and attributable
  • Settings and customisations you can take with you
  • Your data, in your hands, on your timeline
  • The freedom to switch suppliers without starting over
02 · How it happens

Nobody decides to get locked in. It just gets more expensive to leave.

Lock-in is never a single decision. Each convenient choice — let the vendor hold the configs, keep the specs in their portal, accept their export format — is reasonable on its own. Together they raise the cost and risk of ever leaving, a little more every year, until "let's switch" becomes "we can't afford to."

The cost of leaving, over time

Illustrative — the shape is what matters, not the scale

COST & RISK OF LEAVING Year 1 Year 2 Year 3 Year 4 Year 5 Rented assets Owned assets
Rented The longer you stay, the more is buried in the vendor's system — and the harder, riskier and pricier leaving becomes.
Owned Because you always hold a complete copy, switching stays a planned move at roughly the same modest cost, year after year.
03 · The comparison

Owned vs rented, on the things a board cares about

Same six lenses you'd apply to any major asset decision — control, exit cost, compliance, spend, continuity, and leverage.

What you're weighing
Rented from vendor
Owned by you
Control
The vendor holds the keys
You hold the keys
Cost of switching
Rises every year — can become prohibitive
Stays low — a planned migration
Audit & compliance
"Prove what your system does" depends on them
A complete, dated record you can show
Cost model
Fees that grow with headcount & usage
Largely fixed running cost you control
If the vendor fails
Your operations are exposed
You still hold everything that matters
Negotiating leverage
Weak — they know you can't easily leave
Strong — a credible ability to walk away
04 · The money picture

What you're really paying for

The headline price isn't the whole cost. Rented systems tend to charge in ways that scale with your success — more people, more usage, more fees — and the largest cost of all only appears the day you try to leave.

Rented — cost grows with you

Per-person licence feesgrows
Add-on modules & usagegrows
Exit cost (the day you leave)large & hidden

Every new hire and every busy quarter raises the bill — and the exit cost sits off the books until you need it most.

Owned — cost stays predictable

Running the systemssteady
Setup & support effortupfront, then flat
Exit cost (the day you leave)minimal

No per-person licence to multiply, and leaving is cheap because you already hold a full copy. Honest trade-off: you take on running it.

The honest catch

Owning is not free of effort. Someone has to look after the systems — in-house or through a partner. The win is not "no cost"; it's predictable cost, kept control, and no exit penalty. For most organisations the maths favours ownership the moment headcount grows or a vendor relationship sours.

05 · The cost of being wrong

Five things that go differently when you own the keys

None of these are exotic. They are the ordinary ways a vendor relationship turns into a liability — and how the same event plays out depending on who holds the assets.

The vendor raises the price
If rentedYou pay, because leaving costs more than the hike.
If ownedYou negotiate, or you go. Real leverage.
The vendor goes out of business
If rentedYour operations are suddenly at risk.
If ownedYou still hold everything; you migrate calmly.
You want to switch suppliers
If rentedA painful, costly rebuild from scratch.
If ownedA planned move — you take your assets along.
There's a data breach or dispute
If rentedYou depend on the vendor for answers.
If ownedYou have your own complete, dated record.
An auditor asks you to prove it
If rented"What does the system do?" lives in their hands.
If ownedEvery change is on the record, attributable.
A key person leaves
If rentedKnowledge walks out the door with them.
If ownedThe history stays — it's written down and kept.
06 · To be clear

This isn't "ditch your vendors"

Familiar office tools are still the right home for most things

Your everyday platforms — the place you store documents, share files and collaborate — are excellent at exactly that, and there's no reason to move it. Finished documents, contracts, proposals and presentations belong where they are easy to work on together.

The danger is narrower and specific: when the IP-bearing assets — the customisations, the settings, the specifications and the live data that the business actually depends on — live only inside a system you don't control. That's the line. Keep the office files where they're convenient; keep the crown jewels in a vault you own.

07 · What to do

Three moves, none of them dramatic

You don't need to rip anything out. You need to make ownership a standing rule and quietly bring the important assets home.

1

Take stock

Ask one question across the business: for each system we rely on, what could we take with us if we left — and what would we lose? The list is usually shorter and scarier than expected.

2

Bring the keys home

Move the assets that matter — configurations, customisations, specs and data — into a vault your organisation owns, with a full history. Low cost, mostly a one-time setup.

3

Make it a standing rule

From now on, "can we walk away with everything?" is a standard question in every vendor contract and renewal. Ownership becomes the default, not an afterthought.

If your tech team mentions the technical terms — here's the translation
A vault you own, with full history=Git / GitHub
Your complete master copy=a repository
The dated record of every change=commit history
Nothing changes without review=pull requests
The decision

Either your business owns the things that make it yours — or it rents them back, at a price that only goes up. The cheap moment to fix that is now, before the next renewal.