Information security for software delivery

ISO/IEC 27001
ISO/IEC 27001 certified
The guest journey
Eight moments, and the system carrying each one
The website owns two of these moments and influences six. Where a lane is empty, nothing is carrying that moment — which is usually where the booking is lost.
| Stage | 01Discover | 02Website | 03Booking | 04Pre-arrival | 05Stay | 06Requests | 07Checkout | 08Post-stay |
|---|---|---|---|---|---|---|---|---|
| Moment | Search, a map listing, an aggregator, a recommendation. | Rooms, rates, the property's own story, in the guest's language. | Availability, rate rules, payment, confirmation. | Late arrival, transfer, an upsell that is actually relevant. | Check-in, the room, the restaurant, the wifi. | Towels, maintenance, late checkout, a question at 11pm. | The folio, the invoice, the last impression. | The review, the receipt, and whether the next booking is direct. |
| Website | Content and speed decide whether the click happens. | Owns it entirely: rooms, rates, language, performance. | Hands over to the engine — the point most funnels lose people. | Carries the review prompt and the direct-booking offer. | ||||
| Booking engine | Supplies live availability to the rate display. | Owns the transaction, the hold and the confirmation. | Amendments and cancellations run here. | |||||
| PMS | Receives the reservation. If it does not, the desk cannot find it. | Holds the arrival note the desk will read. | Room assignment, folio, everything operational. | Charges and task status post back here. | Produces the folio and closes the stay. | |||
| CRM | Guest profile and marketing consent recorded where it was given. | Pre-arrival messaging on the channel the guest used. | Stay preferences recorded for the next visit. | Owns the relationship the direct booking was for. | ||||
| AI and comms | Answers the question that would otherwise be a bounce. | Takes the booking by phone or WhatsApp when the desk cannot. | Confirms transfers and late arrivals in writing. | Routes requests into the department queue with the room attached. | Answers invoice questions from the folio. | Handles the lost-item and rebooking conversation. | ||
| Analytics | Source and campaign attribution. | Stage-by-stage drop-off, not one conversion number. | Measured across the handover, which is where most funnels go dark. | Repeat rate, the number the whole exercise is for. |
01
Discover
Search, a map listing, an aggregator, a recommendation.
- Website
- Content and speed decide whether the click happens.
- Analytics
- Source and campaign attribution.
02
Website
Rooms, rates, the property's own story, in the guest's language.
- Website
- Owns it entirely: rooms, rates, language, performance.
- Booking engine
- Supplies live availability to the rate display.
- AI and comms
- Answers the question that would otherwise be a bounce.
- Analytics
- Stage-by-stage drop-off, not one conversion number.
03
Booking
Availability, rate rules, payment, confirmation.
- Website
- Hands over to the engine — the point most funnels lose people.
- Booking engine
- Owns the transaction, the hold and the confirmation.
- PMS
- Receives the reservation. If it does not, the desk cannot find it.
- CRM
- Guest profile and marketing consent recorded where it was given.
- AI and comms
- Takes the booking by phone or WhatsApp when the desk cannot.
- Analytics
- Measured across the handover, which is where most funnels go dark.
04
Pre-arrival
Late arrival, transfer, an upsell that is actually relevant.
- Booking engine
- Amendments and cancellations run here.
- PMS
- Holds the arrival note the desk will read.
- CRM
- Pre-arrival messaging on the channel the guest used.
- AI and comms
- Confirms transfers and late arrivals in writing.
05
Stay
Check-in, the room, the restaurant, the wifi.
- PMS
- Room assignment, folio, everything operational.
- CRM
- Stay preferences recorded for the next visit.
06
Requests
Towels, maintenance, late checkout, a question at 11pm.
- PMS
- Charges and task status post back here.
- AI and comms
- Routes requests into the department queue with the room attached.
07
Checkout
The folio, the invoice, the last impression.
- PMS
- Produces the folio and closes the stay.
- AI and comms
- Answers invoice questions from the folio.
08
Post-stay
The review, the receipt, and whether the next booking is direct.
- Website
- Carries the review prompt and the direct-booking offer.
- CRM
- Owns the relationship the direct booking was for.
- AI and comms
- Handles the lost-item and rebooking conversation.
- Analytics
- Repeat rate, the number the whole exercise is for.
Two lanes matter more than the rest: the booking engine handover, because it is where guests leave, and the CRM, because it is what a direct booking was worth in the first place.
The commercial problem
Every booking through an aggregator costs you the commission and the guest relationship
The commission is the visible cost. The less visible one is that the guest belongs to the aggregator: you do not hold the email, the stay preferences or the permission to contact them again, so the second stay has to be bought a second time. A direct booking is worth more than the margin difference suggests.
Hotels know this and respond by redesigning the website, which usually addresses the wrong stage. Guests rarely abandon because the photography was weak. They abandon at the point where the marketing site hands over to the booking engine — the layout changes, the language reverts to English, the page takes four seconds on a phone, and the aggregator app is one tap away with the same room already priced.
That handover is where we start. It is also the part most agency redesigns leave untouched, because it belongs to the booking engine vendor rather than the site. Fixing it is less glamorous than a new visual identity and usually moves the number more.
The funnel
Where hotel websites lose the booking
Four drop-off points account for most of the loss on the properties we have looked at. All four are measurable before anyone redesigns anything.
- 01
The booking engine looks like a different company
The guest crosses from a considered brand experience into a third-party interface with its own typography, its own language handling and no visual continuity. Trust drops exactly where payment details are about to be entered. Most engines allow far more theming than hotels use — and where a vendor genuinely cannot be styled, that is a procurement finding worth having.
- 02
Arabic is a translation, not a design
A mirrored English layout with translated strings is obvious to an Arabic-speaking guest within seconds. Right-to-left reading changes where the eye goes and where the primary action should sit; Arabic typography needs different line height and sizing to be comfortable. Where the booking engine reverts to English mid-flow, the guest has been told which language the hotel actually operates in.
- 03
The site is heavy on exactly the connection guests use
Hotel sites are image-led by nature, and the images are frequently shipped at desktop resolution to a phone on hotel wifi or a mobile network. A hero that takes four seconds on the connection your guests are actually using has lost a proportion of them before the first rate is visible.
- 04
Nobody can say where guests actually leave
Analytics typically stop at the boundary of the booking engine, so the funnel is measured up to the moment it matters and not through it. Without stage-by-stage drop-off you are redesigning on opinion. Instrumenting the existing funnel first costs little and tells you which of these problems you actually have.
What we build
The parts that carry the booking
- 01
A continuous booking path
The engine themed to the brand as far as the vendor allows, language and currency carried across the handover, and the funnel instrumented end to end so drop-off is visible by stage rather than as a single conversion number.
- 02
Arabic-first, not Arabic-also
Layouts designed in both reading directions from the start, Arabic typography set for comfort at mobile sizes, and content localised rather than translated — including rate descriptions and policies, where a literal translation reads as a legal document.
- 03
Multi-property architecture
A group site where each property has its own identity, rates and content without four separate builds. Shared components, per-property overrides, and a content model the properties can edit themselves without a release.
- 04
Performance on a real connection
Responsive images at the sizes actually served, server rendering or static generation, an enforced JavaScript budget, and testing on mid-range devices rather than the studio laptop.
Integration surface
What the site has to talk to
The integration list is where a hotel web project succeeds or fails. We establish what each system actually exposes before design, because it constrains what the site can promise.
Booking
- Booking engine
- Channel manager
- Rate management
- Payment gateway
Property
- PMS
- Housekeeping
- POS
- Folio
Guest
- CRM
- Loyalty
- Email and messaging
- Review platforms
Measurement
- Analytics
- Funnel instrumentation
- Search Console
- Tag management
Common questions
What buyers ask
Will a redesign hurt our search rankings?+
It can, if URLs change without redirects, content is cut, or the new site is slower. Done properly — a redirect map from every old URL, content preserved or improved, and performance measured before and after — a redesign usually helps. The risk comes from treating it as a visual project rather than a technical one.
Can you work with our existing booking engine?+
Usually, and we would look at what it exposes before recommending a change. Most major engines support more theming and deeper integration than hotels have configured. Where an engine genuinely cannot carry the brand or the language through the flow, that is worth knowing as a procurement finding rather than designing around silently.
How do you handle several properties with different brands?+
A shared platform with per-property theming, content and rates, rather than one site pretending to be several or several sites duplicating the same work. Properties get editorial control over their own content; the group keeps the booking path, the performance budget and the measurement consistent.
Can our team update the site without a developer?+
That should be the default for the things you change often — offers, rooms, images, restaurant hours, seasonal content. We define a content model covering those and train the owner before launch. Structural changes still need a developer, and that is the correct boundary.
In this cluster
Review your booking funnel
A review of your current booking funnel with the drop-off measured stage by stage, so the rebuild is scoped against where guests actually leave rather than a redesign brief.
What happens next
- 1We reply within one business day.
- 2A 30-minute scoping call with a senior consultant.
- 3A written proposal with scope, team, and timeline.
Or reach us directly
