LOBBY
Comparisons· 6 min read

Conference Room Scheduler Software: A Feature Checklist for Offices Under 150 People

Most conference room scheduler checklists are written for 2,000-person estates and then sold to offices of 60. This one is calibrated to under 150 people: four features that are essential, four that are genuinely useful, and seven that are usually oversold at that size.

Almost every feature checklist in this category was written with a 2,000-desk estate in mind, then handed to an office manager at a company of sixty. That is why the demos feel impressive and the quotes feel absurd. You are being scoped against a building you do not have.

Size changes which features earn their keep. Under about 150 people you typically have somewhere between four and eighteen bookable rooms, one or two floors, one IT person or none, and no facilities team. In that setting most of the feature list is inert, and a few things matter enormously.

What follows is the same checklist sorted three ways: essential, useful, and usually oversold at this size. The last group is the interesting one, because none of those features are bad. They are just priced and sold as though you were four times larger, and for each one there is a specific point at which it flips to essential. Those points are named below.

Essential under 150 people

Real two-way calendar integration

The scheduler must read your existing room resources in Google Workspace or Microsoft 365, and a booking made anywhere must be a real event on the room's calendar. Not a row in the vendor's database that syncs on a five-minute job.

The failure mode of a shadow booking table is the one that destroys trust in the whole system: someone books in Outlook, the sync lags, and the panel outside the room says free while four people are inside it. Once that happens twice, people stop looking at the panel, and you are paying a subscription for wall decoration. If you are writing a formal spec, the one-page requirements document has the exact wording to send vendors.

Room status where people actually get confused

Not every room. The rooms with solid doors, the rooms off a corridor, the phone booths. A glass-walled room where you can see whether it is occupied does not need a panel, and buying one for it is how a six-room office ends up with a nine-panel quote.

Walk the floor at 11am on a Tuesday and note where people hesitate. That is your list. Everything else can wait.

Automatic release of no-shows

The single feature with the clearest return. Rooms booked and not used are the reason a company with enough rooms believes it has too few, and the arithmetic on ghost meetings is worth reading before you conclude you need to knock a wall through.

Requirements: configurable delay, per-room override, and released time returning to the calendar as genuinely free within seconds. Ask specifically whether the event is deleted, declined or shortened, because those three behaviours produce very different amounts of internal noise. The mechanics are in how to release a meeting room automatically.

Self-serve setup

You should be able to connect the calendar, add rooms and see a display working without a sales call, an implementation partner or a professional services fee. At your size there is no budget line for a three-week deployment project, and more importantly there is nobody to run it.

The honest counterpoint: self-serve products tend to have thinner support when something does go wrong, because the business model assumes you will not need it. If your one IT person is already at capacity, a vendor with a real support desk may be worth the premium. Decide that deliberately rather than by accident.

Genuinely useful, worth paying a bit for

Check-in

Useful, but only as the trigger for auto-release rather than as a policy in its own right. Mandatory check-in with no grace period produces its own failure: the room releases while the organiser is walking up from reception, and someone else takes it.

A Slack or Teams booking route

Most bookings do not happen at the door. They happen in a thread where someone says "can we grab a room". A /book style command removes a context switch, and it is the feature people at this size use most after the panel itself. More on that in booking meeting rooms from Slack.

Basic utilisation data

Four numbers are enough at this size: bookings per room per week, average booked duration, no-show rate, and peak hour. That is sufficient to answer "do we need another room" and "is the big room being used for two-person calls". Anything more granular is a report nobody opens. We went through what is worth measuring in meeting room analytics.

Room attributes and capacity

Capacity, screen, whiteboard, video kit. Cheap to configure, and it stops the four-person standup taking the twelve-seat room. Pairs well with a sane naming convention, which does more work than most software features and costs nothing.

Usually oversold under 150 people

None of these are bad features. They are features whose value scales with building complexity, and at your scale the complexity is not there yet.

Floor plans and interactive maps

A map solves wayfinding. In a single-floor office of sixty people, nobody is lost. Everyone knows where Copenhagen and Aarhus are by their second week.

Flips to essential when: you pass roughly three floors or two buildings, or when a majority of staff are in the office fewer than three days a week and no longer have a mental model of the layout.

Occupancy sensors

Sensors are sold as the fix for no-shows. Auto-release from calendar data solves most of the same problem at a fraction of the cost and with no hardware to maintain. Sensors also add a data protection question you then have to answer internally. The comparison is set out in occupancy sensors versus calendar data.

Flips to essential when: you need evidence for a lease or fit-out decision with real money attached, or when you have rooms people occupy without booking at all, which calendar data structurally cannot see.

