Every meeting.
One screen.
The digital revenue meeting. Twelve data tiles, an AI-generated narrative, captured decisions, automatic tasks — all bound to the snapshot the meeting actually ran on. Frozen forever.
Most revenue meetings spend the first ten minutes pulling numbers. Then ten more deciding which numbers matter. Then someone takes notes that nobody re-reads. This is the surface for the meeting itself — and the audit trail of every decision it produces.
No more 'pulling the numbers' for the meeting.
Open the meeting. The twelve tiles are already loaded — current performance, plan-versus-actual, daily breakdown, channel mix, search demand, top-searched dates, monthly turnover comparison, pickup trend and velocity. The AI summary is already drafted. The previous meeting's open decisions are at the top.
The team walks through the agenda on the screen they already opened, captures decisions as they happen, and closes the meeting with every action assigned to an owner. No second tool, no shared document, no parallel note-taking.
- Three meeting types — weekly · monthly · ad_hoc
- Three statuses — planned · closed · cancelled (with reason)
- Eight participant roles — owner · GM · revenue_manager · sales · marketing · FO · finance · other
- Email reminder 2 hours before — automatic, every participant
- Carry-over banner on new weekly — "previous meeting closed with 3 open decisions"
Every signal the meeting needs.
The dashboard is built on the same tile architecture as Insights — every tile loads in parallel and renders as it lands, frozen against the snapshot the meeting was created on. Switch revenue type or pickup-window from the toolbar; every tile reflows. Refresh to the latest snapshot if fresher data has landed since the meeting started.
Frozen snapshot semantics: a meeting documents a moment. Clicking refresh is a deliberate, audited act — not a random reload — so anyone re-opening the meeting six months from now sees the data the decisions were actually made on.
- Time pressure — days + weekends remaining
- Monthly performance — RN, occupancy, revenue + pickup delta (7/14/30 d)
- Plan vs Actual — budget compared against current OTB
- Correction need — gap to plan, daily required, required ADR
- Daily breakdown — table with pickup tooltips (individual/group, guaranteed/tentative)
- Channel — donut + list with share %, ADR, pickup
- Trend — period turnover summary, required ADR, pickup intensity
- Pickup history (chart) · Search history (chart)
- Top searched dates — five dates the booking engine surfaced
- Monthly turnover comparison — current vs LY same-point vs budget
- Monthly pickup trend — YoY pickup comparison
The narrative is drafted before the meeting starts.
When you create the meeting, the AI summary is queued in the background. By the time the team arrives, the narrative is on the screen: where you stand, what the same-point YoY view says, which days underperform, what the AI thinks the risks are. Written in the user's language.
Open the editor and edit it — add management commentary, override what the AI noticed, replace what doesn't matter. The summary stays attached to the meeting forever; future searches can find any phrase from any past meeting. Fresh upload? A new AI draft regenerates against the new snapshot; the old one stays visible while the new one builds.
- Background generation — the meeting opens instantly; the AI narrative arrives within a minute
- No duplicate runs — only one AI summary per snapshot; collisions are blocked automatically
- "Generating…" status chip on the tile — old summary stays visible meanwhile
- Rich-text editor — manager can rewrite, extend, or fully replace the AI text
- Same input as the 12 tiles — the AI sees the meeting's numbers, never the hotel name
- Cost-aware — the AI only re-runs when a fresher snapshot is loaded
April 25–30 is underperforming vs Budget (−32 RN); OTA share is 8 points higher than last-year same-point. Two pieces of good news: corporate pickup is +9% YoY, and the May 1–3 long weekend is pacing +4 RN ahead of last year.
- OTA dependency is up — worth investigating why direct bookings are softening
- End-of-April is weak — needs a price move or a marketing push
The decisions are the output.
The bottom half of the meeting page is the decision table. Add a decision with the form — title, type (pricing · restriction · sales_action · marketing_action · channel_mix · other), description, priority, owner, due date, affected period. A template gallery pre-fills the typical shapes — Price Increase, Min-Stay, Corporate Push, Campaign — so the form goes from blank to ready in one click.
Every decision with an owner becomes a task automatically. The owner gets an email, sees the task on their My Tasks page, and the task stays in sync with the decision in both directions — closing the task closes the decision, cancelling the decision cancels the task. The decision also shows up on the Revenue Track, filterable to meeting-sourced decisions.
- Six decision types — pricing · restriction · sales_action · marketing_action · channel_mix · other
- Template gallery — price_increase · minstay · corporate_push · campaign · custom
- Priority — low · medium · high (carries to the auto-generated task)
- Bi-directional sync — task done → decision done · decision cancelled → task cancelled
- Inline status flip — planned → in_progress → done on the meeting page table
Every meeting. One backlog. Traffic-light health.
The list page surfaces four KPI cards at the top: meetings this month, open meetings, total open decisions across all meetings, overdue tasks. Beneath them, a filterable table — date / period / type / health / status / decision counts / linked forecast / created-by.
The health indicator is the diagnostic: 🟢 healthy (no open decisions), 🟡 attention (open decisions exist), 🔴 critical (an overdue task or a high-priority open decision). At a glance, the GM can scan five meetings and know exactly which two need a closer look.
- 4 KPI cards — this month · open meetings · open decisions · overdue tasks
- 6 filters — date-range · period · type · status · participant · free-text
- Health column with traffic-light indicator on every row
- Forecast attachment — the meeting can carry an attached forecast version (decision provenance)
- Close pre-check — the close action warns about open high-priority decisions or overdue tasks before it lets you finalize
Five scenarios. Five meetings.
The Revenue Meeting isn't a quarterly thing. It's the weekly rhythm — and occasionally an ad-hoc when something urgent comes up. Here's what that feels like across the cadence.
The manager creates a weekly meeting. The banner reads: "Previous weekly closed with 3 open decisions." The team walks the 12 tiles, captures 3 new decisions, each goes to the owner as a task by email.
A monthly meeting on the previous month. The AI summary lands with last-month performance + YoY. The GM extends the AI text with management commentary in the WYSIWYG editor. Archived.
A 60-room group inquiry comes in. The manager opens an ad_hoc meeting. The team reviews current OTB on the affected dates, channel mix, competitor rates. Decision: accept group, raise weekend ADR. Task to RM.
The GM opens the meeting list on Saturday morning. Two meetings show red. One has an overdue task; one carries a high-priority unresolved decision. Twenty seconds to spot what needs follow-up.
A five-day-old meeting is opened. A fresh upload landed two days ago. The "generating…" chip appears; the old summary stays visible. Sixty seconds later the new narrative renders against the fresh snapshot.
See the meeting as it actually runs.
In our 45–60 minute walkthrough, we run Peaqplus on our live demo environment — a simulated property with data that moves day to day — open a sample meeting end-to-end, walk through the 12 tiles + AI summary, capture two decisions live, and show the task and the Revenue Track entry that lands on the other side.
No setup fee. No PMS access needed. Bring your team — three-way demos welcome.