Founder-led onboarding
Direct support configuring the business, knowledge and initial customer journeys.
Leora Launch Partners
Help shape the future of hospitality intelligence.
Leora is inviting a small group of hospitality businesses to use the platform in real operating environments, work directly with the founding team and help shape the product before wider release.
Applications are assessed for fit. Applying does not guarantee acceptance.
Who it is for
A practical fit for hospitality teams ready to participate.
Independent restaurantsRestaurant groupsBars and loungesCafés and coffee shopsTakeawaysHospitality operators with multiple locations
Strong-fit indicators
- The business receives regular guest enquiries
- The team wants to improve WhatsApp or digital guest communication
- Business knowledge is currently spread across staff, documents or systems
- The business is willing to test structured customer journeys
- A decision-maker can participate in feedback sessions
- The business can provide accurate menus, policies and operational information
These indicators guide the fit assessment. They do not mean every applicant will be accepted.
Partner experience
What launch partners may receive.
Business Knowledge setup
Support structuring menus, FAQs, services, policies and venue information.
Controlled product access
Access to selected live and beta capabilities suitable for the partner’s use case.
Priority feedback channel
A structured route for reporting issues, requesting improvements and sharing operational feedback.
Early product influence
Partner feedback may help shape workflows, integrations and hospitality-specific features.
Launch-stage commercial terms
Selected partners may receive tailored launch-stage pricing based on scope, onboarding requirements and participation.
Launch-stage terms are scoped individually and do not promise a permanent discount.
A two-way partnership
What Leora may ask partners to provide.
Expectations are agreed as part of the pilot scope, not assumed from an application.
- Accurate business information
- Access to relevant operational stakeholders
- Product feedback
- Regular progress check-ins
- Permission to measure agreed outcomes
- Permission to develop a case study only through separate written approval
Participation does not automatically grant Leora permission to use the business name, logo, testimonial, customer information or results publicly.
Pilot journey
From fit assessment to a separate case-study decision.
- 01
Fit assessment
Understand the business, current systems and operational goals.
- 02
Knowledge setup
Configure menus, FAQs, policies and approved business information.
- 03
Experience design
Select customer journeys, WhatsApp use cases, website experiences or staff workflows.
- 04
Controlled launch
Release agreed capabilities to a limited real-world audience.
- 05
Measure and improve
Review conversations, staff handoffs, customer activity and operational feedback.
- 06
Case-study decision
Agree separately whether any results, quotes, logos or business identity may be published.
Possible pilot use cases
Choose a useful, bounded operating challenge.
Availability depends on the product and external conditions agreed for each pilot.
- Guest FAQs
- Menu discovery
- Structured recommendations
- Allergy-aware staff handoff
- Website assistant
- QR guest journey
- WhatsApp enquiries
- Human takeover
- Review-request journeys
- Returning-customer context
- Campaign preparation
- Multi-site knowledge management
Availability depends on
- Product status
- Business configuration
- Provider access
- Meta approval
- Consent requirements
- Agreed pilot scope
Measurement
Agree what useful evidence looks like.
Each pilot should agree its own measurements before launch. These are possible pilot measures, not guaranteed outcomes.
- Enquiries answered
- Questions requiring staff escalation
- Response time
- Guest journey completion
- Review requests displayed
- Staff time saved
- Returning-customer engagement
- Campaign delivery and response
- Offer redemption
- Knowledge gaps identified
Product status and limitations
Access follows current capability, not aspiration.
Available platform foundations
- Business Knowledge
- Evidence-based responses
- Customer context foundations
- Human approval controls
- Website guest experiences
- Operational dashboards
- Audit foundations
Controlled beta or launch-stage capabilities
- Real customer operations
- Automations
- Campaign workflows
- Review journeys
- Selected integrations
- Multi-site workflows
Externally dependent
- Meta Business Verification
- WhatsApp messaging access
- Message-template approval
- Provider APIs
- Booking, EPOS and CRM compatibility
Some capabilities may remain unavailable during a pilot if external approval or provider access has not been completed.
Trust and data handling
Real-world testing keeps real boundaries.
Pilot participation does not weaken customer consent, safety limits, business isolation or publication permissions.
Explore Data and Trust- Business-specific data boundaries
- Consent-aware customer information
- Restricted handling of sensitive information
- Human verification for safety-critical situations
- No automatic cross-business customer sharing
- No public case study without written permission
- No guaranteed allergen safety
- No silent order placement
- No automatic review submission
- Pilot scope is agreed before onboarding
- Pricing may vary by venue count, integrations and support required
- Meta or third-party provider charges may apply separately
- Custom implementation may carry additional fees
- Continuing after the pilot requires a separate commercial agreement
- Applying does not create a contract or guarantee acceptance
FAQ
Before you apply.
Who can apply?
Hospitality businesses that match the programme’s operating needs and can participate constructively in a scoped pilot may apply. Fit is assessed individually.
Does applying guarantee acceptance?
No. An application begins a fit assessment; it does not guarantee selection, product access or a commercial agreement.
Is the launch-partner programme free?
Not necessarily. Commercial terms depend on the agreed scope, venue count, onboarding, integrations and support requirements. Any charges are agreed before onboarding.
How long does a pilot last?
The duration depends on the use case, readiness, provider access and agreed measurement plan. Timing is defined during scoping rather than promised in advance.
Do I need WhatsApp?
No. A pilot can focus on website, knowledge or operational experiences. WhatsApp use additionally depends on Meta access, verification and configuration.
Can Leora use our logo or results publicly?
Only with separate written permission. Participation alone does not permit Leora to publish your name, logo, testimonial, customer information or results.
What happens after the pilot?
The parties review the pilot and decide separately whether to continue. Ongoing use requires a separate commercial agreement.
Can a multi-site hospitality group apply?
Yes. Multi-site operators can apply, but scope and capability availability depend on the locations, workflows, integrations and launch-stage product status involved.
Build the next stage of Leora with us.
Tell us about your business, the systems you currently use and the guest or operational challenge you want to improve.