Leisure Land Digital Platform
A web and mobile-responsive platform covering the full guest lifecycle — from discovery and booking through payments, day-pass ticketing, room & dining management, loyalty, and a fully centralized operations system. Built to carry the brand from upper-middle to high-class.
Prepared by fern. — planning, design, implementation & operational execution
Executive Summary
A single-glance view of the program: scope, scale, priorities and the operational posture across two delivery phases and eleven product modules.
The thesis. Leisure Land currently sells a premium nature-adventure experience through a non-premium channel — a WhatsApp number. This document specifies the platform that replaces it: Phase 1 ships a fast website with real online booking and three payment gateways (Koko, PayHere, Stripe); Phase 2 folds every operation — rooms, food, inventory, staff, finance and loyalty — into one centralized system with a single source of truth.
Introduction & Business Objectives
Leisure Land is a nature-adventure destination in Galle — water slides, outdoor activities, riverside food and cabins. As construction completes and the brand repositions toward a high-class audience, six objectives frame every requirement in this document.
1. Speed & first impression
Rebuild the site for sub-second loads and strong SEO — the digital front door of a premium brand.
2. Frictionless payment
Take money online instantly via the right gateway for each guest and product.
3. Eliminate manual booking
Retire WhatsApp as a booking desk; make it a notification channel instead.
4. Own the guest data
Capture every guest into a CRM to enable loyalty, remarketing and upsell.
5. Centralize operations
One system for bookings, rooms, F&B, inventory, staff and finance.
6. Move upmarket
Membership tiers, concierge and premium UX to attract a high-class clientele.
Stakeholders & User Personas
Internal stakeholder groups who operate the platform, and the guest personas it must delight.
Internal stakeholders
Ownership
Wants revenue, occupancy and brand-position visibility in real time.
Front desk
Manages bookings, check-ins and guest queries from one screen.
F&B / kitchen
Receives orders, manages menu and stock without paper.
Operations & housekeeping
Room status, activity slots and on-site staffing.
Guest personas
Local family day-tripper
Books day passes for the slides. Price-sensitive → loves Koko instalments & PayHere. Sinhala/English.
International tourist
Books a cabin + activities online before arriving. Pays via Stripe, expects multi-currency & English UX.
Premium couple / event
Wants curated packages, dining and concierge. The high-class segment the brand targets next.
Corporate / group organizer
Books in bulk for outings and team events; needs invoices and group rates.
Gifter
Buys gift cards & vouchers for friends and family.
Returning member
Loyalty-tier guest who books repeatedly and earns perks.
System Diagrams
Fifteen interactive views of the same platform — each diagram exposes a different angle on the architecture, flow, hierarchy, data or constraints.
🏗️ Platform Architecture
A layered, modular architecture. Phase 1 ships the booking & payment slice; Phase 2 adds the centralized modules — but every block is independent and API-driven from day one.
Layered architecture (Phase 1 → Phase 2)
🔄 Booking Workflow
The happy path from intent to ticket — fully automated, money settled before arrival.
End-to-end booking flow
⏱️ Payment Sequence
Message-level detail of a successful payment across the system actors.
Sequence — guest pays for a day pass
🏊 Swimlane Process
The same booking process, organized by who is responsible at each step.
Swimlanes — responsibility across actors
🔁 Booking State Machine
Every booking moves through a strict set of states — the system, not a person, enforces the transitions.
States & transitions of a booking
🗄️ Data Model (ERD)
The core entities and how they relate — the foundation of the single source of truth in Phase 2.
Entity-relationship diagram
🧠 Module Mind Map
Everything the platform contains, radiating from the core — a quick mental model of scope.
Capability mind map
🌳 Tree Decomposition
The system broken down hierarchically — useful for scoping and estimation.
Work breakdown structure
🔗 Dependency DAG
What must be built before what — the critical path through the program.
Build dependency graph
🕸️ Integration Network
The platform sits at the centre of a network of third-party services. (Full per-integration diagrams further down.)
Integration network graph
📆 Timeline / Gantt
When each workstream runs across the two phases (indicative).
Delivery Gantt
🏅 Membership Tiers
A loyalty ladder built for the move upmarket — turns day-trippers into repeat premium guests.
Tier comparison
Free
- Online booking
- Digital tickets
- 1× points
3 visits / yr
- 5% off passes
- Priority slots
- 1.5× points
8 visits / yr
- 12% off + dining perks
- Free cabin upgrade*
- 2× points
Invite / spend
- Concierge & events
- Private dining
- 3× points + gifts
📊 Distribution Charts
Projected mix of payments and bookings — to size gateway fees and capacity.
Revenue by gateway (projected)
Bookings by product type
🔻 Conversion Funnel
Where visitors drop off and where the platform must perform — the metric the redesign is judged on.
Visitor → confirmed booking funnel
🗂️ Delivery Kanban
A snapshot of how delivery is tracked — illustrative board for the Phase 1 sprint.
Sprint board
Backlog 4
To do 3
In progress 3
Done 3
Interactive Booking Demo
A working prototype of the Phase 1 guest experience. Pick items, choose a gateway, get a confirmation — no real charges, sample data only.
All slides + activities
4 passes + lunch
Sleeps 2 · breakfast
Set menu · evening
Feature Modules
Eleven modules make up the platform. Each is tagged with the phase it ships in. Phase 1 modules form the revenue engine; Phase 2 modules centralize operations.
Booking Engine
Real-time availability and reservations for day passes, cabins and timed activity slots, with holds and rules.
Payments
One checkout, smart-routed across Koko, PayHere and Stripe, with webhooks, refunds and reconciliation.
Notifications
Automated WhatsApp & email confirmations, QR tickets, reminders and review requests.
CRM & Loyalty
Every guest captured into a profile; loyalty tiers, points and gift cards layered on top.
Property Mgmt (PMS)
Room inventory, rates, housekeeping status and check-in/out from the front desk.
F&B / POS + KDS
Menu, table & tab management, and a kitchen display system for the restaurant.
Inventory
Stock for F&B and retail, low-stock alerts and supplier tracking.
Staff / HR
Rostering, shifts, attendance and payroll inputs tied to operations.
Finance
Invoicing, tax, daily revenue reconciliation across all channels.
Marketing Automation
Win-back, birthday and seasonal campaigns triggered from CRM data.
BI & Analytics
Owner dashboard: revenue, occupancy, popular activities and staff KPIs in real time.
Premium add-ons
QR wristbands, dynamic pricing, AI concierge, digital waivers, OTA channel manager — see roadmap.
Integration Map
Nine third-party services across four categories. Each one is wired through the platform's integration layer, never directly into the front-end — so any provider can be swapped without a rebuild.
| Integration | Category | Direction | Phase | Purpose |
|---|---|---|---|---|
| 🟣 Koko | Payments | Out → callback | P1 | BNPL instalments for day passes |
| 🇱🇰 PayHere | Payments | Out → callback | P1 | Local cards & wallets (LKR) |
| 🌍 Stripe | Payments | Out → webhook | P1 | International cards & Apple/Google Pay |
| 💬 WhatsApp Business | Messaging | Out | P1 | Tickets, confirmations, reminders |
| 📲 Twilio | Messaging | Out | P1 | SMS / OTP fallback |
| ✉️ SendGrid | Messaging | Out | P1 | Transactional & marketing email |
| 🏝️ Booking.com / Airbnb / Agoda | Distribution | Two-way sync | P2 | Channel manager for cabins |
| 📊 GA4 + Metabase | Analytics | In | P1 | Web analytics & BI dashboards |
| 🗺️ Google Maps / Reviews | Ops | Two-way | P1 | Location, directions & reputation |
💳 Payments — Koko · PayHere · Stripe
Three gateways behind a single Payment Service. The service chooses the rails based on product type and guest location, then listens for the callback/webhook before confirming the booking.
Payment routing & settlement
Koko
- BNPL, interest-free splits
- Lifts AOV on bundles
- LL paid upfront, Koko carries risk
PayHere
- Visa/Master/Amex in LKR
- eZ Cash & local wallets
- Low domestic fees
Stripe
- Global cards + wallets
- Multi-currency display
- Strong fraud tooling
💬 Messaging — WhatsApp · Twilio · SendGrid
WhatsApp flips from a booking desk to an automated notification channel. Events in the platform fan out to the right messaging provider.
Event-driven notifications
🏝️ Distribution — OTA Channel Manager Phase 2
Cabins are sold not just on the website but across online travel agencies. A channel manager keeps one calendar in sync so a room can never be double-sold.
Two-way OTA sync
📊 Analytics & Ops — GA4 · Metabase · Maps · Reviews
Behavioural and operational data flows into analytics; location and reputation services flow both ways.
Insight & reputation loop
Phased Rollout
Each phase is independently shippable — Phase 1 delivers visible revenue wins fast; Phase 2 builds the long-term platform on top without throwing any of it away.
Foundation — site, booking & payments
| W1–2 | Discovery, brand, content model, gateway accounts |
| W3–5 | Site rebuild, booking engine, 3 gateways, notifications |
| W6 | QA, security review, staff training |
| W7–8 | Launch, monitor, optimize conversion |
Acceptance: a guest can book & pay online end-to-end; WhatsApp manual bookings → 0.
Centralization — one system
| W1–3 | Core platform, data model, roles, dashboard shell |
| W4–8 | PMS, POS/KDS, CRM, inventory on shared data |
| W9–11 | Loyalty, channel manager, BI, marketing automation |
| W12–14 | Migrate Phase 1, full QA, staff onboarding, cut over |
Acceptance: all operations run from one dashboard with a single source of truth.
Hosting Evolution
Infrastructure grows with the product — start lean and cheap, scale only when traffic and modules demand it.
Phase-by-phase infrastructure
Non-Functional Requirements
The constraints that govern how the product performs, not just what it does.
Performance
<1s LCP on 4G, Core Web Vitals green, image optimization, CDN edge caching.
Security
PCI-DSS via gateways (no raw card data stored), encryption at rest & in transit, RBAC, audit logs.
Accessibility
WCAG 2.1 AA, keyboard navigable, semantic markup, sufficient contrast.
Scalability
Stateless services, horizontal scaling, queue-backed jobs for peak weekends.
Devices
Mobile-first responsive, installable PWA, tested across iOS/Android & desktop.
Reliability
99.9% uptime target, daily backups, monitoring & alerting, graceful degradation.
Admin & CMS Requirements
So Leisure Land staff can run the platform day-to-day without engineering involvement.
- Manage products, prices, packages & promo codes
- Open/close activity slots and set capacity
- Edit website content, pages, banners & gallery
- View, search, refund & modify bookings
- Manage rooms, rates & availability (Phase 2)
- Menu & inventory management (Phase 2)
- Staff accounts & role-based permissions
- Export reports (CSV / PDF) & view dashboards
- Configure notification templates
- Manage loyalty tiers & gift cards
Success Metrics & KPIs
The numbers the platform is measured against once shipped.
Next steps. On sign-off, Fern kicks off Phase 1 discovery: brand & content workshop, gateway account setup (Koko, PayHere, Stripe), and a clickable design prototype within two weeks. This document is a living artefact — it updates as the build progresses.