Every organisation that runs exams, assessments or training across a country eventually asks whether it should stop renting and start building. The instinct is reasonable: rates look like money leaking out, and an owned lab feels like an asset rather than an expense.
The instinct is also where the arithmetic usually goes wrong, because it compares a day rate to a day rate. That is not the comparison. The comparison is between a cost that stops when you stop, and a cost that does not.
The two models
Own infrastructure. You take space — leased or bought — fit it out with workstations, power backup, connectivity and furniture, get it audited, and it is yours. It runs when you want it to. It also exists on the 300 days a year you do not use it.
Pop-up classrooms and booked centres. You stand up capacity in a space that already exists, for the days you need it, and hand it back. Someone else owns the utilisation problem, the maintenance and the lease.
Side by side
The arithmetic that actually decides it
Strip it to one line. An owned site is worth it when
Everything follows from the first term. At 200 days a year the fixed cost spreads thin and owning usually wins. At 20 days a year it does not, and no negotiation on the day rate closes a gap that size — because the thing you are paying for is the other 345 days.
So the honest first question is not "what does a centre cost?" but "how many days a year will this specific location actually run?" For a head-office training facility in a metro, the answer can genuinely be most of the year. For an exam centre in a tier-2 city serving two hiring cycles, it is a fortnight. Those two answers point in opposite directions, and they are often asked about the same organisation in the same meeting.
Why expansion changes the answer
Expansion is normally about coverage — being present where candidates are, so they do not travel and attendance holds up (see how many seats to book). Coverage is exactly the case where owning compounds against you.
Going from 3 cities to 30 does not multiply your demand by ten in each place. It spreads roughly the same volume thinner. Owned capacity in that world means thirty leases, thirty fit-outs, thirty audits and thirty separate utilisation problems — each one worse than the last, because the thirtieth city has the least demand. The booked model in that world means thirty bookings.
This is why the two models are not really competitors. They answer different questions, and most organisations expanding a national footprint are asking the coverage one while evaluating the density answer.
The cost that does not appear in the model
Three things reliably get left out of the build-versus-book comparison, and all three favour not building:
- Refresh. A computer lab is not a one-off cost. Workstations age out, and the fit-out you are amortising over ten years contains equipment with a much shorter life.
- Asset specificity. A 200-seat exam lab is a poor office, a poor warehouse and a poor anything else. If demand moves, the asset does not move with it, and it does not resell into a broad market.
- Management attention. Every owned site is a landlord relationship, a maintenance schedule, a security question and a person whose job it is. Thirty of them is a property operation attached to an organisation that did not set out to run one.
Where owning genuinely wins
A comparison that only argues one way is not worth reading. Owning is the right call when:
- Utilisation is high, steady and in one place. A permanent assessment or training centre in a metro running most weeks of the year is exactly the case the fixed-cost trade was designed for.
- The environment has to meet a standard no third party will. Specialised equipment, a fixed physical configuration, or an accreditation that inspects the premises rather than the session.
- Custody is the requirement. Where security obligations extend to the building itself and not just to the exam, a contract with a venue may not be enough.
- The space is the product. If people are buying the room — a flagship, a showcase, a brand experience — then it is not delivery infrastructure and this comparison does not apply to it.
Notice that all four are arguments about particular locations. None of them is an argument for a footprint.
What most organisations land on: anchor plus pop-up
Own or hold long-term space only where volume is dense and continuous — in practice a handful of metros. Cover everything else on demand.
This keeps control where control pays for itself, and keeps the long tail variable, which is precisely where the idle-capacity risk of owning bites hardest. It also means a new city is a test rather than a commitment: run it booked for two cycles, look at the volume, and only then ask whether it has earned a permanent site. Very few do.
The practical point
A network already spans the footprint that owning would take years and a great deal of capital to assemble. Ours runs to 730 centres across 225 cities in 35 states. Reproducing that by building is not a budget decision; it is a different company.
The useful way to frame it internally is not "build or rent". It is: which of our locations have earned a fixed cost, and why are we carrying one anywhere else?
