What we need for an efficient Launch
Week-1 items vs later. Missing credentials slow the build.
Need in week 1 Unblocks build
- API sandbox credentials: wire flight + hotel against your travel/hotel API sandbox. Usually: client / account owner.
- Markup rules (draft OK): fare / hotel markup model for production. Usually: commercial owner.
- Wallet + refund policy (draft): wallet flows and refund paths. Usually: ops / finance.
- Admin user list (names + roles): who can see what in admin. Usually: ops lead.
- Brand assets: logo SVG/PNG, colours, fonts if fixed. Usually: marketing.
- Sample itineraries / search OD pairs: UAT scripts that match real traffic. Usually: ops.
- Legal entity name for invoices: proposal + invoice header. Usually: finance.
- GSTIN: tax-compliant invoicing (India). Usually: finance.
- Primary contact + escalation: scope questions don’t sit idle. Usually: sponsor.
Before go-live Before UAT / cutover
- API production credentials: cutover after UAT pass with your supplier.
- Domain + DNS access (or change window): point search / booking hosts.
- Payment keys: test first, then live: for checkout / wallet top-up.
- Final markup + wallet rules signed off: freeze before prod.
- UAT acceptor named: who signs “pass”.
- Content / T&Cs links if on your domain: legal pages you own.
Nice later Not week-1 blockers
- White-label domain extras, multi-language copy packs, second supplier IDs, AI inventory-search model choice (Scale), uptime / support SLA beyond Launch keep-alive.