Capstone

Why you need a shared system — the shared truth of a data-driven hotel

10 min

Thursday afternoon, a meeting room at Hotel Peaqplus City. All four leaders sit around one table: Adam, the general manager; Francis, the sales manager; Esther, the marketing manager; and Annette, the owner. It all hangs on one simple question: “How is October looking?”

And this is where the trouble starts. Adam answers from memory: “It’ll be strong — October is always strong.” Francis opens a spreadsheet on his laptop that he exported three weeks ago: “I see two big corporate bookings, we look good.” Esther speaks from her own marketing report: “Our campaigns are driving traffic, my booking numbers are up.” And Annette leafs through a PDF she received at the end of last quarter: “Mine says October is below last year.”

Four leaders. One hotel. Four different truths — because they’re looking at four different sources: memory, a stale spreadsheet, a partial view, and a quarterly PDF. None of them is lying. Yet they’ll spend half an hour arguing about which number is the real one, instead of asking what should we do.

Then Daniel, the revenue manager, quietly turns his screen around and puts up the real-time pace view that’s shared with everyone. A single picture. And the whole character of the debate changes at once.

This closing lesson is about why it isn’t enough to think in a data-driven way — why you need a shared system for that thinking to become decisions. This is the punchline of the entire academy.

The recap: every level led to the same place

Across twenty-six lessons we’ve worked through three levels, and it’s worth seeing that all three led to the same conclusion.

The first level — the data-driven mindset — was about how gut feel misleads you again and again, how an empty room is revenue lost forever, and how you should never decide on a single number. The lesson: to decide well, you have to see the real number.

The second level — data-driven decision-making — taught the relationship between forecast, budget, and actual, the forward-looking reading of pace and pickup (newly received bookings), the real value of segments and channels, and the revenue meeting as a decision forum. The lesson: a decision is good when everyone looks at the same number, and behind every proposal sits the question “by how much, and what does it bring?”

The third level — the role tracks — showed that the GM is the owner of revenue, that sales decides weeks ahead with a single contract, that marketing should spend where the gap is, and that the owner can judge the asset from just four numbers. The lesson: every role is strong only when it aligns its own decisions with everyone else’s.

Notice the common denominator. Mindset, decision, role — all three assumed something we’ve left unspoken until now: that a shared, real-time number exists, one that everyone sees. Without it, mindset is just good intentions, a decision is just an argument, and a role is just a silo. This lesson makes that unspoken assumption visible.

The pain without a system

Let’s look at exactly what happens when there’s no shared system — because it will probably feel familiar.

The numbers live in the RM’s head and in scattered spreadsheets. Daniel knows the pace, knows which dates are lagging — but that knowledge sits in his head and in his files. When he goes on holiday, the knowledge goes with him. The hotel goes blind.

The GM sees a PDF once a quarter. Adam doesn’t see where the house stands in real time, only a snapshot that’s already out of date the moment it’s printed. It’s like driving by the rear-view mirror: you see exactly where you’ve been, but not where you’re headed.

The owner asks in the dark. Annette has no independent line of sight, so she either believes what she’s handed or micromanages out of suspicion. Neither is healthy. Instead of trust, you get either blind faith or constant checking.

Sales and marketing argue on gut feel. Francis wants volume, Esther defends her campaign, and with no shared lens, the louder or the higher-ranking voice wins — not the better argument. The decision becomes authority-based, not data-based.

Decisions aren’t recorded. At last week’s revenue meeting someone said, “let’s raise the price on the second week of October” — but no one wrote down why, or how it turned out. So the organisation doesn’t learn: it can repeat the same mistake next year, because there’s no trace that it already ran into it last year.

This way of working is slow (by the time the four truths meet, the decision window has closed), expensive (the invisible mistakes quietly add up), and distrustful (everyone believes their own number). And worst of all: the RM’s work stays invisible. Daniel makes good decisions, but no one sees them in numbers, so he can’t even defend himself when sales overrules him.

The solution: one shared truth

A shared system isn’t shared because you bought software. It’s shared because everyone looks at the same real-time picture — the same pace, the same forecast, the same decision log, the same meeting record.

Let’s look at what this gives you in concrete terms, and where Peaqplus helps:

  • One shared snapshot — Dashboard. Adam, Francis, Esther, and Annette don’t look at four sources but at one. When the owner logs in, she sees the same RevPAR and occupancy the GM does — not a quarterly PDF. The argument about the number disappears, and what remains is the argument about what to do — the useful one.
  • One shared view of the future — Forecast and Pickup. Pace and pickup aren’t in Daniel’s head but in a shared view. Everyone sees which dates are lagging against the same point last year, and which are running ahead. That’s how marketing knows where to spend; that’s how sales sees when a group would displace a higher-paying guest.
  • One shared decision forum — Revenue Meeting. The proposals, the numbers behind them, and the decision made — all in one place, recorded. “What we decided and why” isn’t lost — it can be looked back on, so it can be learned from.

And here is the soul of the lesson: a shared system is the RM’s ally, not the manager’s surveillance tool. It isn’t about Adam checking up on Daniel. It’s about Daniel’s work finally becoming visible and credible — his good pricing decisions show up in numbers, and the leaders align through a shared lens instead of arguing on gut feel. The revenue manager doesn’t lose anything to the system; he gains from it: authority and trust. From the revenue manager’s point of view, the shared system is unpacked in detail in the RM Academy lessons on reporting and leading the revenue meeting.

