How we measure our data
Every figure on this site falls into one of five evidence types. Below are the benchmark sources behind the ROI model, and the plain-language labels we use so you can tell a measured result from an estimate or a target.
Benchmark sources behind the ROI model
OTA share of bookings
STR / Skift Research, 2025
Verified Oct 202550%
OTA commission rate
Booking.com / Expedia standard rate
Verified Oct 202515%
OTA-to-direct conversion
Management conversion assumption; named research has not been independently substantiated
Verified Oct 20252.1%
Guest vendor booking rate
Industry benchmark (pre-deployment estimate — no live deployment data yet exists)
Verified Oct 202513.7%
Average vendor booking value
UK hospitality vendor network average
Verified Oct 2025£45
Vendor commission rate
GSI vendor agreement terms — actual commission varies 5–15% by vendor category
Verified Oct 202510% (blended average)
Upsell revenue per room/year
Management upsell assumption; replace with hotel-specific attributable sales
Verified Jul 2025£40
Guest review rate via Lucy
TripAdvisor industry benchmark, 2024
Verified Jan 20255%
Attributed review-to-booking conversion
Excluded until hotel-specific incremental attribution is measured
Verified Not measured0% default
Upsell fulfilment margin before platform share
Management assumption; replace with hotel departmental contribution margin
Verified Not measured50% illustrative
Incremental room contribution margin
Management assumption; replace with hotel variable room cost margin
Verified Not measured70% illustrative
Lucy booking engine capture
Management capture assumption; no live Lucy conversion measurement
Verified Oct 20252%
Lucy booking engine fee
GSI direct booking engine pricing (vs 15% OTA)
Verified Oct 20255%
Staff hours redeployed/year
Internal pilot estimate (300-room baseline)
Verified Oct 20252,000 hrs
Loaded staff cost/hour
ONS UK hospitality earnings, 2025
Verified Oct 2025£23
Software cost avoidance (optional)
Hotel enters the subscriptions it would actually cancel; typical list for a 300-room hotel is £19,800/yr (illustrative)
Verified Oct 2025£0 default
What our evidence labels mean
Industry benchmark
A figure taken from a named third-party source such as STR, Skift Research, Cornell Hospitality, ONS or TripAdvisor. The source is listed in the table above.
Internal estimate
A figure from our own pilot modelling or management projection. It is not a production measurement at a live hotel and is marked as an estimate wherever it appears.
Controlled test (smoke test)
A small, controlled technical test, such as a seven-category vendor booking test. It shows the mechanism works. It is not a full-scale load test and not a guarantee of live performance.
Target
A performance goal we are engineering towards, such as response times or uptime. It is not a measured result.
Code-complete, awaiting certification
The connector is built and sandbox-tested but has not been certified against the live system. This applies to Mews, Opera, Cloudbeds and Apaleo.
How we count features and project revenue
- Feature counts are taken from the platform's own registry of data types and backend functions.
- Guest-facing features (80+) are a subset of the wider operations platform (135 staff tools across 18 departments).
- Not every counted feature is live in production. Most are code-complete and sandbox-tested.
- Financial projections use the inputs shown in the ROI calculator so you can change any assumption and see the effect.
Current platform status
Manually maintained pre-deployment disclosure. Targets are engineering goals, not measured results; this section is not a live monitoring feed.
Monthly availability target
99.5% target
No verified production uptime record is presented.
Conversation text response target
Under 3s target
Not a measured audio or live guest performance result.
Hotels live on Lucy
0
Pre-deployment. First founding hotel pilot planned for Q1 2027.
Backend functions deployed
200+
Production-deployed and sandbox-tested. Count taken from the platform function registry.
PMS integration certification progress
Connectors require property credentials, supported-operation testing and any required supplier approval before live use. This manually maintained status is not evidence of certification. Public demonstrations can run without a PMS connection.
Connector code-complete and sandbox-tested. API integration complete. Awaiting first live tenant to certify against.
Connector code-complete (read-only sync; bi-directional write-back pending). Awaiting first live tenant to certify against.
Connector code-complete (two-way sync) and sandbox-tested. Authentication flow complete. Awaiting first live tenant.
Connector code-complete with webhook listener ready. Awaiting first live tenant to certify against.
Last updated: October 2026. Progress is updated when certification milestones are reached.