Where revenue conversations
become decisions.
The collaboration layer that closes the revenue loop. Discussion threads, decisions, meetings, and alerts — all anchored to the data that triggered them.
Most revenue work happens between systems. The signal is in the BI tool. The discussion is in Slack. The decision is in someone's head. The action is in another tool, and the outcome never connects back. We built the layer that puts the loop on rails.
| 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% |
Question. Discussion. Decision. Task. Track.
Discussion Thread and Revenue Decisions are one pipeline, not two features. A question pops on a report row — the chat icon turns it into a thread. The thread carries the discussion until the team converges on what to do. One click promotes it to a Decision with a type, an owner, and a due date. The Decision auto-generates a task for the owner. The task lands on the owner's screen. Everything lives, forever, in the Revenue Track.
Five steps. One data anchor running through all of them. Nothing falls into Slack, email, or a meeting note that nobody re-reads.
- Step 1 — Question pops on a specific report row, linked forever to that data point
- Step 2 — Discussion Thread opens, real-time, @mention-aware
- Step 3 — Convert to Decision: title, type, periods, owner, due date
- Step 4 — Task auto-generated for the owner · notification sent
- Step 5 — Revenue Track: every decision, every source, one backlog
Anchored to the data row, not a Slack channel.
Click the chat icon next to any report row — a daily pickup, a segment line, an Insight tile, a competitor's price point. A panel slides in from the right. Tag a colleague. Ask a question. Discuss the number that matters, in the place where it matters.
The thread carries the report parameters with it; the "Open with these settings" link takes anyone back to the exact data view that triggered the conversation. Threads appear on report rows, on the central /discussions list, with a sidebar badge for your unread count, and on every linked Revenue Track decision card.
- Anchored — every thread stays linked to the exact data row that triggered it
- AI-titled — a short, descriptive title is generated automatically in the user's language, so you never write "Pickup #4"
- Implicit participants — the creator, senders, and anyone @mentioned form the audience automatically
- @mention notifications — tagged colleagues see the unread count light up in the sidebar, with the new message arriving in real time
- Stale-aware — when fresh PMS data lands, the thread is flagged with "still relevant?"; 5 days of inactivity auto-closes
- Convertible to a decision in one click; the thread closes as "converted" and links to the Decision card
- Real-time — messages arrive instantly across the team, no refresh needed
| 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 — auto-suggested by the pricing AI (potential)
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.
Move a rate, change a rule, adjust a level. Most common type — flows naturally from competitor and pickup discussions.
Minimum stay, no-arrival, no-departure, closure. Often surfaces from the Pricing Calendar or Pricing Map.
Corporate push, group rate strategy, sales pipeline action. Owner is usually the sales team lead.
Campaign, channel push, ad budget shift. Owner is the marketing lead; ties back to the booking-engine demand signals.
Channel mix adjustment, OTA-specific contract change, parity decision. Owner is the distribution lead.
An auditable note, not an action. "The German market has been slower to book since April." Status goes straight to done; no task; later searchable in the Revenue Track log.
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. The two-way sync has loop-protection built in, so the system can't oscillate.
- 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
The meeting surface — its own page, its own depth.
Weekly, monthly, ad-hoc — every revenue meeting opens with twelve data tiles already loaded against the meeting's frozen snapshot, an AI-generated narrative drafted in the background, and a decision-capture form ready beneath them. Decisions logged in the meeting feed this same Revenue Track (source = meeting) with auto-generated tasks for the owners.
The meeting workflow is substantial enough to warrant its own module page — the 12-tile architecture, the AI summary lifecycle, the template-driven decision capture, and the health-indicator backlog list each deserve their own depth.
- 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 flagged a corporate group that asked for a discount. Marketing pushed Booking down 5% for the May long weekend. The GM closed Monday check-ins for the Aug 18-21 holiday block. These observations are how a revenue manager learns the shape of their business — but they only have value if they survive past 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 back-fill what you did last week
- 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 popover on the History Report
- Two-way sync with the linked decision — close the decision, the field-log entry closes too
Five scenarios. Five decisions.
The pipeline isn't a feature you use once a quarter. It's the rhythm of the week — pickup anomalies, insight signals, search-demand questions, meeting outcomes, longitudinal observations. Here's what it actually feels like.
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?" Pricing review → decision: "Raise rates for stays of 3+ nights."
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 pushed Booking down 5% for the May long weekend. Logged in Sales Track with the dates. Three weeks later, History Report shows the pickup spike on those dates — and the popover reveals the promo that drove it.
From signal to outcome. In one platform.
Monday morning, Ping fires: weekend pickup is 18% behind forecast. The alert email lands in the GM's inbox. The GM clicks through, opens a Discussion Thread on the row that triggered the drop.
Marketing replies with context: a competitor opened a campaign overnight. The thread converts to a Decision: match the competitor on weekend rates, owner: RM. The decision auto-generates a task. The RM updates the Pricing Engine, the rates push to the channel manager, the task closes. The decision auto-closes too.
Friday afternoon, the Revenue Meeting opens with the AI summary already drafted: weekend pickup recovery — +14% pickup since Tuesday. The loop is done. Inside one platform. Not across four.
Close the loop.
In our 45–60 minute walkthrough (length depends on how deep you want to go), we run Peaqplus on our live demo environment — a simulated property with data that moves day to day — and walk through a real scenario: an alert, a discussion, a decision, an action. You see how it'd land in your team's inbox and how the audit trail looks three months later.
No setup fee. Bring your team — we welcome 3-way demos.