Desk booking bundled in

Desk booking is a different problem with a different failure mode, and bundling it usually means paying per employee for a room product. If you have assigned desks or a stable office, it is dead weight. The distinction is in desk booking versus room booking.

Flips to essential when: your desk ratio drops below about 0.8 desks per employee and people genuinely cannot rely on finding a seat.

Visitor management bundled in

If you have a staffed reception, an iPad sign-in kiosk is solving a problem you already solved with a person.

Flips to essential when: reception is unstaffed, or you have a compliance requirement to produce an evacuation list of everyone in the building.

AI booking suggestions

With eight rooms, the search space is small enough that a human solves it instantly. The suggestion engine needs a corpus of behaviour to be useful, and at forty bookings a week it does not have one. Our view on where this does work is in AI meeting room booking.

Flips to essential when: you have enough rooms across enough floors that finding the right one is genuinely a search problem, which in practice is well past 150 people.

Delegated multi-site admin

Role hierarchies exist so that the Berlin office manager cannot rename Copenhagen's rooms. With one site and one admin, that is a solution without a problem. Worth revisiting when you get there, and we have covered it in managing meeting rooms across multiple offices.

Flips to essential when: you have a second site with its own office manager, which is usually the moment the second lease is signed rather than any headcount number.

SSO and SCIM

The one that most often forces an upgrade to an enterprise tier. Worth being precise about who actually logs in: for most room scheduling products it is two or three admins, not the whole company. Staff booking a room from a panel or from Slack are not authenticating against the scheduler at all.

Flips to essential when: your security policy mandates SSO on every SaaS tool without exception, or when you have enough admin turnover that manual deprovisioning is a real risk. That is a policy trigger, not a size trigger, and it can hit at forty people.

Where Lobby fits

Lobby is built for exactly this band, which is both the recommendation and the warning. It reads Google Workspace and Microsoft 365 room resources, offers a 7.5-inch e-ink panel by the door at USD 69 per unit for 1 to 9 units, dropping to USD 62.99 at 10 or more, bought direct from the manufacturer and owned outright with no markup from us, a virtual display which is the same view as a URL in any browser tab on hardware you already own, and a room overview board that counts as one display. Pricing is flat: free forever up to 3 active displays with no credit card, then USD 30/month billed yearly (USD 360/year) or USD 50 month to month for Unlimited, and USD 60/month billed yearly (USD 720/year) or USD 100 month to month for Pro Unlimited, which adds the Slack /book command, custom templates, your own logo, room feedback and a 5-minute e-ink refresh. Setup is under ten minutes with no sales call and no professional services fee.

The limitations map directly onto the oversold list above, and that is not an accident. Lobby has no floor plans, no occupancy sensors, no room automation or AV control, no enterprise SSO or SCIM at scale, no MDM on the e-ink hardware and no on-premises Exchange without a hybrid setup. Calendar access is read-only, which is a real constraint against the first item on the essential list above: Lobby reads your room resources and never writes to them, so the booking itself is always made in Google Calendar or Microsoft 365, including when the Slack /book command hands you a pre-filled event to save. If any of those items has already flipped to essential for you, the honest answer is that a larger platform is the right purchase and you should stop reading here.

Visitor management and desk booking are coming soon, so you can run your whole office from Lobby: rooms, visitors and desks on one plan.

TL;DR

  • Four things are essential under 150 people: real calendar integration with no shadow booking table, status displays only on the rooms where people actually hesitate, configurable auto-release of no-shows, and setup you can do yourself without a sales call.
  • The shadow-database failure mode is the one that kills adoption. A panel showing free outside a full room twice is enough for people to stop trusting every panel in the building.
  • Auto-release beats sensors for the no-show problem at this size, at a fraction of the cost, but it cannot see rooms people occupy without booking. That is the specific gap sensors fill.
  • Four features are worth paying a little more for: check-in as an auto-release trigger, a Slack or Teams booking route, four utilisation numbers, and room attributes with capacity.
  • Floor plans flip from oversold to essential at roughly three floors or two buildings, not at a headcount.
  • Desk booking flips when your desk ratio drops below about 0.8 per employee. Before that it is per-employee pricing on a room product.
  • SSO is a policy trigger rather than a size trigger, and for most room schedulers only two or three admins ever log in. Check that before paying for an enterprise tier over it.
  • Self-serve products usually have thinner support. If your one IT person is already stretched, that premium may be the right thing to pay for.

Related reading

Sources

Prices verified 11 August 2026. Tier-based and quote-based pricing changes, so confirm directly with each vendor.

Try Lobby — free forever up to 3 displays

Room booking that just works.

Get started →