New Delhi, Aug. 11 -- Why a CRE-funded, data-driven approach to real estate and IT works for companies of any size, and why it matters most for fintech and banking.

The Problem: Paying Full Price for Half-Used Space

Corporate real estate is one of the biggest fixed costs a bank carries, right after people. It's also one of the hardest costs to touch, because so much of it sits inside long-term leases and seat allocations nobody has looked at in years.

One global bank ranked every location it occupied by CRE cost, meaning rent, lease, and facilities spend, and pulled out the 200 that cost the most on that measure specifically, spanning regional hubs and back-office centers across multiple countries and continents. These weren't necessarily the biggest offices or the busiest ones. They were the 200 locations where the corporate real estate line item itself was highest. The reason those costs had crept up was simple: seats were assigned based on headcount on a spreadsheet, not on how many people actually showed up and used them. Nobody had measured the gap. Once they did, it was hard to unsee. A meaningful share of assigned seats sat empty on a typical day, while the bank kept paying for 100% of the space regardless.

"A meaningful share of assigned seats sat empty on a typical day, while the bank kept paying for 100% of the space regardless."

The goal became clear: cut occupancy allocation from 100% down to 80% across those 200 sites, without disrupting operations, hurting the employee experience, or triggering a years-long fight to unwind leases. The savings target attached to that goal was ambitious, roughly $200 million globally. The program hit it.

This isn't a pandemic story or a remote-work story. The gap between "seats we pay for" and "seats we actually use" exists in almost every company that grew its real estate alongside its headcount and never checked whether the two still needed to move together. That's the part that travels, and it's especially relevant for fintech and banking, where CFOs are under constant pressure to fund digital transformation, fraud prevention, and regulatory technology while operating margins stay tight. A program that funds its own infrastructure investment out of savings it generates elsewhere, rather than competing for scarce digital budget, is a capital efficiency story as much as a facilities one.

Start With the Data, Not the Floor Plan

The most important decision in this program was refusing to guess. Before touching a single seat, the team ran daily occupancy reports across the target locations, for weeks, capturing actual usage day by day rather than a one-time headcount.

That mattered because occupancy doesn't hold steady. It swings by day of week, by team, by season, and around month-end or quarter-end reporting periods, which look nothing like an ordinary Tuesday in a bank. A single snapshot would have missed all of that. Running the numbers daily over an extended window did three things: it gave a real baseline for peak and average utilization, instead of relying on assigned-seat counts that were often years out of date; it flagged locations and teams that genuinely ran hot, protecting the program from a blanket cut that would have caused real disruption; and it gave the team a case built on evidence rather than a directive handed down from above, which made it far easier to get buy-in from business unit leaders who might otherwise have resisted losing dedicated seats.

Only after that groundwork was the program ready to move, on three fronts at once:

Rationalize space based on what the data showed. Each of the 200 locations was modeled individually to see where allocation could safely drop from 100% to 80%. Not a uniform cut applied everywhere, a location-by-location call, backed by numbers.

Turn dead space into flexible capacity. Instead of simply shrinking the footprint, the program converted underused cafeteria and library space into hoteling zones, unassigned desks anyone could book for the day. That broke the link between "seats available" and "seats paid for," letting the bank absorb occasional busy days without carrying permanent extra seats year-round.

Treat the IT upgrade as part of the same decision, not a separate one. Hoteling only works if people can actually get work done from a repurposed cafeteria corner. That meant upgrading wifi and network capacity in those spaces to match the core office. Skip this step and the "flexible space" is just an empty room with tables in it, and the whole savings case falls apart.

How the Program Was Run

A program touching 200 sites across multiple countries doesn't run informally. This one was structured as a formal, waterfall-managed program, with defined phases, measure, model, build, migrate, monitor, rather than an agile, iterate-as-you-go effort. Real estate and physical infrastructure changes don't lend themselves to quick sprints: a lease doesn't get renegotiated in a two-week cycle, and neither does a wifi installation across a regional hub.

