Project Proposal
Raffles Leisure PVT(LTD)
Destination Web App
Lead Developer: Melshan Perera
Agency: ColorCodeLabs
Project Scope: Phase 1 – Sri Lanka Launch & Multi-Country Infrastructure
1. Project Concept
The Raffles Leisure Web App is a scalable tourism marketplace. It allows travelers to explore destinations, drill down into specific cities, and book activities either with or without a professional guide. While the platform handles standard tours, its core strength is the ability to manage complex, high-demand events with precision.
2. Feature Highlight: Advanced Event Seating
To illustrate the platform’s power, we use the Kandy Esala Perahera as the primary functional example. Unlike a standard tour booking, certain events require a “Cinema-Style” experience:
- Interactive Seat Mapping: When a user selects a major event, they see a visual layout of the venue.
- Tiered Pricing by View: The system automatically assigns different prices to seats based on the quality of the view (e.g., Front Row vs. Elevated Gallery).
- Real-Time Inventory: Just like a cinema website, once a seat is clicked, it is temporarily held to prevent double-booking while the user completes the payment.
- Automated Ticketing: The system generates a digital invoice and entry pass with specific seat numbers immediately after a successful IPG transaction.
3. The Three-Tier Dashboard System
A. Agent Dashboard (B2B)
- Custom Rate Access: Agents log in to a private portal where they see rates based on the commission set by Raffles Leisure.
- Booking Management: A centralized view of all client reservations, event times, and guide assignments.
- Financial Tracking: A clear breakdown of commissions earned and pending payments.
B. Supplier Dashboard (Event Owners)
- Real-Time Manifests: Using the Perahera management as an example, suppliers can log in to see exactly who has booked which seat.
- Reservation Control: Suppliers can monitor their seat inventory and manage cancellations directly.
- Offline Settlement Data: Provides the necessary reports for the Admin to transfer payments to the Supplier offline.
C. Customer Dashboard (B2C)
- User Accounts: Customers create an account during the checkout process.
- Digital Vault: Access to all historical and upcoming booking details, downloadable invoices, and e-tickets.
4. Financial Workflow Summary
- Customer → Admin: Online payment via integrated payment gateway (IPG).
- Agent → Admin: Online payment or offline bank transfer options.
- Admin → Supplier: Offline settlement based on system-generated reports.
- Admin → Agent: Commissions are managed via the backend according to the set percentage.
5. Access Control: Guest User vs. Logged-in Agent
To maximize sales, the platform treats standard travelers and registered travel agents differently. This table outlines the specific permissions and views for each:
| Feature | Guest / Standard Customer | Registered Travel Agent |
| Pricing View | Standard Retail Price (SRP) | Agent-Specific Rate (SRP minus Commission) |
| Booking Method | Immediate Online Payment (IPG) | Credit Limit or Offline/Online Hybrid |
| Seat Selection | Individual seats only | Bulk seat selection for groups |
| Documentation | Standard Digital Invoice | White-labeled Vouchers for their clients |
| Dashboard | Personal Booking History | Full Sales Ledger & Commission Reports |
| Guide Selection | Default rates | Priority Guide Assignment options |
| Event Details | General Event Info & Seat Map | Real-time Seat Availability & Timings |
6. Summary of Workflow & Terms
The “Kandy Esala Perahera” Booking Flow Example
- User Action: Selects “Kandy” —-> “Esala Perahera.”
- Seat Mapping: User picks a specific seat from a visual map (e.g., Front Row, Gallery).
- Pricing: The system calculates the price based on the seat’s view quality.
- Transaction: User pays via IPG; a seat lock is applied to prevent double-booking.
- Confirmation: A digital ticket is sent to the Customer Dashboard, and the booking appears on the Supplier Manifest.
7. Hosting & Infrastructure
For a platform handling real-time seat locks and high-traffic events, reliable hosting is critical.
- Primary Suggestion: VPS (Virtual Private Server) Hosting.
- Cost: Estimated between $150 USD – $200 USD, billed annually.
- Rationale: While AWS or Firebase are powerful, they involve complex usage-based billing. A VPS provides a stable, high-performance environment with a predictable annual budget.
8. Investment & Payment Terms
The total development fee for the Phase 1 launch is 300,000 LKR.
Payment Milestones:
To ensure a structured development cycle, we propose the following terms:
| Milestone | Percentage | Amount |
| Project Kickoff / Advance | 30% | 90,000 LKR |
| Core Feature Delivery | 30% | 90,000 LKR |
| Final Deployment & Handover | 40% | 120,000 LKR |