Build Own Operate
Definition
Build Own Operate
Build own operate is an arrangement where a provider builds a facility or capability, owns it outright, and runs it as a service. There is no transfer at the end, which is the whole point of choosing it over the alternatives.
The model shows up wherever the buyer wants an outcome and has no appetite to own the machinery behind it.
Data centres, contact centres, and utilities are the classic settings — the provider carries the capital, the risk, and the refresh cycle.
Compare it to build operate transfer and the difference is one word — ownership stays put, so the contract has to work indefinitely rather than for a defined term.
That changes the negotiation. Without a transfer option, the buyer’s only real protection is a solid exit clause and a credible second supplier.
Pricing is usually per unit of service: per seat, per transaction, per megawatt, or per rack, rather than a recovery of build cost.
Key takeaways
- Build own operate leaves ownership with the provider permanently.
- It suits buyers who want the outcome without the capital or the refresh cycle.
- Exit provisions matter more than in models with a transfer option.
- Pricing is normally per unit of service rather than a build cost recovery.
How it works
The provider funds and builds the asset, keeps title to it, and sells the resulting capability as a service against agreed levels. The buyer pays a recurring charge and never takes ownership, which keeps the capital off its own balance sheet.
Cloud computing is the mass market version of this. Somebody else built the data centre, owns it, and rents you the capability by the hour.
| Model | Who owns the asset | Buyer exit route |
|---|---|---|
| Build own operate | Provider, permanently | Contract termination and migration |
| Build operate transfer | Provider, then buyer | Exercise the transfer option |
| Captive | Buyer, from day one | Restructure or close |
| Conventional outsourcing | Provider or neither | Retender the service |
The cloud definition makes the pattern explicit. NIST SP 800-145 describes cloud computing through five essential characteristics, three service models, and four deployment models, all of them provider owned.
Public buyers are steered towards outcomes rather than assets. FAR Part 37 makes performance based acquisition the preferred method for services, which fits an arrangement where the buyer never owns anything.
Test the exit before signing — if migrating away would take two years and a rebuild, the recurring price is far less negotiable than it appears.
Examples
Build own operate appears in data centres, contact centres, energy, and increasingly in managed technology platforms. Four cases show why buyers chose it and what they gave up in return.
A UK retailer. Bought contact centre capacity as a service in 2024. The provider owned the site, the technology, and the workforce contracts.
A hospital group. Contracted an energy provider to build and own a combined heat and power plant. The hospital bought heat and electricity, not equipment.
A financial services firm. Used a provider owned data centre rather than building one. The refresh cycle became somebody else’s capital problem.
A logistics operator. Signed a ten year deal for warehouse automation. Exit modelling was done at year seven rather than year one, which weakened the renewal.
Related terms
Build own operate belongs to the family of models describing who owns the delivery capability. The terms below cover the alternatives it competes with and the contract mechanics that make it workable.
- Build-Operate-Transfer (BOT): the variant ending in a handover to the buyer.
- Captive Center: the opposite model, where the buyer owns everything.
- Managed Services: the service posture these deals are sold as.
- Fully Managed Outsourcing: the delivery model where the provider owns the outcome.
- Data Center: the asset type most often held this way.
- Global Delivery Center: the provider owned site delivering the service.
- Service Level Agreement (SLA): the main control the buyer actually holds.
FAQ
How does build own operate differ from build operate transfer?
Ownership never moves. Build operate transfer ends with the buyer taking the asset; build own operate leaves it with the provider indefinitely.
When is it the better choice?
When the buyer wants the outcome, not the asset, and has no strategic reason to own the capability. Capital intensity is usually the deciding factor.
What is the main risk?
Lock in. Without an ownership route, the buyer depends entirely on the exit clause and the existence of an alternative supplier.
How is it priced?
Per unit of service, such as per seat, per transaction, or per unit of capacity. Build cost is recovered inside that rate over time.
Is cloud computing a build own operate model?
Effectively yes. The provider owns the infrastructure and sells the capability, which is the same structure at industrial scale.
What should the exit clause cover?
Notice periods, data return, migration assistance, and a maximum transition charge. Test the timeline before signing, not at renewal.
Explore outsourcing models and provider options at Outsource Accelerator.
Independent
