Share this article
Most companies sign their first managed office contract without knowing what to scrutinise. The headline price is easy to compare across operators. What sits underneath it isn't.
The questions below aren't meant to interrogate the operator. They're meant to surface the things that tend to cause friction later, before they do. A confident operator will welcome them. A vague one will deflect, which is itself an answer.
1. What's actually included in the monthly fee?
Push past the brochure. Is internet bandwidth dedicated or shared, and at what speed? Is housekeeping daily or scheduled? Are meeting rooms included, or charged per use beyond a certain allowance? Are utilities capped at a particular consumption level, with overages billed back? What about after-hours access, weekend operations, and pantry consumables?
The version of "all-inclusive" varies a lot between operators. Specifics matter.
2. What sits outside the monthly fee?
The mirror question, and often the more revealing one. Some add-on items include custom branding work, additional parking slots, IT hardware beyond the baseline, specialised infrastructure (server racks, dedicated power, lab requirements), and one-time setup costs. Knowing what's on the add-on list before signing prevents the budget conversation from getting awkward six weeks in.
3. What's the payment cadence and structure?
Monthly, quarterly, or annually? In advance or in arrears? Are there any fees that work on a different cadence to the main monthly fee? Most operators converge on monthly in advance, but the variations matter for cash flow planning, especially for larger engagements.
It's also worth asking how invoicing actually works. A single consolidated monthly invoice covering rent, utilities, and services is one of the operational advantages of the managed model, but it isn't universal. Some operators bill components separately, which puts the consolidation work back on the occupier.
4. What does the exit look like?
Lock-in length, notice period, security deposit refund timeline, and any dilapidation clauses. The exit terms are easy to skim past when you're focused on getting in, but they're the terms that matter most if circumstances change.
A clean operator will commit to a specific deposit refund window (typically within thirty days of exit), a clearly defined notice period, and a transparent process for handing the space back. Ambiguity here is worth pushing on.
5. What's the expansion path?
If headcount grows, can you take more space in the same building? What's the notice requirement, and how quickly can the operator deliver additional seats? Is pricing pre-agreed or renegotiated at the time of expansion?
Most companies underestimate how often they'll need to scale, and the cost of getting locked out of expansion options is one of the quieter ways a managed office relationship can go wrong.
6. Who handles compliance?
Fire NOC renewals, lift insurance, statutory filings, building permits, GST documentation. These obligations don't go away just because the space is managed. The question is who's responsible for them, and the answer should be unambiguous.
Operators with strong in-house capability handle this transparently and absorb it into the monthly fee. Operators with weaker capability leave gaps, which become the occupier's problem at exactly the moment they're least equipped to deal with them.
7. What are the SLAs on operations?
Response times for maintenance issues. Internet downtime resolution targets. Security incident protocols. Cleaning standards. These should be defined, documented, and committed to in the agreement, not described in marketing language.
8. How does day-to-day communication actually work?
When something needs attention, whether a maintenance issue, a request for an additional seat, or a question about a meeting room booking, what's the channel? An app, a portal, a phone number, an email address, an on-site team? The practical mechanics of getting things done matter more than the org chart.
A clear answer here usually correlates with a clear operation underneath. If the operator can describe exactly how a request moves from raised to resolved, the process is probably working. If the answer is vague, the experience usually follows.
9. What does customisation look like after signing?
Even in pre-built spaces, some adjustments are usually possible: branding, paint, partition reconfigurations, minor layout changes. The question is what the operator will actually accommodate, on what timeline, and at what cost. In Enterprise custom builds, the question is different but no less important: how change requests are handled mid-project, and what the variation process looks like.
Knowing the limits upfront avoids friction later.
10. What happens when something goes wrong?
The least glamorous question, and arguably the most important. Power outage on a working day. Internet down for half a shift. AC failure in the server room at nine in the evening. A break-in. A water leak. The operator's posture on these moments tells you everything about what the relationship will feel like.
Ask for examples. A confident operator will have them, and will describe how the situation was handled with reasonable specificity. A vague answer here is the signal worth paying attention to.
A note on what this isn't
These questions aren't a stress test. The goal isn't to find a reason to walk away. The goal is to surface the operational realities that the monthly headline price doesn't cover, so the comparison between operators is honest and the eventual relationship starts from a clear baseline.
Vestian Spaces is structured to answer these questions concretely, which is partly a function of the offering being built on top of Vestian's broader work in transaction management, design and project services, and facility management. The same team that builds the space runs it, which collapses the usual ambiguity about who's responsible for what.
If you'd like to walk through any of these questions specifically, get in touch.