It ran formally as an IT program, with a dedicated PMO owning overall governance, reflecting where the real coordination burden sat: rolling out infrastructure consistently across 200 sites in different countries, each with its own local teams, vendors, and regulatory quirks.

Four groups sat at the center of execution:

CRE, which owned and validated the occupancy targets for each site, using data pulled and shared with them site by site.

Local IT support teams, who delivered the wifi and network builds, working through local vendors and regulatory requirements far better understood on the ground than from a central team.

Security, involved as a standing stakeholder from day one rather than a final sign-off gate. Every new wifi zone had to meet the same standards as the core office network: proper segmentation between hoteling traffic and internal systems, encryption, and controls that would satisfy internal audit and external regulators. In a regulated financial institution, connectivity expansion at this scale without security embedded from the start isn't a program, it's a future audit finding.

HR, which owned the human side of the rollout: employee communication, updated hoteling and desk-booking etiquette guidance, and gathering informal feedback on how the new space was landing, so friction points surfaced early instead of showing up as complaints after the fact.

Governance ran on two tracks: steering committee meetings brought CRE, IT, PMO, HR, and Security together to track progress and resolve cross-functional conflicts, while individual technical program meetings handled site-by-site execution detail, infrastructure specs, scheduling, vendor coordination, and security sign-off. That two-tier structure kept strategic decisions and daily execution from tangling into the same meeting.

Phase one, covering the full 200 sites end to end, ran for roughly two and a half years.

What Went Wrong

No program touching 200 sites across multiple countries and continents runs cleanly, and this one is more useful as a case study because it didn't.

Coordinating across countries and continents was the single biggest challenge. Time zones, language, local working norms, and simply keeping teams on three or four continents aligned to one timeline created constant friction. What looked simple in a steering committee slide, "upgrade wifi at 200 sites," turned into 200 separate local negotiations in practice.

Hardware shipment and timelines were a recurring headache. Equipment ordered centrally didn't always arrive on schedule, and delays at one site had a way of cascading into the sequencing of others.

Import laws varied site by site. Equipment that shipped and installed without friction in one country ran into customs delays or certification requirements in another, forcing the program to build in buffer rather than assume a uniform process anywhere.

Lease terms across 200 sites were far from uniform. Understanding what each site's lease allowed, and where occupancy changes intersected with lease covenants, took real legal and CRE effort site by site. There was no shortcut around reading the fine print 200 times.

"What looked simple in a steering committee slide, 'upgrade wifi at 200 sites,' turned into 200 separate local negotiations in practice."

None of this derailed the program, but it's why it ran on formal, waterfall governance with a dedicated PMO rather than a looser effort. At this scale, coordination overhead isn't optional. It's the job.

The Payoff

CRE funded this initiative, and it paid the bank back many times over. This wasn't a cost center quietly absorbing an IT upgrade as a favor to the business, it was CRE putting its own budget behind a program that became one of the strongest-performing investments the function made during that period. The global savings target was roughly $200 million, and the program achieved it, without shrinking the effective capacity available to employees on a busy day.

The savings held up because the program avoided the two things that usually kill a CRE cost-cutting effort: employees ended up with more usable space, not less, so morale never became the story, and the bank never had to force lease terminations faster than the business could absorb, since the savings came from using space better, not from a rushed exit.

This is also what sets the approach apart from the usual CRE playbook of subleasing, market exits, or headcount-driven cuts, each of which comes with real friction of its own. This program didn't reduce headcount, exit any market, or wait on a subleasing market to cooperate. It changed how existing space was used, backed by data, and funded a relatively modest infrastructure investment to make that change work. That's a materially lower-disruption path to the same financial outcome, and a more repeatable one.

The Employee Experience

