Speaker script
Nine minute delivery
A timed product pitch and a separate appendix. The script contains about 857 words. At 130 words per minute, allow 144 seconds for transitions and explaining the visuals, then one minute of breathing room.
This is a pacing model checked against the actual browser sequence, not a recorded human oral rehearsal. The appendix is outside the timed pitch.
0:00 to 0:15 · 15 seconds
Guest service depends on back office coordination
A stay extension changes reservations and housekeeping. A supplier invoice crosses purchasing and finance. Independent groups need accountable workflows across existing systems. The operating case informs the design; wider demand remains unvalidated.
0:15 to 0:45 · 30 seconds
Connect hotel systems through shared services
Build shared workflow services and staff workspaces; connect the hotel systems that keep authoritative records. Knowledge, context and ownership travel across modules. Typed proposals and a separate execution service enforce permission, approval and readback. People still deliver care and physical service. Every adapter needs property specific validation; these are proposed connections.
0:45 to 1:10 · 25 seconds
Guest conversations
Start with guest conversations: the agent sees the whole request, current facts and unresolved items. Voice follows a separate gate. The table distinguishes the user, AI task, intended value and illustrative situation.
Property questions and conversations Multilingual voice notes Call handling and handover Reservation and availability enquiries
1:10 to 1:35 · 25 seconds
Guest service and experiences
Service extends beyond answers. Dispatchers need accepted tasks; custodians verify ownership; concierges check practical constraints; managers approve feasible preparation. Notice that the guest outcome and the staff user are distinct.
Service requests and updates Lost item returns Local itineraries Personalized stay preparation
1:35 to 2:00 · 25 seconds
Guest bookings and payment requests
These are later commitment workflows. A suggested option is not a confirmed booking. Eligible reservation changes require zero financial impact; priced extensions go to staff. Hosted payment requests are separate from payment release.
Dining and activity bookings Eligible changes and cancellations Approved room bookings Hosted payment requests
2:00 to 2:25 · 25 seconds
Rooms, food and service quality
Property teams need usable plans and verified service, not automatic room release. Forecasts use real occupancy, sales and stock. Quality and guest feedback feed human investigation and the next owned task.
Food demand and stock Housekeeping and maintenance plans Room cleaning quality checks Guest feedback and recurring issues
2:25 to 2:50 · 25 seconds
Commercial and event operations
Commercial modules join evidence with reviewable choices. Consent controls audiences; rate comparisons need equivalent terms; event layouts must be checked by operations. None of these examples establishes incremental revenue or automatic commercial authority.
Campaign preparation Market demand insights Event layouts and setup Rate and parity checks
2:50 to 3:15 · 25 seconds
Finance and resource use
Finance must separate matching, invoice preparation and daily close. Facilities uses consumption evidence and a different approval boundary. Shared controls connect the modules without giving an analytical result authority to move money or equipment.
Payment settlement reconciliation Supplier invoice approval Guest ledger reconciliation Resource use and intervention proposals
3:15 to 3:40 · 25 seconds
People, identity and shared knowledge
People and information need stewardship too. Staff opt into feedback; owners accept commitments; stewards resolve identity ambiguity. Approved property knowledge is reusable, but broader enterprise sources require their own permission tests.
Guest profile linking Voluntary staff feedback Staff commitments and reminders Approved knowledge and corrections
3:40 to 4:05 · 25 seconds
Governed data and cross system answers
Data stewards approve definitions and resolve feed failures. Analysts ask permitted questions through controlled computations. Both need source dates, reconciliation and clear gaps before an answer can be trusted.
4:05 to 4:30 · 25 seconds
Leadership reporting and scenarios
Reporting packs and objective updates need reproducible inputs and owner approval. Simulation explores choices with visible assumptions; it is separate from actual results and has no operational write path.
Leadership reporting packs Operating decision scenarios Evidenced objective updates
4:30 to 4:55 · 25 seconds
Acquisition and development
Development work has different sources and users: acquisition analysts, project directors and site managers. Each receives evidence and missing coverage, while professional due diligence, inspections and financial commitments remain human decisions.
Development site screening Development oversight Site photo evidence
4:55 to 5:55 · 60 seconds
An extra night changes reservations and room work
A guest asks for another night. Staff verifies identity. The property system supplies current availability, rates and stay state; approved knowledge supplies the terms. AI prepares options and flags the room work implications. A priced extension is not an eligible automatic zero financial impact change. Reservations staff confirms the guest’s choice and handles it in the native system. Only an actual confirmed record drives the reply. The changed departure reaches housekeeping, where a supervisor adjusts the plan and accepts ownership. A failed or uncertain change stays with reservations; no false confirmation or blind retry. Housekeeping acknowledgement remains distinct from completing and verifying physical work.
5:55 to 6:50 · 55 seconds
From supplier invoice to an approved accounting draft
A supplier invoice reaches accounts payable. AI extracts fields; rules check arithmetic, supplier identity and duplicates. Procurement owns the order and receipt. A missing receipt, price variance or duplicate stays with an AP owner. The budget holder approves expenditure; finance reviews coding, exceptions and separation of duties. Only an enabled draft integration prepares the approved accounting record. Readback verifies its reference and status; failure remains an owned exception. Posting, scheduling and payment release stay in the existing finance process with separate authority. Scanned bank details never update the supplier master. The intended value is less validated handling effort with an intact approval trail.
6:50 to 7:20 · 30 seconds
Measure completed work and total operating cost
Measure completed work, not AI answer volume. Include unresolved handovers, room readiness and finance exceptions alongside active effort. Total cost includes review, content, integration, infrastructure and support. The commercial hypothesis is modular recurring software by group, property and room, with separately scoped implementation. Shared service reuse may improve economics; accepted pricing, savings and margin still need evidence.
7:20 to 7:45 · 25 seconds
Base annual software scenario: USD 262m
Future full platform annual software scenarios are about USD 53m, USD 262m and USD 787m. These are assumptions, not the narrower first release opportunity. Coverage, eligibility and additive pricing remain unvalidated, with mixed stock and dates. Scope excludes China including Hong Kong and Macao, Russia and North Korea. Full model and launch bridge follow.
7:45 to 8:15 · 30 seconds
Compete against complete hospitality workflows
Native platforms and specialists already deliver overlapping hotel workflows. Mews, Cloudbeds, HelloShift, Duve, hotelkit and Sweeply are substantive alternatives. Aphy and Inntelo challenge orchestration directly, but marketed scope is not complete verified execution. Compare the same job, integration burden, staff effort and total cost. Lower coordination effort with clear ownership remains a hypothesis, not a demonstrated advantage.
8:15 to 8:45 · 30 seconds
Start with a bounded guest service release
Start with controlled property knowledge, reviewed replies, read only enquiries and staff initiated tasks. The customer supplies truth, dispatch coverage and business testers; the provider builds and monitors agreed services within defined support terms. Demo tests do not establish operator acceptance. Test live identity and rates, mixed requests, failures and fallback. Later modules need separate owners, permissions and acceptance.
8:45 to 9:00 · 15 seconds
Agree the first operating validation
Validate priority work, source access and accountable handovers. Protect business testing capacity and test a real commercial offer. Full requirements and additional candidates follow in the appendix.
End of timed pitch. Open the separate appendix.