A single-city booking problem is annoying. A five-city one, running simultaneously, with different teams rotating in and out on different timelines, is a different order of problem entirely — and it's exactly what a lot of consulting, IT services, and manufacturing rollouts look like in practice.
Why multiplying cities doesn't multiply linearly
The obvious assumption is that managing accommodation across five cities is five times the work of managing it in one. In practice it's worse than that, because the coordination overhead compounds:
- Different vendors in each city means different invoice formats landing on finance's desk in the same month
- No shared visibility means one city's team doesn't know if another city already negotiated a better rate with the same hotel chain
- A policy exception granted informally in one city (a late check-out, a rate adjustment) has no record anywhere else, so it gets re-negotiated from scratch every time
A framework that scales without scaling headcount
One request format, every city. The same request process — city, dates, budget band, project code — regardless of whether it's Gurgaon or Kolkata. Consistency is what makes centralized reporting possible later.
Preferred properties per city, not per booking. Once a property has been verified and used successfully in a city, it becomes the default option for that city's future requests, cutting repeated due diligence to zero.
One billing relationship, mapped to project codes. A single monthly statement that breaks down spend by city and project, rather than a folder of hotel invoices that someone has to manually sort and code.
The goal isn't to remove local flexibility — it's to remove the part of multi-city logistics that has nothing to do with the actual project and everything to do with fragmented vendor management.
What this looks like at rollout scale
For a 200-person deployment spread across five metros over a two-quarter project, the difference between fragmented and centralized accommodation management usually isn't visible in any single booking. It shows up in aggregate: fewer emergency escalations when a property falls through, one clean report finance can close the books against each month, and a project lead who can answer "where is everyone staying and is it working" without pulling data from five different sources.
