Keep the reason behind
every revenue decision.
Hotel revenue decision software that connects the signal, the discussion, the owner, the deadline and the outcome in one traceable workflow.
The GM sees what was agreed and what is still open. The revenue manager can return to the figures behind the call. Sales and marketing receive a clear next step — without relying on a Slack thread or meeting note that disappears from view.
| Period | Segment | OTB | LY · SP | Δ |
|---|---|---|---|---|
| W17 · Mar | Direct | €48k | €44k | +9% |
| W17 · Mar | OTA | €62k | €58k | +7% |
| W17 · Mar | Corporate | €18k | €26k | −31% |
| W17 · Mar | MICE | €12k | €11k | +9% |
Clarity for the leader. Context for the expert. Ownership for the team.
Everyone enters the workflow from a different role, but the decision and its supporting data stay shared.
Owners and GMs can review the decision, its reason, owner and deadline without rebuilding the meeting from memory.
Revenue managers can open the report row or Insight that started the conversation and see what the team knew at that point.
Sales, marketing and distribution receive an assigned task instead of an action point buried in notes or chat.
“If everyone analyzes the data separately, it’s easy to end up with different conclusions.”
Every manager at Hotel Divinus opens Peaqplus at least once a day. The team starts its morning leadership briefing from one shared set of figures.
From a question on the data to an owned next step.
Open a Discussion on the report row or Insight that raised the question. When the team agrees on the next move, turn the thread into a Decision with a type, affected dates, an owner and a due date. Peaqplus creates the linked task and keeps the decision in Revenue Track.
The data reference stays attached throughout. Months later, the team can still see what prompted the decision, who owned the action and whether it was completed.
- Step 1 — Start from a specific report row or Insight
- Step 2 — Open a Discussion and bring in the right colleagues
- Step 3 — Record the decision, reason, affected dates, owner and due date
- Step 4 — The owner receives a linked task and notification
- Step 5 — Revenue Track keeps the open item and its history together
Anchored to the data row, not a Slack channel.
Open the chat beside a daily pickup row, segment line, Insight tile or available competitor-rate point. Tag a colleague and discuss the figure where the team can still see its period and filters.
The thread carries the report settings with it. Anyone in the conversation can return to the same data view, while the central Discussions list and unread badge keep active questions visible.
- Every thread stays linked to the report row, Insight and dated data state that triggered it
- The creator, contributors and @mentioned colleagues form the participant list automatically
- Mentioned colleagues receive an unread notification and new messages appear without a page refresh
- New hotel data prompts a relevance check; five inactive days close the thread automatically
- One click converts the thread into a linked Decision
| Period | Segment | OTB | LY · SP | Δ |
|---|---|---|---|---|
| W17 · Mar | Direct | €48k | €44k | +9% |
| W17 · Mar | OTA | €62k | €58k | +7% |
| W17 · Mar | Corporate | €18k | €26k | −31% |
| W17 · Mar | MICE | €12k | €11k | +9% |
One backlog. Five sources. Every decision in one place.
Every revenue decision your team makes — wherever it originates — lands in the Revenue Track. Discussion-, meeting-, direct-, sales-, and pricing-sourced decisions all live in one unified backlog, with the source as a filter chip rather than a separate page. Open or closed, pricing-only or everything, source-filtered or all — same backlog, same audit trail.
Every decision carries a reason, an owner, a due date, and one or more affected periods (a single decision can span multiple date ranges). Status moves between open, done, and not-executed; the linked task moves with it in both directions automatically.
- discussion — promoted from a Discussion Thread
- meeting — captured during a Revenue Meeting
- direct — created standalone on the /decisions page
- sales track — captured from a Sales Track note
- pricing — recorded from a pricing recommendation or review
Every decision is shaped, not free-form.
Every Decision carries a type — the form pre-selects it from the discussion context, and the Revenue Track filters by it. Five types generate tasks for an owner; the sixth, observation, is special — it's an auditable note, not a unit of work.
Review a rate, change a rule or adjust a pricing level. Often starts from a pickup or market-position discussion.
Review minimum stay, arrival, departure or closure settings for a defined period.
Follow up a corporate lead, group-rate strategy or sales pipeline opportunity.
Launch or revise a campaign for the period where the booking or search signal needs support.
Review channel mix, an OTA-specific agreement or a rate-parity question.
Keep a searchable note when the team needs context but no one needs a task.
Close the task, the decision closes. Close the decision, the tasks move.
Every Decision with an owner (and a non-observation type) auto-generates a task. The owner gets a notification; the task lands on their My Tasks page next to whatever else they're working on. The decision and the task are linked — and synced automatically in both directions.
If the owner marks the task done, the decision auto-closes. If a colleague closes the decision from the Revenue Track, the linked tasks move with it. And the two-way link knows not to chase its own tail — a change never bounces back and forth.
- One task system — for decisions, meeting decisions, manual to-dos, and system alerts alike
- Four task statuses — planned · in progress · done · cancelled
- Task done → decision auto-closes · all tasks cancelled → decision auto-marks not-executed
- Decision closed at the top → linked tasks sync · decision reopened → tasks move back to planned
- My Tasks page — owners see their work-list with deadline / priority / type filters
Leave the meeting with owners, deadlines and a shared record.
Weekly, monthly or ad hoc, the Revenue Meeting opens with twelve data tiles on the meeting's dated snapshot and the decision form ready underneath. Decisions recorded in the meeting enter the same Revenue Track and create linked tasks for their owners.
The meeting workflow is included in BI Core. When Pulse AI is active, it also prepares the written meeting narrative; the twelve data tiles, decision capture and follow-up do not depend on AI.
- Weekly — short, tactical; open decisions roll forward
- Monthly — strategic; reviews previous outcomes, sets next plan
- Ad-hoc — any time something urgent comes up
- Health indicator on the list — 🟢 healthy · 🟡 attention · 🔴 critical
Capture what you did. So you remember why.
Some decisions don't happen in a meeting. The reception lead flags a corporate group asking for a discount. Marketing launches a 5% direct-booking offer for the May long weekend. The GM sets an arrival restriction for the Aug 18–21 holiday period. These actions only become useful learning if they remain visible after the day they happened.
Sales Track is the daily field log. Pick a category — pricing action, marketing campaign, distribution restriction, anything you define for your hotel — set the period the note affects, write it down. Every entry automatically becomes a Decision in the Revenue Track, so the field log and the formal backlog are the same backlog. Three weeks later, when you open the History Report and see a pickup spike on a Tuesday, a small icon on the row reveals the note that explains it.
- Categorised by you — wellness-package promo, MICE inquiry, corporate window, your own taxonomy
- Target period ≠ when you wrote it — annotate a future window, or record last week's action after the fact
- Every note becomes a Revenue Decision automatically — nothing slips through the cracks
- Surfaces in three places — its own page, the Executive Summary tile, and a hover detail on the History Report
- Two-way sync with the linked decision — close the decision, the field-log entry closes too
Six situations. One shared record.
The workflow is useful whenever a figure needs an owner or a later explanation — from a pickup change to a meeting follow-up or a longer-term observation. The figures below are simulated examples, not promised results.
A daily-pickup row jumps +18 room-nights. Thread on the row: "Thursday spiked — source?" RM replies: "Czech long weekend, Polish campaign launched." Decision: marketing-team raises Friday CPC. Marketing-lead gets the task.
An Insights tile flags "Aug 5–12 occupancy falling". Thread on the tile. Decision: "15% all-inclusive non-refundable for these dates." Distribution-lead task.
Top Searches row: "Aug 20 — 124 searches, 8 bookings". Thread: "Why doesn't it convert?" Decision: review the rate and booking path for 3+ night searches before changing either.
Friday's Revenue Meeting → 5 decisions logged (source=meeting). Saturday morning the Revenue Track shows 3 due-this-week. Owners see them on their My Tasks. Tasks complete → decisions auto-close.
"The German market has been slower to book since April." Logged as type=observation. Status goes straight to done; no task. Six weeks later, audit-searchable when someone asks why the strategy shifted.
Marketing launches a 5% direct-booking offer for the May long weekend and records the dates in Sales Track. Three weeks later, the History Report shows the note beside the relevant pickup movement.
Follow one decision from signal to review.
Monday morning, Ping flags that weekend pickup is behind forecast. The GM opens the supporting row and starts a Discussion so the revenue and marketing teams can add context.
The team records a Decision to review the weekend offer, assigns it to the revenue manager and sets a deadline. The linked task records the follow-up; if the separate Pricing module is active, any approved rate change is handled there.
At the next Revenue Meeting, the team returns to the same decision and the latest performance. The record shows what prompted the action, who owned it and whether it was completed — without turning a simulated example into a promised result.
Included in BI Core from €109/month.
Discussion, Decisions, linked tasks, Sales Track and the Revenue Meeting workflow are included on every plan. BI Core has a one-time €135 setup fee with 2 hours of team training; most hotels are live in 7–14 days. The written AI narrative in Revenue Meeting requires Pulse AI. Prices are per property and exclude VAT.
See plans and pricing →What Decisions & Collaboration includes.
The workflow, package boundary and AI dependency in plain language.
Hotel revenue decision software keeps the business reason, supporting data, owner, deadline and status of a revenue decision in one record. Peaqplus connects that record to the report row, Insight, Discussion or Revenue Meeting where the question started, so the team can return to the original context instead of reconstructing it from chat and meeting notes.
The team opens a Discussion on a report row or Insight, adds the relevant colleagues, then converts the agreed next step into a Decision with a type, affected dates, owner and due date. Peaqplus creates a linked task for the owner and keeps its status synchronized with the Decision in Revenue Track.
Discussion, Decisions, linked tasks, Sales Track and the Revenue Meeting workflow are included in BI Core on every Peaqplus plan. The workflow works without AI. Pulse AI is required for the written AI narrative in Revenue Meeting; standard BI Core subscription and setup still apply.
Bring one decision your team keeps revisiting.
In a 45–60 minute demo, we run the workflow on a simulated property whose data changes from day to day: open the signal, discuss it, assign the action and return to the record. Bring the GM, revenue manager or the colleague who usually owns the follow-up.
The demo is free and requires no PMS access. We reply within 1 business day.