Demand Manager
Turn quiet periods into targeted booking opportunities.
Detects future spare capacity and recommends an approved offer to a suitable existing audience, stopping outreach as the allocation fills. Capacity, margin and eligibility are calculated by fixed rules, and nothing is sent until the owner approves the plan.
A real customer situation
A guesthouse has six unsold room nights midweek and a list of previous guests, some of whom have agreed to hear about offers. The owner would discount a few nights but not below what covers cleaning, linen and breakfast, and does not want to keep advertising once the rooms are gone.
Where the owner wants to be
Quiet nights are offered to the right past guests at a price that still earns a set contribution, the owner signs off once, and outreach stops by itself when the allocation is sold.
What it handles
- Finds unsold nights in a date window and caps the offer allocation at real inventory
- Filters the audience on consent, opt-out, recent contact and existing bookings
- Checks the offer against the margin floor and states the contribution estimate with its assumptions
- Sends bounded daily batches only after owner approval, recomputing inventory before each
- Stops outreach when the allocation fills and applies the configured cancellation rule
What it deliberately does not do
- Never sends an offer below the owner's minimum contribution
- Sends nothing without explicit owner approval
- A cancellation does not restart outreach unless the owner configured that rule
- The public demo sends no messages and holds no rooms
Interactive demo
Try it with sample data
No sign-up needed. Pick a scenario, change the inputs, then play the customer and the owner. The right-hand panel only shows what the workflow actually recorded.
Interactive simulation using a sample guesthouse calendar and guest list. No offer is sent, no room is held and no booking is taken.
Choose a scenario
25% offer to previous guests with a four-night allocation. Book nights and watch outreach stop when full.
Rack rate A$220; variable cost A$62 per night.
Website enquiries have no marketing consent.
Customer side · Offer email (held)
Press “Run scenario” to start. Every message and record here comes from sample data.
Workflow and harness
How Demand Manager runs
Reference schematic for the proposed workflow. Blue steps do the work, purple paths handle exceptions and returns, and amber checks are the harness controls that a step cannot pass without.
Overview — business stages
Read the full flow as text
- Detect future capacity gap (business step)
Unsold nights; allocation capped at inventory. Output: Inventory record. Leads to: Select eligible audience. - Select eligible audience (business step)
Consent, not opted out, not contacted in 30 days, not already booked. Output: Eligible audience count. Leads to: Propose offer within margin floor. - Propose offer within margin floor (business step)
Contribution per night ≥ floor; estimate with assumptions. Output: Campaign plan. Leads to: Owner approves campaign; Below margin floor. - Owner approves campaign (business step)
Explicit owner decision required. Output: Approval receipt. Leads to: Send bounded batches; Rejected. - Send bounded batches (business step)
≤ 12 per batch, ≤ 4 per remaining night, one batch a day. Output: Offer messages. Leads to: Track bookings and remaining capacity. - Track bookings and remaining capacity (business step)
Reserve each booking against the allocation. Output: Bookings, remaining inventory, contribution. Leads to: Capacity remains; Allocation filled. - Below margin floor (exception or return path)
Block; owner may revise to a compliant offer. Output: Blocked plan. Leads to: Propose offer within margin floor (revise offer). - Rejected (exception or return path)
Stop; nothing sent. Output: Rejected plan. - Capacity remains (exception or return path)
Next eligible batch on the next day. Output: Next batch. Leads to: Send bounded batches (next eligible batch). - Allocation filled (exception or return path)
Stop outreach; cancellation restarts only if configured. Output: Stopped campaign. - Price and margin rules (harness check)
Rate − A$62 variable cost ≥ floor. Output: Pass / blocked. Leads to: Propose offer within margin floor (required check). - Explicit approval (harness check)
Recorded approval before any send. Output: Approval receipt. Leads to: Owner approves campaign (required check). - Inventory before send (harness check)
Recompute unsold and allocation before every batch. Output: Remaining allocation. Leads to: Send bounded batches (required check).
Harness controls
- Owner approval before any batch is queued
- Margin floor on the offer's contribution per night
- Audience eligibility: consent, opt-out, recent contact, existing booking
- Send limits per batch and per remaining night
- Allocation and inventory recomputed before every batch
- Stop switch, and fulfilment capacity capped at unsold nights
Systems and data
Production reads inventory from the booking calendar, customer segments with consent, approved offer rules and a messaging service. The demo uses a sample calendar, a fictional guest list and an outbox that holds every message.
Demo boundary
External calls, customer messages, payments and business writes use synthetic fixtures and an on-screen outbox. The demo shows only verified demo state. Custom production connections are a paid implementation deliverable.
What gets delivered
The records your business receives
Offer email
A short note to eligible past guests with the dates, the offer rate and how to book, sent in bounded batches.
Owner approval request
Campaign plan with offer, allocation, eligible audience count, contribution estimate and the assumptions behind it.
Campaign record
Approval receipt, batches sent, bookings reserved against the allocation, remaining inventory and the stop reason.
Custom deployment
Configured for your business during a paid implementation. Integrations are confirmed during discovery, never assumed.
Your business rules
- Your rack rates, variable cost per night and minimum contribution
- Which offers are approved and how large an allocation can be
- Audience rules: consent, recent-contact window and exclusions
- Batch size, send days and the stop switch
- What happens when a cancellation reopens the allocation
Systems we connect
Measurement
We measure completed business against a baseline, not messages sent. No results are promised before discovery.
Business results
- Incremental contribution from quiet periods, not campaign message volume
- Offer nights booked against allocation
- Full-rate bookings displaced (target: none)
Operational reliability
- Messages sent after the allocation filled (target: zero)
- Offers sent below the margin floor (target: zero)
- Duplicate batch sends (target: zero)
Want this watching your own booking calendar for quiet nights?
Book a call about Demand Manager. We start with discovery: your current process, volumes, systems and who handles exceptions. The proposal then defines the integrations, approvals and acceptance tests before anything goes live.