The conversation that happens in a one-property operation feels nothing like the conversation that happens at thirty. At one unit, the operator is the concierge, the cleaner, and the escalation path. At thirty, the operator is the routing layer — the person who decides which conversations need them, which conversations need a junior team member, and which conversations are routine enough to be handled by prepared, approved drafts.
Four flat pricing bands reflect this same progression. Active properties 1–3 cost $15 USD per property/month, 4–9 cost $10 USD, 10–29 cost $7 USD, and 30+ cost $5 USD. The selected band rate applies to every active property, so 5 properties cost $50 USD/month and 30 properties cost $150 USD/month. Every customer starts with the same free 14-day, one-property pilot: no card, no charge during the pilot, no automatic conversion, and explicit consent before paid billing.
One to seven units — the concierge operation
At one to seven units, the operator is the operation. They know every property, every guest’s name on arrival day, every local contact they have built up over seasons of hosting. The conversation they have with each guest is personal because the team is small enough to make it personal — there is no need to standardize what one human can carry in their head.
Standardization is still useful at this size, but it is a different kind of standardization. The operator usually wants faster inputs (a pre-built reply template for the Wi-Fi question, the same way to write a check-in line). What they do not need is a routing layer — every inbound message is one person’s decision. The tool at this band is a typing accelerator plus a draft review queue, not a triage engine.
Eight to twenty-nine units — the routing layer
At eight to twenty-nine units the operator stops being able to answer every message themselves. Some messages need a junior team member. Some messages need a regional manager. Some messages need a property-specific contact. The operator becomes the routing layer — the person who decides who owns the next step on each message, not the person who types out the next step in every thread.
This is the band where audit history first becomes load-bearing. With more than one person handling outbound messages, the team needs a record of who approved what, so an outside reviewer can answer "who decided this?" with a name. Per-property context also becomes important — the right answer for the eight-unit message is rarely the same person’s approval as the right answer for the twelve-unit message, even if they read similar in the inbox.
The 10–29 band adds per-property context, escalation routing, prepared drafts in the operator’s voice for routine questions, and a paper trail for every outbound message. The selected $7 USD/property/month rate applies to all active properties in that count.
Thirty plus — the multi-manager operation
Past 30 units the conversation changes shape again. Multiple regional managers may own different segments of the portfolio. Multiple properties may share a host but rotate through team rosters. The operator who started at one unit is now running a small operations group, and the layer they need is closer to an operations desk than a concierge tool.
At 30+ properties, the same self-serve pilot and flat $5 USD/property/month band apply. The selected rate, monthly total, consent timestamp, and version stamps are recorded before checkout so the operator can review the exact amount and terms.
The free 14-day, one-property pilot is shared across every portfolio band. It never charges a card and never converts automatically; the operator must explicitly approve the displayed price and payment terms before a paid subscription begins.
Coordination, voice, and audit history across a growing portfolio
Three things change shape as the portfolio grows. Coordination — how the team agrees who handles a message. Voice — how the team agrees what the messages say, even when more than one person is sending. Audit history — how the team keeps a record of which decisions were made by whom.
Coordination is the first thing that breaks. A one-person operation does not need to coordinate. A four-person operation does. A thirty-property operation across three regional managers absolutely does — and the answer cannot be "every message comes to the operator," because the operator’s job is now to be available for the messages that actually need them.
Voice is harder than coordination. Two team members handling the same property at different times will, by default, write different replies to similar messages. Consistency over weeks adds up; inconsistency shows up in guest reviews. The fix is not more copy-paste; it is a per-property style profile and an approval-first workflow so the operator maintains the voice even when the typing is distributed.
Audit history is the layer no one thinks about until something goes wrong. Then it is the only thing that matters. A message that should not have been sent, a refund that should not have been approved, an escalation that should not have been routed to a junior — these are all questions where the paper trail is the answer. The right workflow keeps the prepared draft, the approval or rejection, and the outbound message together, so "who decided this?" is read off a log.
Where the Approve & Send workflow fits
The Approve & Send model works across all four bands, but the way it is used changes. At 1–3 properties it is mostly a speed improvement. At 4–9 and 10–29 it becomes a coordination layer with property context, routing, and audit history. At 30+ it is an integral part of how the operations desk runs, with the same flat USD pricing and explicit-consent checkout.
Pricing bands follow the same flat formula: active property count × selected band rate. The published rates are $15 USD/property/month for 1–3, $10 USD for 4–9, $7 USD for 10–29, and $5 USD for 30+; the right workflow scales with the band while the operator remains the entity every layer resolves to.