A program like this lives or dies on whether people actually use the new space, and the response here was genuinely positive. Employees liked the shift away from being tied to a single, fixed desk all day. The hoteling model gave people the freedom to work from a cafeteria corner, a library zone, or a traditional desk depending on what suited the day, rather than being anchored to the same seat regardless of what they were doing. That flexibility, paired with wifi performance matching the core office, meant the new space options got adopted rather than avoided, which is what made the occupancy math hold up in practice rather than just on paper.

The Sustainability Angle

A 20% reduction in dedicated occupancy across 200 of a bank's costliest sites isn't only a cost story, it's an environmental one. Less dedicated space generally means lower energy consumption for heating, cooling, and lighting, and a smaller footprint reduces the operational carbon footprint tied to facilities. For a global bank, that has value beyond the balance sheet: environmental impact from corporate real estate is an increasingly visible line in ESG reporting, and banks face growing pressure from regulators, investors, and rating agencies to show measurable progress there. A program that improves the cost line and the environmental line at once gives CFOs and sustainability officers a rare joint win to report, and it's worth featuring as a secondary benefit whenever this kind of program gets pitched.

Why This Matters Specifically for Fintech and Banking

Beyond the sustainability angle, three things about this program are worth calling out for fintech and financial services readers specifically:

Compliance was designed in, not bolted on. Security sat as a standing stakeholder throughout. In banking, any infrastructure change touching network access, even cafeteria wifi, is a compliance surface, and readers in this space will recognize immediately whether a program treated security as core design or as an afterthought.

Self-funded programs are a different pitch to the board than typical cost-cutting. Most cost programs in banking compete for the same budget as fraud prevention and regulatory technology spend. A program that generates its own return, funded by the function that benefits, is a materially easier story to fund, and a stronger one to publish, because it shows financial discipline rather than belt-tightening.

The regulatory and multi-jurisdiction complexity is itself the fintech story. Import laws, lease variation, cross-border coordination- these are the same categories of friction that show up in every large-scale fintech infrastructure or compliance initiative. Readers running similar programs will recognize these obstacles immediately.

From a Single Office to a Global Portfolio

What makes this transferable is that it never depended on scale, it depended on measuring before cutting.

A small company with one office can run the same exercise at a fraction of the size, using a few weeks of daily headcount-versus-seats data to show that a meeting room or quiet corner is sitting empty and could become bookable space, with maybe a wifi extender as the only real cost. A mid-sized company with a handful of regional offices can prioritize by lease renewal dates or wherever cost pressure is worst, then run the same model site by site. A large or global company can apply it at portfolio scale by ranking every location by CRE cost first, exactly as this bank did, then use the data to build a business case solid enough for the board, with the program governance to execute it across borders.

The sequence never changes: measure real usage daily, for a real stretch of time. Model site by site. Convert underused space into flexible capacity instead of just cutting it. Treat the IT upgrade as part of the real estate decision, not an afterthought. Skip the measurement step and it's not a data-driven decision, it's a guess, and guesses get reversed the first time a business unit complains.

What's Next

Phase one ran for roughly two and a half years, start to finish. Having proven the model and hit its savings target, the bank moved into a phase two, targeting the next 200 highest-cost sites using the same measure-first approach. That renewal is itself a signal worth noting: the strongest evidence a cost program worked isn't the first-phase savings number, it's whether the organization trusted the model enough to fund a second round.

The Bigger Point

Real estate and IT used to be treated as separate budgets, managed by separate teams. This program worked because several things came together at once: sustained daily data, a facilities decision, an IT decision, and cross-functional governance disciplined enough to hold 200 sites across multiple countries to the same standard. For any company with a meaningful real estate footprint, whether that's one building or two hundred, the takeaway is the same: cutting occupancy cost isn't a real estate project or an IT project, it's one project, built from measured behavior rather than what the org chart assumes.

NOTE: This Article is a thought leadership piece by Rethish Nair Rajendran (Senior Project Manager) - New York, United States, who played a key leadership role in this program.

Published by HT Digital Content Services with permission from VC Circle.