Product definition
Full requirements, shared controls, operating design, all canonical workflows and candidate families.
Open product reportProduct MarkdownCatalogue JSONReference and evidence
Separate from the pitch
The main presentation ends before this appendix. This appendix holds the full product reference, market assumptions and detailed reports.
Product status: proposed platform. Developer tests in a Demo environment do not establish business acceptance or accepted live performance. Most capabilities remain proposed.
Core buyer: independent small and midsize groups operating multiple hospitality properties. Major global brand portfolios are excluded, including those run by regional franchise managers.
Market scope
Geographies and commercial assumptions
Priority markets are Middle East, Europe, Latin America and the Caribbean, Canada, the United States and Australia. They are priorities within the wider eligible scope.
Worldwide scope excludes China, Russia and North Korea. Hong Kong and Macao are included in the China exclusion. Europe includes Türkiye and Cyprus; Egypt is in Africa; Mexico and the Caribbean are in Latin America. Country rows are assigned once.
Covered annual software scenarios: about USD 53m, USD 262m and USD 787m.
Eligibility and pricing assumptions. Not a verified global total addressable market, observed demand or a buyer census. The model quantifies 158 of 244 eligible reporting areas; 86 remain unquantified. Stock definitions and dates vary.
Priority geography base scenarios
Rounded annual software scenarios, USD. The Latin America amount includes the Caribbean. Priority geography amounts do not sum to the covered global subtotal; other eligible regions remain in the model. All regional scenarios and coverage.
Buyer boundary and stock conversion
The working model uses 2 to 100 operating properties and no more than 20,000 operating rooms at parent or operator level, with at least two qualifying independent properties. This is an unvalidated commercial assumption, not approved policy or an industry standard.
Single property, larger enterprise and franchise routes require separate economics. A mixed manager contributes only qualifying independent properties. Parent control and purchasing rights must be checked; one group is not counted again for each country.
About 28.9 million reported rooms are filtered through assumed scope, independent and group shares. The base gives about 2.7 million eligible rooms, 32,000 properties and 4,600 buyer equivalents. These are modeled equivalents, not identified or deduplicated companies. Missing areas are not zero.
Pricing, launch scope and sales capacity
The base annual price hypothesis is USD 12,000 per group, plus USD 2,400 per property, plus USD 48 per room. A group with seven properties and 630 rooms gives USD 59,040 for the future full platform. The assumed launch package at half price gives USD 29,520. These are arithmetic illustrations, not accepted quotes or willingness to pay evidence.
Full platform opportunity, conditional launch opportunity and sales capacity answer different questions. The conditional launch serviceable available market covers UK, Ireland, Canada, US, Australia and UAE only. Its low, base and high annual software scenarios are about USD 75k, USD 2.0m and USD 17m, conditional on compatible systems, language, workflow fit and operating readiness.
The capacity based serviceable obtainable market gives about USD 55k, USD 510k and USD 2.4m in ending annual recurring revenue in commercial year three. These are sales, onboarding and retention assumptions, not contracts, pipeline or a share of total market.
Annual recurring revenue is a recurring run rate, not recognized annual revenue. Implementation, bespoke connectors, usage, managed services, customer savings, funding, valuation and payment volume are separate. No generally saleable market, accepted price, margin, ROI or funding need is established.
First release and operating responsibilities
Evidence and action boundaries
What the benchmark supports
An anonymous operator case reports developer tested email FAQ, messaging and read only reservation components in a Demo environment. Business acceptance and accepted live performance are not established.
Voice is on hold and testable. Reservation change completion reports conflict and acceptance is unresolved. Most enterprise workflows remain proposed.
What the first release proposes
Approved property knowledge, reviewed replies, read only enquiries on an agreed property management system adapter and staff initiated tasks. A property management system is the hotel system of record for reservations and availability.
People review guest messages, accept tasks, perform physical work and verify results. Complaints, negative and sensitive messages go to staff without an automatic guest reply. Invoice requests route to the relevant property or finance owner without an AI draft.
Ownership, delivery and measures
Customer content and data owners approve facts and access. Business testers supply representative enquiries and protected testing time. Dispatchers and supervisors own acceptance, physical fulfilment and exceptions. The provider owns reliable integrations, traceability, controls, monitoring and agreed technical support.
Discovery of roughly 2 to 4 weeks and first release hardening and business testing of roughly 8 to 16 weeks are conditional discussion assumptions. They depend on source access, reuse, one stable adapter, content, named testers and delivery capacity. They do not cover delivery of all 36 workflows.
A proposed cell is one product or technical lead, two integration engineers, one full stack engineer and shared quality, security and design support. Availability is unconfirmed. No support service level agreement is created by this document.
Measure useful drafts, factual and privacy errors, unresolved handovers, verified task outcomes, review burden and total operating cost against an agreed baseline. Zero unapproved sends or writes is a test gate, not a guarantee about all future traffic. A routed task, sent reply or closed conversation does not establish completed physical work.
Higher authority remains separate
Reservation enquiries create no booking, hold, change, cancellation or payment link. Private status requires sufficient identity checks and minimal disclosure. Existing systems retain authority.
Later reservation changes require a permitted field change, zero financial impact rules, exact approval, fresh checks, duplicate prevention and source readback. New bookings and hosted payment requests need separate provider rights and business acceptance. Card data stays outside the assistant. Capture, refunds, bank changes and supplier payments require separate authority. Autonomous and physical controls are disabled by default.
Complete product reference
36 canonical workflows
Simple examples below are illustrative and proposed. Stage codes describe proposed sequencing, not accepted live capability. All original requirements and 39 additional candidates remain in the linked product report.
36 of 36 workflows
No workflows match. Reset the filters or try another term.
UC01Keep guest requests togetherR1
Guest service & reservations
Illustrative proposed use: A guest emails after a chat with two questions about the same stay.
- Who needs it
- Reservations agents and duty managers
- Guest contacts the property
- Assistant gathers open requests
- Agent sends a complete reply
- What people do
- An agent checks every answer and sends the reply; a supervisor owns queue coverage.
- Result to verify
- One review queue shows the conversation, each open request and its owner.
- Authority and limit
- R1 permits staff approved messages and internal records; unclear guest identities remain separate.
UC02Assign and track service requestsR1
Guest service & reservations
Illustrative proposed use: A guest reports a broken light and asks for fresh towels.
- Who needs it
- Guest services agents and department dispatchers
- Guest reports a need
- Dispatcher accepts linked tasks
- Staff records the work done
- What people do
- People assess urgency, accept assignments, perform the work and verify the outcome before a reviewed reply.
- Result to verify
- Each request has an owner and visible progress, including any work still outstanding.
- Authority and limit
- Creating a task does not complete the work; emergencies follow the human emergency procedure.
UC03Return a guest’s lost itemR2
Guest service & reservations
Illustrative proposed use: A guest asks whether a coat was left after checkout.
- Who needs it
- Housekeeping staff and guest services agents
- Staff logs a found item
- Assistant suggests possible matches
- Custodian approves the return
- What people do
- The property custodian verifies ownership and approves disclosure and release before arranging return.
- Result to verify
- The claim has a custody record and a confirmed return or an open exception.
- Authority and limit
- A suggested match proves no ownership; shipment purchases and payments need a separate process.
UC04Understand guest voice messagesR2
Guest service & reservations
Illustrative proposed use: A guest sends a voice message in another language asking about arrival and breakfast.
- Who needs it
- Guest services agents and reservations staff
- Guest sends a voice note
- Assistant transcribes and translates
- Agent approves a reply
- What people do
- A staff member checks names, dates and instructions and approves the text or audio reply.
- Result to verify
- Staff can review the original audio, translated request and each unanswered item together.
- Authority and limit
- Only tested languages and formats qualify; uncertain speech needs clarification and adds no booking authority.
UC05Answer calls and arrange handoverR2
Guest service & reservations
Illustrative proposed use: A caller asks an approved property question and then requests a person.
- Who needs it
- Callers and reservations staff
- Guest calls an enabled number
- Assistant answers within approved scope
- Staff receives a handover
- What people do
- Staff take complaints and complex cases; they own callbacks when a transfer fails.
- Result to verify
- The caller receives permitted information, a transfer or an assigned callback request.
- Authority and limit
- Live voice needs its own release approval, tested telephone route and staffed fallback; bookings and payments remain separate.
UC06Prepare a useful local itineraryR2
Guest service & reservations
Illustrative proposed use: A guest asks for a local afternoon plan with step free access.
- Who needs it
- Concierges and guest services staff
- Guest explains interests and needs
- Assistant drafts feasible options
- Guest chooses with staff help
- What people do
- Concierge staff check changing details, accessibility and unusual arrangements and handle any booking handoff.
- Result to verify
- A proposed itinerary shows what is suggested, what is verified and what still needs confirmation.
- Authority and limit
- Suggestions are not bookings; provider availability and accessibility require current confirmation.
UC07Plan food orders and staffingR2
Property operations & sustainability
Illustrative proposed use: A restaurant manager plans breakfast ingredients for a busy weekend.
- Who needs it
- Food and beverage managers, chefs and buyers
- Manager reviews occupancy and sales
- Assistant forecasts demand and gaps
- Manager approves the plan
- What people do
- Chefs check recipes, buyers place orders and managers approve staffing in the existing systems.
- Result to verify
- A draft plan shows likely demand, stock needs and uncertainty for a defined service.
- Authority and limit
- Begin with advice only; no automatic supplier order, roster change or ingredient substitution.
UC08Prepare campaigns for permitted audiencesR2
Commercial & guest experience
Illustrative proposed use: A marketing manager prepares a return stay offer for guests who agreed to marketing.
- Who needs it
- Marketing managers and revenue owners
- Manager sets the campaign objective
- Assistant drafts audience and content
- Owners approve before export
- What people do
- People verify consent and commercial terms, approve the audience and send through the marketing system.
- Result to verify
- A reviewable campaign brief connects the audience, offer and creative to an explicit objective.
- Authority and limit
- No automatic campaign send or paid spend; missing consent excludes a contact.
UC09Explain changes in market demandR2
Commercial & guest experience
Illustrative proposed use: A revenue manager reviews a demand shift for next month’s weekends.
- Who needs it
- Revenue managers
- Licensed market data arrives
- Assistant explains comparable changes
- Revenue manager decides action
- What people do
- Revenue staff check local context and source comparability and apply any changes in the native system.
- Result to verify
- A cited market brief shows possible actions and the evidence and uncertainty behind them.
- Authority and limit
- Read only in R2; stale or incomparable data limits advice and cannot trigger an automatic price change.
UC10Coordinate guest offers and preparationR2
Commercial & guest experience
Illustrative proposed use: A guest opts into an available service and staff need to prepare it before arrival.
- Who needs it
- Guest services and marketing teams
- Eligible stay creates a prompt
- Owner approves an offer or task
- Staff records actual delivery
- What people do
- People check consent and capacity, approve contact and tasks, and perform or arrange the chosen service.
- Result to verify
- The guest’s choice connects to owned preparation and a record of what was actually delivered.
- Authority and limit
- No automatic purchase, upgrade or paid extra; a task still needs human fulfilment.
UC11Check possible duplicate guest profilesR2
Commercial & guest experience
Illustrative proposed use: A data steward reviews two records that may belong to the same guest.
- Who needs it
- Guest data stewards and guest teams
- Permitted profile records change
- Assistant suggests possible matches
- Steward approves or keeps separate
- What people do
- Stewards decide uncertain links, approve source corrections and handle any mistaken match.
- Result to verify
- An approved linked guest view shows the evidence while preserving the original records and permissions.
- Authority and limit
- Begin with analytical links only; matching does not grant consent or permission to merge source records.
UC12Plan an event room layoutR3
Commercial & guest experience
Illustrative proposed use: A client asks whether a venue can support a dinner and a presentation.
- Who needs it
- Event sales and banqueting teams
- Client shares event needs
- Assistant drafts layout options
- Venue team approves setup
- What people do
- Venue professionals verify capacity, access, equipment and safety; staff approve the final setup and perform the work.
- Result to verify
- A versioned visual proposal and setup specification give the client and staff a shared plan.
- Authority and limit
- A rendered layout certifies no safety and commits no booking, contract or supplier order.
UC13Check comparable room pricesR2
Commercial & guest experience
Illustrative proposed use: A revenue manager investigates different displayed prices for the same room and dates.
- Who needs it
- Revenue staff
- Staff selects equivalent offers
- System checks terms and amounts
- Revenue owner investigates differences
- What people do
- Revenue staff verify that offers are comparable and decide any correction in the native system.
- Result to verify
- An exception list shows evidenced differences with dates, terms and possible causes.
- Authority and limit
- Initial access is read only; an unavailable rate or failed connection is not evidence of a pricing breach.
UC14Plan cleaning and maintenance workR2
Property operations & sustainability
Illustrative proposed use: A supervisor prepares tomorrow’s cleaning plan while engineering schedules recurring fault checks.
- Who needs it
- Housekeeping supervisors and engineering managers
- Teams review rooms and capacity
- Assistant proposes separate work plans
- Supervisors assign and review work
- What people do
- Supervisors assign people, engineers diagnose faults and authorized staff decide room readiness after actual work.
- Result to verify
- Coordinated proposed schedules show cleaning priorities, maintenance windows and capacity gaps.
- Authority and limit
- Advice comes first; no automatic shift changes, room release, equipment control or deferred safety inspection.
UC15Support a room cleaning checkR3
Property operations & sustainability
Illustrative proposed use: An attendant completes an approved checklist and a supervisor reviews a possible missing amenity.
- Who needs it
- Room attendants and housekeeping supervisors
- Attendant records checklist evidence
- Assistant flags visible omissions
- Supervisor checks before room release
- What people do
- People inspect cleanliness, equipment and safety, resolve disputed flags and authorize room release.
- Result to verify
- An advisory checklist highlights items for inspection and records the supervisor’s decision.
- Authority and limit
- Photos are optional under approved privacy rules and cannot prove hygiene or release a room automatically.
UC16Explain payment settlement differencesR2
Finance & procurement
Illustrative proposed use: An analyst investigates why a payment processor’s settlement differs from expected receipts.
- Who needs it
- Finance analysts and financial controllers
- Finance imports settlement records
- System matches references and amounts
- Analyst reviews unresolved differences
- What people do
- Finance validates exceptions and approves any proposed accounting correction through the existing workflow.
- Result to verify
- A match set and exception queue show explained differences and any incomplete cash picture.
- Authority and limit
- The first release is read only; matching authorizes no refund, transfer, supplier payment or ledger posting.
UC17Prepare invoices for approvalR2
Finance & procurement
Illustrative proposed use: A supplier invoice arrives and must be checked against the order and receipt.
- Who needs it
- Accounts payable clerks and budget holders
- Invoice enters the approved inbox
- System checks and drafts coding
- Budget holder and finance approve
- What people do
- People approve expenditure and exceptions; supplier bank changes use an independently verified process.
- Result to verify
- A draft invoice and approval task preserve the original evidence and show any mismatch.
- Authority and limit
- Enabled writes are limited to draft invoice records; no automatic supplier creation, bank edit or payment release.
UC18Check the nightly guest ledgerR2
Finance & procurement
Illustrative proposed use: A night auditor checks guest charges, payment batches and bank timing at the agreed cutoff.
- Who needs it
- Night auditors and financial controllers
- Nightly reporting cutoff arrives
- System reconciles charges and tenders
- Controller reviews close exceptions
- What people do
- Auditors validate unusual items and control totals; the controller approves any proposed journal.
- Result to verify
- A reproducible nightly report separates folio differences, settlement timing and unresolved close items.
- Authority and limit
- Initial mode is read only; late bank feeds stay incomplete and no invented balancing entry is permitted.
UC19Understand staff working conditionsR2
People & everyday coordination
Illustrative proposed use: Staff voluntarily answer an approved short question about their working week.
- Who needs it
- HR leads and participating staff
- HR approves a voluntary question
- Staff choose whether to respond
- HR reviews safe aggregate themes
- What people do
- HR checks privacy, interprets themes and leads agreed improvement actions with staff.
- Result to verify
- A sufficiently large group can receive an aggregate trend and an HR reviewed action plan.
- Authority and limit
- No individual sentiment score or automated employment decision; small groups are suppressed and sensitive disclosures follow a confidential human route.
UC20Track agreed staff commitmentsR2
People & everyday coordination
Illustrative proposed use: A manager forwards an authorized meeting note containing actions that need confirmed owners.
- Who needs it
- Employees and team managers
- Staff shares an approved source
- Assistant proposes actions and dates
- People accept and confirm completion
- What people do
- People accept assignments, set priorities, resolve ownership disputes and provide completion evidence.
- Result to verify
- A shared queue links accepted commitments to their source and shows what remains open.
- Authority and limit
- Start with proposed tasks and optional reminders; external follow ups need explicit communication permission.
UC21Review energy and water useR3
Property operations & sustainability
Illustrative proposed use: A facilities manager investigates an unusual overnight energy reading.
- Who needs it
- Facilities and sustainability managers
- Approved meter readings arrive
- Assistant flags a possible anomaly
- Facilities reviews an intervention
- What people do
- Facilities checks equipment limits and carries out approved work; sustainability and finance validate any reported savings.
- Result to verify
- A resource dashboard and intervention proposal show the baseline, uncertainty and observed follow up.
- Authority and limit
- Begin read only; equipment control needs separate engineering approval, safe limits and local override.
UC22Connect reliable operational dataF0
Knowledge, data & leadership
Illustrative proposed use: A steward connects the permitted reservation fields needed for the first release.
- Who needs it
- Data stewards and analysts
- Owner approves fields and purpose
- System checks and transforms feeds
- Steward publishes a trusted view
- What people do
- Domain owners approve data definitions and stewards resolve failed checks and source corrections.
- Result to verify
- A governed data view shows definitions, source lineage, freshness and any quality issue.
- Authority and limit
- F0 covers the first release slice; the hub cannot silently correct operational systems or call stale data current.
UC23Answer approved operational questionsR2
Knowledge, data & leadership
Illustrative proposed use: A manager asks how booking pickup compares with budget for an authorized property.
- Who needs it
- Analysts and managers
- Manager asks a defined question
- Controlled queries calculate the answer
- Manager reviews evidence and gaps
- What people do
- People clarify business definitions, review incomplete answers and decide what action to take.
- Result to verify
- An answer, chart or permitted export uses approved definitions and cites the supporting data.
- Authority and limit
- Read only with property and data access checks; no arbitrary database commands or invented joins.
UC24Find the current approved answerR1
Knowledge, data & leadership
Illustrative proposed use: A front office agent looks up the current breakfast policy for the correct property.
- Who needs it
- Employees and content owners
- Staff asks a scoped question
- Assistant retrieves approved content
- Staff reviews a cited answer
- What people do
- Content owners approve publication and corrections; staff review answers and raise gaps or conflicting policies.
- Result to verify
- A cited answer or draft shows current authorized guidance, with a review queue for improvements.
- Authority and limit
- Search is read only and publication needs a separate role; edited replies do not automatically become policy.
UC25Prepare a leadership reporting packR2
Knowledge, data & leadership
Illustrative proposed use: A finance leader prepares the monthly pack using an agreed cutoff and reporting template.
- Who needs it
- Finance leaders and executive assistants
- Reporting period reaches its cutoff
- Assistant drafts figures and commentary
- Owners validate and approve release
- What people do
- Owners validate figures and explanations and the authorized report owner checks the audience before release.
- Result to verify
- A versioned reporting pack links its figures and commentary to reproducible evidence.
- Authority and limit
- No automatic distribution to boards, lenders or investors; unverified explanations stay labelled as hypotheses.
UC26Compare possible operating decisionsR3
Knowledge, data & leadership
Illustrative proposed use: Leaders explore how later checkout might affect cleaning capacity.
- Who needs it
- Leaders and operational specialists
- Team defines a decision and baseline
- Model compares assumptions and ranges
- Experts assess the tradeoffs
- What people do
- Domain experts approve assumptions and judge plausibility; any chosen intervention follows normal operational approvals.
- Result to verify
- A modeled comparison shows possible outcomes, constraints and sensitivity to uncertain assumptions.
- Authority and limit
- A simulation is not a forecast guarantee and cannot change reservations, staffing, prices or equipment.
UC27Screen potential development sitesR2
Acquisition & development
Illustrative proposed use: An analyst reviews new site listings against an approved geographic and asset brief.
- Who needs it
- Development analysts and investment teams
- Permitted site records arrive
- Assistant organizes and ranks evidence
- Analyst qualifies the opportunity
- What people do
- Analysts verify ownership, planning and constraints; investment teams decide whether to commission further checks.
- Result to verify
- A ranked digest and evidence linked lead show fit, missing information and next review tasks.
- Authority and limit
- No owner contact, offer, bid, registration or financial commitment; screening does not replace professional due diligence.
UC28Review development project progressR2
Acquisition & development
Illustrative proposed use: A project director reviews a delayed update that conflicts with the approved budget and programme.
- Who needs it
- Project directors and project managers
- Owners submit project updates
- Assistant compares approved baselines
- Managers resolve gaps and risks
- What people do
- Project professionals verify status and risk; authorized officers approve any budget, variation or baseline change.
- Result to verify
- A review snapshot shows project evidence, exceptions and accountable follow up tasks.
- Authority and limit
- Initially read only with internal tasks; reported or photographed progress is not certified completion.
UC29Organize site progress photosR2
Acquisition & development
Illustrative proposed use: A site manager reviews weekly photos and discovers that a required viewpoint is missing.
- Who needs it
- Site managers and project directors
- Staff uploads permitted site photos
- Assistant groups views and flags gaps
- Site manager verifies the report
- What people do
- Site professionals confirm dates, investigate visible differences and approve the internal report.
- Result to verify
- A dated gallery and coverage report make missing evidence and comparable views easy to find.
- Authority and limit
- Photos certify no completion, safety or payment milestone; external publication needs separate approval.
UC30Find recurring guest experience issuesR2
Knowledge, data & leadership
Illustrative proposed use: A quality manager investigates repeated noise comments across permitted reviews and messages.
- Who needs it
- Quality managers, guest services and leaders
- Permitted feedback enters analysis
- Assistant suggests themes with uncertainty
- People review and assign improvements
- What people do
- People review complaints and sensitive cases, validate the interpretation and decide improvement work.
- Result to verify
- A theme dashboard and review queue show recurring issues with source coverage and uncertainty.
- Authority and limit
- Inferred sentiment is not surveyed satisfaction; negative cases get no automatic reply and compensation needs separate approval.
UC31Prepare updates on agreed objectivesR2
Knowledge, data & leadership
Illustrative proposed use: A department head submits evidence for a monthly objective and explains a changed target.
- Who needs it
- Department heads and executive support staff
- Reporting cycle requests owner updates
- Assistant checks evidence and changes
- Owners attest and reviewer approves
- What people do
- People set targets, verify progress, explain changes and approve the final update.
- Result to verify
- A versioned update pack distinguishes evidenced progress, changed definitions and missing submissions.
- Authority and limit
- Missing information stays unknown; no automatic target change, external distribution or individual performance assessment.
UC32Confirm a dining or activity bookingR2
Guest service & reservations
Illustrative proposed use: A guest chooses an available in house activity and asks staff to reserve a place.
- Who needs it
- Concierges, food and beverage staff and guest services
- Guest confirms the offered terms
- Staff approves a checked booking
- System reads back provider confirmation
- What people do
- People approve commitments, confirm provider arrangements and perform the service; staff reconcile uncertain booking outcomes.
- Result to verify
- The guest receives a reviewed confirmed reference or a clearly pending request with an owner.
- Authority and limit
- No implicit charge or deposit; paid commitments need UC36 and uncertain results must be checked before retrying.
UC33Answer availability and reservation questionsR1
Guest service & reservations
Illustrative proposed use: A guest asks about room availability and the status of an existing reservation.
- Who needs it
- Reservations agents and front office staff
- Agent verifies property and identity
- System retrieves permitted current facts
- Agent reviews and sends the answer
- What people do
- Staff check the complete draft, resolve unanswered items and approve the reply.
- Result to verify
- A reviewed draft gives permitted availability, indicative price, policy or status information with its query time.
- Authority and limit
- Read only with no booking, hold, change, cancellation or payment link; private status needs verified identity and excludes sensitive stay details.
UC34Review eligible changes or cancellationsR2
Guest service & reservations
Illustrative proposed use: A verified guest requests a permitted reservation change with no financial impact.
- Who needs it
- Reservations agents and front office staff
- Rules check identity and eligibility
- Staff approves the exact proposed change
- System rechecks, writes and reads back
- What people do
- Staff approve both the specific change and reply and handle exceptions or uncertain results.
- Result to verify
- An approved change is confirmed only after the actual reservation state has been checked.
- Authority and limit
- Separate write permission, approved eligibility and zero financial impact are required; any price change blocks execution and acceptance is unresolved.
UC35Create an approved new reservationR3
Guest service & reservations
Illustrative proposed use: A guest accepts a checked offer and explicitly asks the reservations team to book.
- Who needs it
- Reservations teams and commercial operations staff
- Guest accepts complete booking terms
- Staff approves a revalidated proposal
- System creates once and reads back
- What people do
- Staff approve the booking commitment, resolve commercial exceptions and review the confirmation.
- Result to verify
- A reservation is reported as confirmed or pending according to the actual source system result.
- Authority and limit
- A separately gated R3 proposal requiring booking rights and mature write controls; enquiries grant no booking or hold authority.
UC36Request payment through an approved providerR3
Guest service & reservations
Illustrative proposed use: Finance approves a payment request for a defined reservation amount and the guest pays through the provider.
- Who needs it
- Finance and reservations staff and guests
- Staff approves purpose and amount
- Guest uses a hosted provider link
- System verifies status and reconciliation
- What people do
- Finance controls requests and exceptions; the guest authorizes payment in the provider interface.
- Result to verify
- A tracked payment request shows a verified provider result and reconciliation status.
- Authority and limit
- A separately gated R3 proposal for hosted links only; no card details in messages and no capture, refund or bank changes.
What the stage codes mean
F0 is the shared foundation. R1 is the proposed first release. R2 and R3 are later modules with their own readiness and acceptance gates. Codes do not establish delivered capability.
39 additional candidate families
Historical candidates are unprioritized, proposed and unvalidated. They are separate from the canonical workflow count.
| ID | Candidate | Department | Boundary |
|---|---|---|---|
| C01 | Digital arrival and mobile keys | Front office | Identity verification, lock hardware and native check in approvals; no automatic access credential issuance in this draft. |
| C02 | Departure folio review and split billing | Front office and finance | Authoritative folio, verified identity, billing permissions and dispute ownership; financial adjustments need explicit authority. |
| C03 | Secure guest casting | IT and guest services | Device pairing and automatic credential/session cleanup; primarily vendor integration rather than an AI differentiator. |
| C04 | Sold out date waiting lists | Reservations | Opt in contact, queue fairness and live inventory recheck; a notification is not a hold. |
| C05 | Room move coordination | Operations | Room readiness and guest consent, baggage/privacy controls and coordinated PMS updates. |
| C06 | Corporate and group self service | Sales and reservations | Account authentication, negotiated rates, rooming list access and complex billing; requires a separate commercial workflow. |
| C07 | Digital food ordering | Food and beverage | POS/KDS acceptance, allergens and delivery ownership; payment is a separately approved stage. |
| C08 | Guest surveys and review management | Quality and marketing | Valid survey design, platform terms and human response ownership. Historical selective positive review solicitation is not adopted; avoid review gating. |
| C09 | Gift card administration | Finance and marketing | Issuer liability, balances, redemption and fraud controls; no automatic issuance or value movement. |
| C10 | Employee access lifecycle | HR and IT | Authoritative hire/leaver events, reversible provisioning and verified deactivation; access actions require independent controls. |
| C11 | Workforce scheduling | HR and operations | Availability, skills and approved employment/roster constraints; managers publish schedules, with worker consultation. |
| C12 | Chargeback evidence preparation | Finance | Verified evidence sources, deadlines and human submission approval; risk controls and representment need provider integration. |
| C13 | Maintenance parts and housekeeping supplies | Procurement and operations | Stock units, lead times, usage history and buyer approval; start with draft orders. |
| C14 | Coaching training and recognition | HR and managers | Transparent purpose and human review; no individual decisions based solely on automated scores or guest sentiment. |
| C15 | Receivables and collections | Finance | Credit policy, aged ledger reconciliation and approved contact rules; no autonomous dunning or credit decision. |
| C16 | Supplier payment batches | Finance | Segregated payment approval, verified supplier bank records and bank controls; separate from UC17 invoice approval. |
| C17 | Paid media and incrementality | Marketing | Spend limits, audience permission, experiment design and approved campaign controls; ad platform setup is a dependency. |
| C18 | Commercial inventory and ancillary recommendations | Revenue | Comparable net contribution, channel rights and source readback; automated pricing or closure needs separate authority. |
| C19 | Corporate rate synchronization | Revenue and sales | Contractual rate source, code ownership and safe rollback/reconciliation; no silent overwriting of live rates. |
| C20 | Group lead triage and displacement analysis | Sales and revenue | Qualified enquiry, CRM ownership and validated displacement model; final quotes and commitments stay with staff. |
| C21 | Sales proposal preparation | Sales | Approved offer templates, versioning and authorized signatory; drafting cannot bind the operator. |
| C22 | Fit out procurement coordination | Development and procurement | Approved specifications, budget and supplier authority; software assists coordination without approving expenditure. |
| C23 | Software license and IT asset intelligence | IT and finance | Reliable inventory and usage, renewal ownership and human decisions; no automatic license cancellation or device disable. |
| C24 | Data rights request coordination | Privacy and IT | Verified requester, source coverage, retention exceptions and privacy owner review; no automatic deletion across systems. |
| C25 | Document and contractor evidence expiry | Compliance and development | Qualified reviewers define required evidence and dates. OCR flags missing/expired documents; it cannot certify coverage or legal compliance. |
| C26 | Property opening and ramp up | Openings operations and commercial | Stage gates, dependencies and accountable readiness checks; a checklist does not prove a property is safe or ready. |
| C27 | Operational incident and compliance records | Safety operations and facilities | A qualified owner must define severity, emergency routes and required inspection evidence; no AI certification or replacement of emergency systems. |
| C28 | Month end close coordination | Finance | Approved close checklist, period locks and controller sign off; automation cannot bypass accounting controls. |
| C29 | Intercompany consolidation | Finance | Entity/currency policies, reconciled balances and approved adjustments; jurisdictional accounting validation required. |
| C30 | Fixed asset and capital tracking | Finance and development | Asset register, depreciation policy and authorized capital approvals; native accounting system remains authoritative. |
| C31 | Expense review | Finance and employees | Approved expense policy, evidence and separation of duties; reimbursement is a separate financial action. |
| C32 | Tax mapping and reporting assistance | Finance | Qualified tax owner, approved jurisdiction/version rules and native filing controls; no automated legal compliance assertion or filing. |
| C33 | Financial control evidence | Finance and assurance | Control matrix, evidence sampling and independent reviewer; automated checks do not constitute an audit opinion. |
| C34 | Occupancy and demand forecasting | Revenue | Historical coverage, forecast horizon and reference baseline; measure error before using in commercial decisions. |
| C35 | Labor and revenue analysis | Operations HR and finance | Aligned business date, roster/pay data permission and consistent revenue definitions; no automatic staffing cuts. |
| C36 | Channel contribution and pace | Revenue and finance | Commission/cost completeness, comparable periods and attribution; recommendations begin read only. |
| C37 | Loyalty programme operations | Marketing and finance | Guest consent, reward liability and transparent eligibility; no assumed enrollment or automatic points/value changes. |
| C38 | Promotion abuse review | Revenue and security | Validated risk signals, fair review and appeal; automatic code revocation needs separately approved rules. |
| C39 | Overbooking and relocation planning | Reservations and duty management | Verified availability, commercial agreements and guest communication ownership; staff approve relocation and any spend. |
Slide evidence
Sources behind the pitch
Source material is the cleared product definition, covered market model and competitive landscape. Dates, scenario assumptions and evidence limits remain in the detailed reports.
- Guest service depends on back office coordination
Product and buyer - Connect hotel systems through shared services
Architecture and system authority - Guest conversations
Property questions and conversations Multilingual voice notes Call handling and handover Reservation and availability enquiries - Guest service and experiences
Service requests and updates Lost item returns Local itineraries Personalized stay preparation - Guest bookings and payment requests
Dining and activity bookings Eligible changes and cancellations Approved room bookings Hosted payment requests - Rooms, food and service quality
Food demand and stock Housekeeping and maintenance plans Room cleaning quality checks Guest feedback and recurring issues - Commercial and event operations
Campaign preparation Market demand insights Event layouts and setup Rate and parity checks - Finance and resource use
Payment settlement reconciliation Supplier invoice approval Guest ledger reconciliation Resource use and intervention proposals - People, identity and shared knowledge
Guest profile linking Voluntary staff feedback Staff commitments and reminders Approved knowledge and corrections - Governed data and cross system answers
Governed data connections Cross system questions - Leadership reporting and scenarios
Leadership reporting packs Operating decision scenarios Evidenced objective updates - Acquisition and development
Development site screening Development oversight Site photo evidence - An extra night changes reservations and room work
Reservation enquiries Change authority Housekeeping plan - From supplier invoice to an approved accounting draft
Supplier invoice requirements - Measure completed work and total operating cost
Measurement and total cost - Base annual software scenario: USD 262m
Market model and assumptions - Compete against complete hospitality workflows
Named alternatives and coverage - Start with a bounded guest service release
Sequence and evidence Operating ownership - Agree the first operating validation
Participation decisions
Public vendor examples retain their attribution and deployment limits in the landscape report. Vendor reported outcomes are not independently verified results or benefits of this proposed product. Published company revenue is separate from category software opportunity.
Detailed reports and models
Full supporting material
Market opportunity
Country stock, eligibility and price assumptions, regional scenarios, launch scope and sales capacity.
Open market reportEditable market workbookCountry CSVMarket sourcesCompetitive landscape
Named alternatives, capability evidence, customer deployments and the limits of reported outcomes.
Open competition reportFull landscape modelCustomer evidence CSVLandscape sourcesThe source reports are preserved copies. Their original draft labels and typography remain unchanged. The two portable landscape links retain the transformation already recorded for the reviewed bundle. External citations require internet. Local pitch and reference files work after extracting the complete bundle.