Register Waitlist

Playbook

Boutique hotels

You are running six systems that do not talk to each other, and the reconciliation between them is somebody's entire job.

Boutique hotels
01

Who this is for

You are an independent boutique property or a small group — enough rooms to have a revenue pattern, more than one outlet, a housekeeping team, and a finance person tired of exports. Possibly more than one property, which is where roles and scopes stop being theoretical.

The Room Rack in Nerve: one row per room, grouped by type, with coloured bars spanning the nights each room is taken across a July date range.
Every room and every night in one grid — the view the desk actually works from.
02

What you switch on

And why this module, for this kind of property — not the generic description.

  • Front Desk

    The full desk: rack, arrivals and departures, folios, group billing, and stay-time policies three levels deep — so a rate plan that includes a late check-out is a policy rather than a note somebody has to remember.

    See the module →

  • Reservations

    One availability truth, channel ceilings that shape distribution without touching real inventory, and a queue that tells you when a rate push did not land.

    See the module →

  • Housekeeping

    A board the team works from, and a readiness gate the desk cannot silently step around.

    See the module →

  • Accounting

    Postings that come from operations rather than from re-keying, receivables that reconcile one remittance against several open items, and a night audit that closes the day.

    See the module →

  • Revenue

    Occupancy, ADR and RevPAR that name the base they were computed from, pace against the prior period, a forecast per night, and rate recommendations you accept or dismiss with the reasoning in front of you.

    See the module →

  • Point of Sale

    More than one outlet, one catalog. Checks settle to a folio, a card or an event account, and the day will not close while a check or a drawer is still open.

    See the module →

  • Settings

    Roles at a scope, an audit log covering people and keys, and step-up on refunds and voids. At this size that stops being paperwork and starts being how you sleep.

    See the module →
03

What you can ignore

This section is the point of the page. A product that needs all of itself at every size is not a product that fits you.

  • Inventory

    Worth switching on when you want recipe-level food cost and a valuation that reconciles to the movement ledger. With one outlet and a short menu, the POS catalog carries the weight — start there, and add Inventory when the kitchen becomes the question.

  • Partner Portal

    You operate your own property. The portal is for organisations that operate other people's.

04

A Thursday

  1. The rack shows a tight night. The forecast for it was a red pill three weeks ago, and the rate recommendation that came with it was accepted then.
  2. A group checks in against a master folio, with the billing split set per stay and a total row reconciling the master against the guests.
  3. The bar closes. Its checks settled to folios and cards, the drawer closes against what was taken, and the outlet day closes because nothing is left open.
The Demand forecast table in Nerve, one row per night, each showing the occupancy already on the books, a colour-coded forecast occupancy pill, and the forecast rooms out of a fifteen-room house.
A forecast per night, next to what is already booked for it.
05

What you already have

A channel manager's worth of channels, an accountant, and whatever your bank sends as a remittance file. The receivables screen matches one remittance against several open statements, which is where most of that reconciliation used to go.

Sound like your property?

There is nothing to install and nothing to migrate before you have seen it.

Register Waitlist →Read the docs →

← All property types