Hotels, Resorts & Travel · founder's prior sector experience · before OmniFlow
What international hospitality taught our founder about direct demand, rate integrity and seasonality
Before OmniFlow existed, our founder held growth and commercial roles connected to major international hotel groups. This entry records what that sector teaches about the economics of a room night — where demand is bought, what it costs to buy it through someone else, and why a rate that differs by channel is a trust problem before it's a revenue one. It's career history, not an OmniFlow client engagement, and it makes no performance claim of any kind.
At a glance
The engagement in brief
Services
- Positioning
Stack
- Central reservation system
- Channel manager
- Revenue management system
- Online travel agency extranets
- Metasearch
- Corporate and group rate agreements
The situation
What we walked into
Hospitality is one of the few categories where the same unit of inventory is sold simultaneously through paths with radically different economics. The same room, on the same night, can reach a guest through the brand's own site, a metasearch auction, a large online travel agency, a niche regional one, a corporate rate agreement or a group block, and the net rate the property keeps differs materially across all six. Layered on top of that are parity clauses that constrain what the operator may publish, a demand curve that changes shape several times a year, and a booking engine that is usually owned by a different department from the website in front of it.
The same room, on the same night, can be sold through five or six different paths at five or six materially different net rates, and the guest sees none of that.
What we found
The diagnosis
01
Direct is not free, it is differently expensive
A booking that arrives through the brand's own site still costs media, engineering, a loyalty incentive and a booking engine that has to work on a phone at midnight in a bad signal area. The honest comparison is net rate after all acquisition cost, per channel, held in one place. Very few operators keep that comparison anywhere, which is why the direct-versus-intermediated argument is usually conducted on intuition.
02
Rate integrity is a trust problem before it is a revenue problem
A guest who finds the same room cheaper on a third-party site three minutes after booking direct does not conclude that the operator has a sophisticated distribution strategy. They conclude they were overcharged by the brand, and the next booking goes to the third party by default. The revenue lost on the individual booking is trivial next to the habit that gets formed.
03
Seasonality makes annual averages actively misleading
A property's year is a small number of very different markets stacked end to end, with different guests, different length of stay and different price elasticity. An annualised occupancy or acquisition figure describes none of them, and a plan built on the average is wrong in both directions for most of the calendar.
04
Group, corporate and leisure demand are three businesses sharing a building
They are sourced differently, contracted differently, cancel differently and respond to completely different signals. Treating them as one demand pool is how a property ends up discounting into a segment that was going to book anyway, in a week where the segment it actually needed was never approached.
What we built
The system
There is no OmniFlow build to describe here, because OmniFlow did not deliver this work. What the experience contributes to the agency is a way of framing hospitality problems: start from net rate per channel rather than from the headline rate, treat the booking engine as part of the funnel rather than as a downstream system somebody else owns, read the seasonal shape before reading the performance report, and separate leisure, corporate and group demand before writing a single line of creative. When OmniFlow takes on hospitality work, the first deliverable is a channel-by-channel view of what a booking actually costs, because that view almost never exists in one place and every decision after it depends on having one.
The sequence
How it was delivered
Before publication
Scope confirmation
Written description of the roles actually held and what was and was not within their remit
Owner: OmniFlow founder
Before publication
Permission check
Written confirmation of what may be described; any brand, property or figure not cleared stays out
Owner: OmniFlow founder + former employer
Before publication
Claim review
Every sentence tested against one question: could this be read as an OmniFlow client engagement?
Owner: OmniFlow
Before publication
Framing pass
Entry written around what the sector teaches rather than around anything achieved
Owner: OmniFlow
At publication
Publication gate
Ships with no figure, no brand name, and an explicit statement that this is career history
Owner: OmniFlow
Outcome
Results
There is no result to report here and none should be inferred. This entry describes prior individual professional experience of OmniFlow's founder, in roles held before the agency existed. It is not an OmniFlow client engagement, no work was delivered by OmniFlow to any hotel group, and no performance figure is claimed, implied or available. Career history and client work are two different claims, and a page that lets a reader mistake one for the other fails the first question due diligence asks. Scope, the exact description of the roles held, and any permission required from a former employer must be confirmed in writing before this entry is published in any form.
Founder's prior professional experience in international hospitality, before OmniFlow. This is career history, not an OmniFlow client engagement. No performance figure is claimed, no brand is named, and scope and permissions must be confirmed in writing before publication. Cited: Book Better Direct *2026*; SiteMinder *Hotel Booking Trends*; LocaliQ *2026 Search Benchmarks*. ---.
Reporting
What you would actually see
These are the surfaces this engagement is run and measured from, shown with representative figures built around the benchmarks cited on this page. Every account we run reports into views like these, and you keep ownership of all of them.
These are demo dashboards. They show the reporting surfaces this engagement is run and measured from, with representative figures generated around the published benchmarks cited on this page — not a client account and not a client result. Live reporting for your own account replaces every number here.
Google Analytics 4
Hotels, Resorts & Travel · all web data
Sessions
2,049
+81.6%
Key events
64
+101.9%
Session key event rate
3.1%
+0.9%
Engagement rate
57.9%
+7.7%
Sessions by month
Dashed line marks the month the engagement started.
| Session default channel group | Sessions | Key events | Rate |
|---|---|---|---|
| Organic Search | 803 | 19 | 2.4% |
| Paid Search | 468 | 18 | 3.8% |
| Direct | 380 | 10 | 2.6% |
| Referral | 250 | 9 | 3.6% |
| Organic Social | 148 | 6 | 4.1% |
Method
How this is measured
3 of the figures on this engagement are not published yet. Rather than estimate them, this is the standard they will be held to: the system each is read from, and the exact definition and window that will be used. Nothing appears above until it has been pulled from the system named here.
| Figure | Read from | How it is defined | Status |
|---|---|---|---|
| Direct share of room-night bookings | the relevant group's own commercial reporting | not held by OmniFlow. Publish nothing here without written permission from the former employer and a named report to cite | Not yet published |
| Rate parity variance across channels | channel manager and rate-shopping reports | not held by OmniFlow; historical and almost certainly unrecoverable — consider removing this metric rather than sourcing it | Not yet published |
| Occupancy and seasonality spread | the property or group's own performance reporting | not held by OmniFlow. Publicly available market data must never be presented here as work output | Not yet published |
Honestly
What we would do differently
Not a delivery critique, because there was no OmniFlow delivery to critique. The honest admission is about the claim itself. It is tempting to place sector experience beside client work on the same page, in the same layout, with the same visual weight, and let the reader draw the flattering conclusion without anyone ever writing it down. That is the failure mode this entry exists to avoid. Career history is evidence that we understand a sector. It is not evidence that we have produced a result in it, and the page must never blur the two. If that distinction cannot be made obvious in the design as clearly as it is in the copy, this entry should not run at all.
Next
Start the same conversation
Start the same conversation
Tell us what you are working on and we will say plainly whether this is the right shape of engagement for it.