Share this article
Most people in a company think running an office means paying rent. The person who actually runs it knows otherwise.
Behind a working office is a constant stream of small problems, vendor calls, statutory obligations, and minor crises. Most of it never makes it onto anyone's job description. None of it is hard in isolation. All of it adds up, and most of it consumes the time of people whose job is supposed to be something else.
This is a look at what that work actually is. Not as a sales pitch for moving to a different model, just an honest description of the layer that sits between a building and a functioning office.
The vendor layer
A working office relies on a roster of specialist vendors, each handling one piece of the operational stack. HVAC servicing. Plumbing. Electrical maintenance. Lift maintenance. Pest control. Fire system testing. Water tank cleaning. Generator servicing. Security agency. Housekeeping. Pantry supplies. Office stationery. Internet service provider. Building management coordination.
Each of those is a separate contract, a separate point of contact, and a separate negotiation when the contract comes up for renewal. Coordinating them isn't optional; it's the work. Someone has to make sure the AC service team shows up on Tuesday, the fire drill is scheduled before the certification expires, the housekeeping shift starts before the team arrives, and the pest control contract doesn't lapse before the monsoon.
In a typical mid-size office, this is fifteen to twenty active vendor relationships. In a larger setup, more.
The day-to-day operations
The vendor layer is the recurring part. Day-to-day operations are the constant part.
Consumables procurement, ordering paper, soap, coffee, tea, pantry supplies, stationery, before they run out. Utility payments, tracking and paying electricity, water, internet, and telephone bills, each on its own cycle. Internet escalations, every time the connection drops below acceptable speeds or fails altogether. Security rostering and shift handovers. Visitor management. Mail handling. Courier coordination. Reception coverage. Meeting room bookings, conflicts, and reshuffles.
None of it is complicated. All of it requires attention. Most of it doesn't surface to leadership until something fails, at which point the failure is the only thing visible.
The compliance layer
The least glamorous part of the work, and the part with the highest downside risk if it gets neglected.
Fire NOC renewals on the cycle defined by the local authority. Lift insurance renewals. Building permits and occupancy certificates. Statutory filings, including labour-related obligations for staff working on site. GST documentation for the property and its operations. RERA compliance where applicable. Periodic audits and inspections.
Most of this is manageable when someone is actively tracking it. The problem is that none of it is urgent until it's overdue, and the consequences of being overdue, fines, operational disruptions, insurance gaps, can be disproportionate to the effort of staying ahead of it.
The breakdown moments
The work above is at least predictable. The breakdown moments aren't.
The 9 PM call about the AC failing in the server room before a critical demo the next morning. The Monday power cut that takes down the office for half a day. The plumbing issue in the women's washroom that needs solving by 11 AM. The internet outage during a board meeting. The water tank leak that floods the cafeteria. The break-in that wasn't supposed to be possible. The fire system that goes off because someone microwaved popcorn.
Each one of these takes someone's full attention for somewhere between an hour and a full day. The cost isn't the resolution; it's the disruption to whatever that person was supposed to be doing instead.
Who actually does this work?
The answer varies by company size, and tells you something about where the operational burden lands.
In larger companies, there's usually a dedicated admin or facilities team. The work is real, but it's at least sitting in the right place, with people who are trained to do it and budget assigned to it.
In mid-size companies, the work often falls to one overstretched admin head, or a senior assistant who's also doing five other things. The cost shows up as quality, certain things get done well, others get deprioritised because no single person can do all of it at the level the business actually needs.
In smaller companies, the work falls to whoever's available. A founder takes the AC call at 9 PM because there isn't anyone else to take it. A COO ends up negotiating the housekeeping contract because someone has to. The work gets done, but it's getting done by people whose time costs the business much more than the work is worth.
In every case, the question isn't whether the work happens. It's where in the organisation it lands, and what gets crowded out as a result.
The case for putting it somewhere else
This isn't a hard pitch. Plenty of companies handle the operational layer themselves, well, and it's a defensible choice. Direct control over vendors, full visibility into the operational stack, and no margin paid to a service provider sitting in between.
But for companies where the calculation tilts the other way, where senior bandwidth is the scarce resource, where the business is moving faster than the office can keep up with, where the operational work has started crowding out higher-value work, the case for moving the layer somewhere else is reasonably straightforward. The work doesn't disappear; it gets done by people whose primary job is doing it, on terms defined upfront, under a single contract.
That's what Vestian Spaces is built to do. The same team that delivers the space runs it, handling facility management, vendor coordination, compliance, and the breakdown moments, on a single monthly fee. The point isn't that running an office in-house is wrong. It's that the operational layer is real work, and for the right kind of company, it makes sense to put it with someone whose job is doing it.
If your admin head is spending their week on vendor calls instead of the work you actually hired them for, that's the signal. Get in touch and we'll walk through what moving the layer looks like in practice.