A worked example: what does a “non-shared” operation cost?

Let’s make the pain measurable. What does it cost Hotel Peaqplus City (80 rooms) in a year that the four leaders don’t look at the same picture? Take three plausible, conservatively estimated sources of loss — all of them the kind a shared, real-time view would largely eliminate.

Source of lossCalculationAnnual impact
Late-corrected pricing
(the pace is only in Daniel's head, so the move comes too late)
1 day/week × 8 EUR/room shortfall × 55 rooms sold × 52 weeks22,880 EUR
Blindly displaced guest
(sales books a group because it can't see the high pace)
3 times/year × (110−75) EUR × 25 rooms × 2 nights5,250 EUR
Mistimed marketing
(budget goes to days that fill on their own)
~5 campaigns/year × ~1,600 EUR wasted/forgone~8,000 EUR
Total~36,000 EUR/year

Let’s check the maths. The first row: 8 × 55 = 440 EUR per day, which over 52 weeks comes to 22,880 EUR. The second: (110 − 75) = 35 EUR of displaced rate difference, which for 25 rooms and 2 nights is 35 × 25 × 2 = 1,750 EUR per occasion, and across three occasions 5,250 EUR. The third is a cautious estimate: five misfired campaigns, each with roughly 1,600 EUR of wasted spend or forgone revenue, for ~8,000 EUR. The sum: 22,880 + 5,250 + 8,000 = 36,130 EUR, rounding to roughly 36,000 EUR a year.

Let’s put that in context. An 80-room hotel, at ~76 EUR RevPAR, produces roughly 2.2 million EUR in room revenue a year. The 36,000 EUR is about 1.6% of that — and it came from just three conservatively estimated sources. It isn’t one big, dramatic mistake: it’s small, invisible, recurring friction that no one feels on any single day. That’s exactly why it’s dangerous. And it’s exactly the kind of loss that a shared, real-time truth largely removes — not by forcing smarter decisions, but by making the good decision visible in time and in front of everyone.

Back to the meeting room

Daniel’s turned-around screen sits on the table. On the shared pace view everyone sees the same thing: the first week of October is strong, ahead even against the same point last year — but the second week is lagging, ten days before the critical window.

And from here the conversation is different. Adam doesn’t speak from his gut but points at the picture: “We raise the price on the first week.” Francis sees that, because of the high pace, one of his corporate bookings would actually displace a more expensive guest, and proposes a higher rate on his own. Esther knows at once where to move the budget: to the weak second week, not the first that fills on its own. And Annette doesn’t ask out of suspicion, because she sees what they see — she just asks the good owner’s question: “What is the second week’s catch-up based on?”

Four leaders, one picture, ten minutes. They didn’t align because someone dictated the truth, but because they arrived at a shared truth. That’s the difference between data-driven intent and a data-driven hotel — and one thing makes it possible: the shared system.

This is the academy’s final message. In practice, data-driven leadership is impossible without a shared data system. You have the mindset, you know the decision logic, you understand your role — the shared lens is what ties all of it into a single, aligned hotel.

Key takeaways

  • Four sources, four truths. When leaders look from memory, a stale spreadsheet, and a quarterly PDF, they’ll have different pictures of the same hotel — and their argument will be about the number, not about what to do.
  • A data-driven mindset without a shared system is only intent. All three levels (mindset, decision, role) assumed the same thing: that a shared, real-time number exists, one that everyone sees.
  • The system is the RM’s ally, not a surveillance tool. The shared view makes the revenue manager’s work visible and credible, and aligns the leaders — it doesn’t control, it builds trust.
  • The cost of its absence is real and measurable. From just three conservative sources, ~36,000 EUR/year at an 80-room hotel — small, invisible, recurring friction that a shared truth largely eliminates.
  • Shared picture = fast alignment. Looking at the same pace, forecast, and decision log, the four leaders align in ten minutes — arguing on gut feel, they wouldn’t in hours.
Check your understanding

Click an answer — you see immediately whether it is right.

Answer all of them and the lesson counts as complete — and toward your progress.

What makes a shared system truly "shared," according to this lesson?
In the worked example, sales books a group three times a year without seeing the high pace: 25 rooms, 2 nights, at 75 EUR each time — on dates where 110 EUR transient demand would have come. What is the annual loss?
Why does the lesson call the ~36,000 EUR annual cost of a "non-shared" operation dangerous?
Go deeper
Related terms

See the full definitions in the glossary.

Leadership questions

If you asked your hotel's four key people right now, this minute, "how is next month looking?", how many different sources would they answer from — and how far apart would their answers be? What would happen if they all looked at a single shared picture? Think back to your last leadership argument about a date or a rate: how much of it was about the number (who sees the real one), and how much about what to do? How much time would a shared lens have saved you?

Signal → Decision → Action → Outcome

See Peaqplus on your own data.

In our 45–60 minute walkthrough we run Peaqplus on our live demo environment — a simulated property with data that moves day to day.

No setup fee. No PMS access needed.

Not ready for a demo? Start smaller —5-min revenue check →ROI in 4 numbers →