Ride-hailing launches fail publicly in ways no other software launch does. This is the 30-item checklist Waslni works through for every tenant in the final week before public launch.
A ride-hailing launch fails publicly in ways no other software launch fails. A broken mobile-app build is visible to every rider in the city. A misconfigured payment gateway charges hundreds of customers double. A driver-document workflow gap blocks 90% of your fleet on day one. A regulator finds out about your operation through the Instagram launch announcement before you have filed the licence.
This checklist is the 30 items Waslni verifies for every tenant before they go public. It is organised in eight groups — apps, payments, drivers, regulators, operations, marketing, support, contingency. We work through it as the final step of the four-week launch playbook.
Print it. Hand it to your operations lead. Tick every item. The 7-day soft launch in your strongest city catches the last 5% that no checklist anticipates.
Each group covers one operational dimension; each item is verified before public launch.
iOS build approved by Apple. Android build approved by Google. App listing has correct screenshots, description in your launch language, privacy policy URL working. Deep links work from SMS and email. Push notifications tested end-to-end. Crash reporting wired (Sentry or similar).
Every payment method tested with a real card or wallet: card via primary gateway, card via fallback gateway, mobile wallet (Apple Pay / Google Pay / regional equivalents), cash workflow, refund flow, failed-payment retry. Settlement runs configured. VAT-ready receipts confirmed.
Minimum 50 drivers onboarded, documents approved, vehicles inspected, training session complete. Driver-app accounts active. Driver-acquisition pipeline in place for weeks 1-4 post-launch. Driver-support channel (WhatsApp group, hotline) live.
Transport-authority licensing complete. Commercial registration current. Data-residency confirmed. AML/KYC workflow validated. Insurance policies in force for drivers and operations. Privacy policy and terms of service published in all launch languages.
Service types defined with fare formulas. Peak windows set for the launch city. City geofences finalised. Surge / dynamic-pricing policy in place. Operator console accounts created for dispatcher and finance roles. Audit log enabled.
Launch announcement scheduled. First-rider incentive (free credit, promo code) configured. Referral codes generated for early adopters. App-store ASO done. Social channels live. PR pipeline (if applicable) primed.
Customer-service team trained on common rider issues. Operator console permissions configured for support staff. Refund-issuance permission limits set. Driver-support hotline live. WhatsApp Business number active.
Outage plan for backend incidents. Customer-comms templates for known failure modes (payment outage, gateway downtime, driver-supply shortage). Public-launch press incident plan (in case of a viral negative review).
Yes. Even on Waslni's battle-tested platform, every tenant's combination of brand assets, payment-gateway configuration, driver pool, and regulatory environment produces some unique edge cases. A 7-day soft launch in your strongest city catches them before they go public.
Payment-failure customer-comms template. Almost every operator handles the happy path and forgets the failure messaging. When a gateway has an hour-long outage in week three, the support inbox explodes. Pre-write the apologetic-but-firm template; have it approved by legal; deploy it the moment an outage begins.
Day one of your four-week launch playbook. Each item maps to a specific week: items 1-10 are platform setup (week 1-2), items 11-20 are operations (week 2-3), items 21-30 are pre-launch verification (week 3-4). Treating the checklist as a "week four problem" causes preventable slippage.
Yes. Every Waslni tenant has a designated launch lead from our team who works through the checklist with your operations lead in the final week. We have done the four-week playbook enough times that the common mistakes show up early.
14 days free demo, plus a designated launch lead on the four-week playbook. No card required.