Section 3

Before you buy Getting started

What a 30-day rollout actually looks like

The work that decides whether a workplace platform sticks happens in the first month, and most of it is not technical.

Content reviewed: September 2026

Floor plan demonstration showing rooms and desks arranged on an office layout

Why this happens

Week one is naming, not configuring

Wrong names break search — rework follows.

Name buildings, floors and resources first.

Add a building and its floors

Identity comes before policy

Write rules before people sync — directory shifts under you.

Sync people from Microsoft 365 or Google first.

Sync people from Microsoft 365

Start with fewer rules than you want

Launch with rules you can explain in one sentence.

Check-in on scarce rooms only — add rules later.

How check-in and no-show work

A pilot floor buys the objections early

One pilot floor surfaces issues while fixes are cheap.

Named champions on one floor before estate-wide rules.

How to add a room
Impact

Who pays for this today

The same problem costs each group something different — and they rarely compare notes.

Common questions

For a pilot floor and one site, yes. Multi-site rollouts usually repeat the same four-week pattern per site rather than extending one long project.

Unresolved naming, and waiting on a directory or calendar permission that nobody owned. Both are avoidable if raised in week one.

Yes, and most teams do. Booking first, then visitors, services, devices and signage as each is needed.

Floor plan demonstration showing rooms and desks arranged on an office layout
Smiling workplace professional in front of an office floor plan schematic
Next step

See it against your own rooms

Walk through your estate, your booking rules and your calendar setup with our team — or start free and try it on one floor.