Inside a Revenue Gap Review: How a Composite Bath Hotel Found £180k in Six Weeks

A note before we start: GapMap is a new tool and we don't yet have a published customer case study to share. What follows is an illustrative, composite example — built from the kind of gap we see repeatedly across UK premium venues — to show how a gap review actually works in practice, not a claim about a specific real venue.

Picture a 45-room boutique hotel in Bath. Solid reviews, a loyal repeat-guest base, a GM who knows the property inside out. Occupancy looks healthy on paper. And yet, quarter after quarter, revenue growth is flat while the competitive set around it edges up.

Step 1: Find where the heatmap goes cold

A gap review starts by laying every day of the year against every rate and occupancy signal available, and looking for where the pattern breaks. For our composite hotel, the heatmap shows almost exactly what you'd expect for a well-run boutique property — strong weekends, steady summer — with one conspicuous cold patch: Sunday-to-Tuesday in the shoulder months, consistently underperforming both its own weekend and the wider Bath market for the same nights.

That's the starting signal. Not a hunch, not a competitor's rate glimpsed once — a pattern that holds across months of data.

2. Ask why, not just where

The heatmap tells you where the gap is. It doesn't tell you why. For this composite property, three plausible drivers stack up:

• No differentiated midweek offer — the same room product, same rate logic, applied to a Tuesday as a Saturday, despite very different demand.
• A local corporate segment that isn't being targeted — Bath has meaningful weekday business and event traffic that a leisure-first hotel typically under-serves.
• A shoulder-season rate that was set once and never re-tested — the kind of "temporary" markdown from a quiet January that quietly became the default.

3. Turn the gap into a number

Once the pattern and the likely cause are clear, the gap becomes a revenue estimate: for this composite scenario, closing the Sunday–Tuesday shoulder-season gap to within striking distance of the property's own weekend performance — not matching it, just narrowing it — works out to roughly £180,000 over six weeks of the affected period. That's not a hypothetical improvement pulled from nowhere; it's the gap between what the property is actually earning on those nights and what its own data says those nights are capable of earning.

Why this pattern is so easy to miss internally

None of the three drivers above would show up in a standard monthly occupancy report, and that's the point. A GM looking at "Sunday–Tuesday occupancy: 68%" for the shoulder season has no obvious reason to flag it as unusual — a dip on the traditionally quieter nights looks exactly like what everyone expects to see. It only reads as a genuine gap once it's compared against the venue's own weekend performance and the wider local market for the same nights, which is a comparison most trading reports simply aren't built to make automatically.

That's usually the real value of a structured gap review: not finding data nobody had, but looking at data everyone already had in a way nobody had tried before.

4. From gap to campaign

The last step is the one that actually moves the number: turning the finding into something bookable. For a gap like this, that typically means a targeted midweek package aimed specifically at the underserved corporate segment, timed to launch ahead of the shoulder season rather than during it, with messaging built around what that segment actually books for — not a generic "midweek discount" that trains guests to wait for a markdown.

This is the part of the process GapMap was built for — going from "here's a cold patch on a heatmap" to a ready-to-run campaign brief, without weeks of manual analysis in between. If you want to see what this looks like against your own venue's data, get in touch.

The takeaway

The gap in this composite example wasn't a demand problem — the hotel had guests it wasn't reaching and rate it wasn't asking for. That's the pattern we see most often: the revenue was already sitting in the data, just not in a shape anyone had looked at closely enough to notice.