A responsive room, availability and direct booking-request journey for the property website.
Pilot-readyMature product foundation
Independent hotels, resorts and hospitality groups
Hotel Operating System
A mature operating foundation for hospitality businesses that need connected enquiries, reservations, operations and finance workflows across guest-facing and daily team work.
Available for scoped implementation and controlled pilots.


Operating problem
A specialist foundation shaped around the operating workflow.
Room inventory, rates, website enquiries and reservation follow-up are often split across spreadsheets, inboxes and disconnected booking tools. The result is duplicate work and uncertain availability.
Product definition
Hybrid by design.
The hosted workspace and website integration use one tenant-scoped product boundary.
A tenant-scoped operator workspace for inventory, rates, reservations, guests and audit history.
No card required. The workspace remains available in read-only mode after expiry while an upgrade is reviewed.
The product records an idempotent upgrade request for owner review and invoice handoff; no unverified payment success is shown.
Onboarding
- 1
Create the trial workspace
- 2
Add the property, rooms, rates and policies
- 3
Review the hosted booking route
- 4
Connect the same booking contract to WordPress or another website
Trial feature matrix
- Property and room setup
- Rates and 30-day inventory
- Booking requests
- Reservation workflow
- Team administration
- Payment-state changes
- Production service links
- CSV exports and custom domains
Two sides of the system
Clear for customers. Controlled for operators.
The public journey and the private operating workspace have separate responsibilities and access boundaries.
What the buyer or traveller can do
- Browse room types, availability and disclosed stay pricing
- Send a direct booking request with a visible reference
- See that confirmation and payment remain with the property
- Use a responsive booking journey on the property website
What the operating team can control
- Manage properties, room types, inventory, restrictions and rate plans
- Review website, manual and connected-channel reservation records
- Control booking confirmation and manual payment states
- Review sync health, reconciliation and audit history
Isolation and integration
Tenant boundaries stay explicit.
Each business is separated by tenant-scoped data and access checks. Operator sessions, public request routes and audit records have distinct boundaries; payment and external-provider actions remain owner controlled.
Website and service integration
A Hotel tenant can be linked to an approved Taxi tenant through the suite’s signed service boundary. The link prepares transfer requests in Taxi without exposing service credentials in the browser. It is configured and tested per pilot; requesting a pilot does not create a tenant or enable the link.
Review the product previewImplementation support
Included in a scoped rollout
- One agreed property operating scope
- Room, rate, tax and policy intake
- Branded public booking-request route
- Least-privilege operator handoff
- Booking and optional Hotel → Taxi QA
Getting started
Start with a useful product workspace.
- 01
Create the trial workspace
- 02
Add the property, rooms, rates and policies
- 03
Review the hosted booking route
- 04
Connect the same booking contract to WordPress or another website
Hotel pilot, setup and subscription terms are proposal based. No unverified public numeric price is shown.
Start with the real constraint
What needs to work better?
Share the product, platform or workflow that needs to be built, modernised or made easier to operate.
