Roadmap
MelonQ & BookDirect delivery — Oct 2026 to Mar 2027. Published PM plan (not a /next draft). How-to-build winners stay on v1 playbooks until a row is promoted. Amenities stay the local slug catalog.
Oct 13, 2026
Summary
This is the dev team's delivery plan for MelonQ and Bookdirect from 13 October 2026 to 31 March 2027, with the feature waves that follow. It shows what we are building, in what order, by when, and what each piece depends on. Releases 1 and 2 are planned for acceptance by 18 December 2026. Release 3 builds the late modules in January and February, before Staylier launches.
Use this roadmap to plan sprints, replace the planning sizes with your own, and see which dates are fixed. It orders the work so shared foundations ship first, compares demand with capacity, and sets the checkpoints and cut order we use when work runs behind. The anchor dates:
- 13 to 31 October: Release 1 merges the migration and the v1 foundations. Pending, then live, properties move this week; cutover is 30 October.
- 2 to 27 November: Release 2 builds the revenue and guest-facing modules, code complete on the team's 27 November feature line.
- 1 to 18 December: stabilization with no new scope, then full acceptance on 18 December.
- 21 December to 1 January: change freeze.
- 4 January to 26 February: Release 3 builds the late modules (Group, Insight, Loyalty and Members, Channel Management and Channel Plus, Events, the Room, Experience and Spa calendars, Hotel Marketing and the AI Website builder).
- 3 March 2027: Staylier launches, built during February.
- January to 30 March 2027: extra mobile engineers join in January and launch both mobile apps on 30 March.
- 4 March onward: rebranding, then the industry-standard feature waves to 19 November.
Three rules set the order. Protect live revenue first. Build shared foundations (orders and cart, billing) before the modules that sit on them. Make one risky change at a time: Google Hotel Center changes stay out of cutover week.
Scope notes and decisions
These scope notes and decisions were agreed on 13 October 2026 and apply to every section below.
Scope notes
- The Staylier launch date is 3 March 2027.
- Staylier is corporate business travel management for companies: company accounts, travel policies, approvals, traveller profiles, consolidated invoicing and reporting.
- The team's dates (30 October cutover, 27 November feature line, 18 December acceptance) are fixed and carried over.
- "Migrate live properties" this week means moving the property data into the rebuilt system (pending properties first, then live ones) and reconciling the counts. Production traffic switches at the gated go/no-go on 29 and 30 October. Traffic does not switch before the gate.
Decisions made (13 October)
- The 27 November feature line holds for the Release 2 modules. The Release 3 modules are built late, in January and February, before the Staylier launch. The mobile apps follow their own plan.
- The CTO is the migration decision owner, with the founder as escalation.
- The Google Hotel Center landing page for GT integration moves to secure.bookdirect.ng immediately, for direct booking. BK1 integration landing page is bookdirect.ng.
- The 21 December to 1 January change freeze is confirmed.
Timeline at a glance
Releases 1 and 2 finish by 18 December. After the freeze, Release 3 and the Staylier build run to the launch on 3 March, with rebranding and four feature waves after.
roadmap dates as set in this doc · 13 Oct 2026 to 31 Mar 2027
The diamonds mark the three gates. The mobile apps run on their own track, with extra engineers from January and a launch on 30 March. Staylier starts on 1 February, after Billing (18 December) and Group and Insight (29 January) are accepted.
| Checkpoint | Date | The test | If behind |
|---|---|---|---|
| 1. First week | Fri 23 Oct | Pending and live data migrated and reconciled; repo separation and orders and cart done | Re-plan Release 1 and protect the cutover |
| 2. Go/no-go | Thu 29 Oct | Every migration-critical item verified | Move non-critical Release 1 items to November; never delay the cutover for them |
| 3. Midpoint | Fri 13 Nov | First Release 2 modules accepted by the business; Google Hotel Center verified | Start the cut order in the risk table; move work to Release 3 |
| 4. Feature line | Fri 27 Nov | Every Release 2 module code complete | Apply the cut order in the risk table |
| 5. Release 3 line | Fri 19 Feb | Every Release 3 module code complete; Group and Insight already accepted | Apply the cut order; protect Staylier |
Release 1: Migration and v1 foundations (13 to 31 October)
Release 1 merges the migration with the v1 foundations in one window: pending, then live, properties move into the rebuilt system this week, repo separation runs alongside, and the gated cutover is 30 October.
| Dates | Work | Gate |
|---|---|---|
| 13 to 16 Oct | Import pending properties into the rebuilt system, then migrate live property data the same week and reconcile the counts. Start moving the GT Google Hotel Center landing page to secure.bookdirect.ng for direct booking. Start repo separation and stand up platform.melonq.com. Run the migration audit. Start orders and cart hardening. | 16 Oct: parity matrix, prioritized backlog and cutover plan. Source and target counts match. |
| 19 to 23 Oct | Finish the landing page move (price checks before and after), repo separation and orders and cart. Build the Reservation Portal, the Bookdirect Booking Engine, the MelonQ Booking Engine (standalone, booking link, deep embed), and the new platform UI shell and core screens. | 23 Oct: no critical workflow without an implementation and verification plan. Checkpoint 1. |
| 26 to 30 Oct | Rehearse the cutover, run regression, hold the go/no-go on 29 Oct and cut over on 30 Oct. The cutover includes switching partners from bookdirect.ng/extranet to platform.melonq.com, with redirects. | 29 Oct go/no-go. 30 Oct smoke tests. Checkpoint 2. |
| 31 Oct | Contingency: stabilize, reconcile data, confirm booking and email. | Escalate to the founder if a blocker remains. |
Only migration-critical items gate the cutover: anything else not finished by 29 October moves to early November. Google Hotel Center changes stay out of cutover week.
The old system stays available for rollback until the responsible stakeholders approve its retirement. Do not force the cutover to hit the date if data integrity, booking correctness or rollback readiness is uncertain.
Release 2: Revenue and growth (2 to 27 November)
Release 2 builds the revenue and guest-facing modules and ends at the team's 27 November feature line.
| Window | Work | Exit |
|---|---|---|
| 2 to 13 Nov | Add BK1 integration to Google Hotel Center, with before and after price checks. Coupons and Promos. Start Upsells and Retail, AI Rate Match, the MelonQ website, Billing and Reconciliation and Guest Communication. | 13 Nov: Google feeds verified, Coupons accepted. Checkpoint 3. |
| 16 to 27 Nov | Finish Upsells, AI Rate Match (manual) and the website (20 Nov). Build AI Rate Match (automatic). Finish Billing and Reconciliation, Guest Communication, Guest Dashboard, the Business Development portal with CRM integration, Membership plan subscription and the new Bookdirect.ng UI. | 27 Nov: every Release 2 module code complete. Checkpoint 4. |
Billing and Reconciliation covers the hotel-facing reconciliation feature and the admin Billing, collection and Reconciliation portal. It collects commissions and subscriptions, so it is built early.
Stabilization and acceptance (1 to 18 December)
December is stabilization and acceptance of Releases 1 and 2 with no new scope, followed by the change freeze.
| Window | Work | Rule |
|---|---|---|
| 1 to 11 Dec | Fix defects, close anything not yet code complete, start the full regression. | No new scope. |
| 14 to 18 Dec | Full-system regression and security testing, UAT, documentation, monitoring, backup and recovery checks for Releases 1 and 2. | 18 Dec: business acceptance and handover, as in the team plan. |
| 21 Dec to 1 Jan | Change freeze. | Hotfixes only; an on-call engineer is named. |
Release 3: late modules (4 January to 26 February)
Release 3 builds the modules scheduled late: Group, Insight, Loyalty and Members, Channel Management, Channel Plus (including BL), Events, the Room, Experience and Spa calendars, Hotel Marketing and the AI Website builder. It runs alongside the Staylier build and finishes before the Staylier launch. Group and Insight come first because Staylier needs them; Loyalty and Members comes first because the mobile apps need it from 15 January.
| Window | Work | Exit |
|---|---|---|
| 4 to 29 Jan | Group, Insight, Loyalty and Members, Channel Management and the AI Website builder. Events from 18 Jan and Hotel Marketing from 25 Jan. | 29 Jan: Group and Insight accepted. |
| 1 to 19 Feb | Finish Channel Management, Events and the AI Website builder (5 Feb). Build the Room calendar, then the Experience and Spa calendars, and Channel Plus including BL. Finish Hotel Marketing. | 19 Feb: every Release 3 module code complete. Checkpoint 5. |
| 22 to 26 Feb | Regression, UAT and fixes for Release 3. Contingency for anything open. | 26 Feb: Release 3 accepted, or on the cut list with a date. |
Each channel goes live only when that channel certifies the connection, so some may land after 26 February.
Staylier launch (3 March 2027)
Staylier launches on 3 March 2027 as a corporate business travel management product on top of the booking engine, with Group, Billing and Insight accepted first; the build must start by 1 February with three engineers.
Proposed first shippable scope (to be confirmed in the Staylier spec):
- Company accounts, traveller profiles and user roles.
- Travel policy rules, such as rate caps and approved properties.
- Booking on behalf of a traveller, with an approval step.
- Multi-traveller bookings, using the Group module.
- Consolidated company invoicing and collection, using the Billing portal.
- Spend and travel reports, using the Insight dashboards.
| Date | Milestone |
|---|---|
| 18 Dec | Billing accepted (Staylier prerequisite) |
| 29 Jan | Group and Insight accepted (Staylier prerequisites) |
| 1 Feb | Staylier build starts |
| 24 Feb | Code complete; UAT with pilot companies begins |
| 1 Mar | Go/no-go for launch |
| 3 Mar | Staylier live |
Signing two or three pilot companies through the Business Development portal before 24 February is part of the launch checklist. Staylier launches with the same regression and security gates as every earlier release.
Mobile apps (January to 30 March 2027)
Extra mobile engineers join in January to build the MelonQ app and the Bookdirect.ng app on one shared codebase, and both launch on 30 March 2027. The core team supplies the stable APIs, the design tokens and the release gates, and does not build the apps, so the 27 November feature line is not affected. The dates below are proposed; the mobile lead confirms them in the first week of January.
| Date | Milestone |
|---|---|
| 15 Jan | Mobile engineers onboarded; app designs, API documentation and design tokens handed over |
| 29 Jan | Both apps run against production APIs |
| 12 Mar | Code complete; device regression and security testing |
| 16 Mar | Both apps submitted to the app stores |
| 30 Mar | MelonQ and Bookdirect.ng apps launch |
Apps are built on the design tokens, so the rebranding token swap on 4 to 12 March reaches them before submission.
Rebranding (4 to 31 March 2027)
Rebranding opens the post-launch period, with a 4-week window starting 4 March; it stays cheap only if every product already draws its colours, type and logos from shared design tokens.
- Scope is open. Decide by 29 January what changes (names, logo, colours, domains) and which products it touches.
- Build rule from Release 2: all new UI uses design tokens, so the rebrand is a token swap plus new assets and not a redesign.
- 4 to 12 Mar: swap tokens and assets across the web apps and both mobile apps.
- 15 to 26 Mar: update domains, email templates, app store listings and partner communication.
- 29 to 31 Mar: verify redirects and feeds, then announce.
Any rename that changes a domain used by Google Hotel Center needs a price-accuracy and landing-page check before it goes live.
Industry-standard completion (4 March to 19 November 2027)
From 4 March, four waves build the 22 features the modules above leave out, closing the gaps against what journey.travel and GuestCentric publish; they total 98 engineer-weeks and finish on 19 November 2027.
post-launch plan as set in this doc · 3 Mar to 19 Nov 2027
Rebranding and Wave A overlap in March, so frontend time is shared between them.
| Wave | Feature | What it adds | Size (eng-wks) | Dates |
|---|---|---|---|---|
| A. Convert and collect | Conversion boosters | Live-rate and availability widgets for hotel websites, pop-ups, urgency messages and abandoned-booking recovery. Reference: GuestCentric DateSelect, Availability Scroller and pop-ups. | 4 | 8 Mar to 14 May |
| A. Convert and collect | AI booking assistant | Website chat and WhatsApp assistant that answers questions, recommends rooms and takes bookings. Reference: GuestCentric Melissa. | 5 | 8 Mar to 14 May |
| A. Convert and collect | Personalization | Different room order, offers and member-only rates per shopper, from segments and booking history. Reference: GuestCentric with Duetto PlayMaker. | 4 | 8 Mar to 14 May |
| A. Convert and collect | Vouchers and gift cards | Sell, redeem and track vouchers in the unified cart. Reference: Journey Ecommerce vouchers. | 2 | 8 Mar to 14 May |
| A. Convert and collect | Melon QPayQ | One payments layer over Paystack, Flutterwave, Squad and Tsara: pay-by-link, deposits, pre-authorization, refunds, split settlement and hotel payouts. Reference: Journey Pay. | 6 | 8 Mar to 14 May |
| A. Convert and collect | Security and compliance baseline (added) | Card-data scope reduction through tokenization, data-protection compliance, audit logs, roles and single sign-on. | 4 | 8 Mar to 14 May |
| B. Experience management | Spa management | Treatments, therapists, rooms, packages and online booking on the Spa calendar. Reference: Journey EMS. | 6 | 17 May to 16 Jul |
| B. Experience management | Activities and facilities | Tours, transfers, day passes, sports and golf bookings with live inventory and pricing. Reference: Journey EMS. | 5 | 17 May to 16 Jul |
| B. Experience management | Restaurant tables and Digital Menu | Table booking, menu and pre-orders. | 5 | 17 May to 16 Jul |
| B. Experience management | Fulfilment | Tickets, QR redemption and order fulfilment for retail and experiences. Reference: Journey EMS. | 3 | 17 May to 16 Jul |
| B. Experience management | Paid memberships and day passes | Sell memberships for spa, facilities and clubs, with renewals. Reference: Journey EMS memberships. | 3 | 17 May to 16 Jul |
| B. Experience management | Online check-in and digital registration | Contactless pre-arrival forms, ID capture and arrival time. Reference: GuestCentric mobile access and contactless services. | 3 | 17 May to 16 Jul |
| C. Performance engine | Revenue management | Demand forecasting, dynamic pricing and pace reports, extending AI Rate Match. Reference: GuestCentric revenue and rate management and RMS integrations. | 8 | 19 Jul to 24 Sep |
| C. Performance engine | Competitor rate intelligence (added) | Daily competitor rate shopping that feeds AI Rate Match. | 4 | 19 Jul to 24 Sep |
| C. Performance engine | Advanced analytics and attribution | Funnel, source and cohort analysis across every booking source. | 4 | 19 Jul to 24 Sep |
| C. Performance engine | Multi-property management | One login, shared guests and loyalty, and benchmarking across properties. Reference: GuestCentric Multi-Property Intelligence. | 5 | 19 Jul to 24 Sep |
| C. Performance engine | GEO: AI search visibility | Structured data and content so AI assistants recommend the hotel. Reference: Journey GEO. | 3 | 19 Jul to 24 Sep |
| C. Performance engine | Reputation management (added) | Review requests, aggregation and responses. | 3 | 19 Jul to 24 Sep |
| D. Scale | Public API, webhooks and integration marketplace | Developer access and partner integrations for PMS, RMS and payments. Reference: GuestCentric integrations and API. | 5 | 27 Sep to 19 Nov |
| D. Scale | Wholesaler, OTA and GDS connections | More metasearch channels, bed banks and GDS. Reference: GuestCentric OTA and wholesalers, GDS and metasearch. | 8 | 27 Sep to 19 Nov |
| D. Scale | Multi-language and multicurrency | Booking engine and emails in more languages, prices in the guest's currency. | 4 | 27 Sep to 19 Nov |
| D. Scale | Housekeeping and operations | Room status, tasks and maintenance. Reference: GuestCentric housekeeping management. | 4 | 27 Sep to 19 Nov |
Wave sizes are 25, 25, 27 and 21 engineer-weeks. Each wave ends with the full acceptance gate: full regression, security testing and UAT.
Rows marked "added" are not on either company's public pages; they are included because a revenue engine of this class needs them. Product management confirms each one before its wave starts.
Sources, read 13 October 2026: journey.travel, GuestCentric, Journey EMS overview, GuestCentric on SoftwareFinder, GuestCentric and Duetto.
Master module schedule
Every item has a slot below: 34 rows covering 137 engineer-weeks. Lanes: BE backend, FE frontend, FS full-stack, Mobile (the extra engineers joining in January). Release 2 modules are code complete by 27 November and Release 3 modules by 19 February. Staylier, the mobile apps and rebranding follow.
| # | Module | Size (eng-wks) | Lane | Start | Finish | Depends on | Risk |
|---|---|---|---|---|---|---|---|
| 0 | Migrate live properties (pending first, then live data; gated cutover 30 Oct) | 9, whole team | All | 13 Oct | 31 Oct | Parity matrix | High |
| 1 | Importing pending properties | 1 | FS | 13 Oct | 16 Oct | None | Low |
| 2 | Repo separation and partner platform move to platform.melonq.com (switch at cutover) | 3 | BE, FS | 13 Oct | 30 Oct | None | Medium |
| 3 | Orders and cart hardening (orders, line items, booking sources) | 3 | BE | 13 Oct | 23 Oct | None | High |
| 4 | Stabilization and automated tests | 3 | All, QA | 13 Oct | 18 Dec | None | Medium |
| 5 | Admin: Reservation Portal | 3 | FS | 19 Oct | 30 Oct | 3 | Medium |
| 6 | Bookdirect Booking Engine module | 4 | FS, FE | 19 Oct | 30 Oct | 3 | Medium |
| 7 | MelonQ Booking Engine (standalone, booking link, deep embed) | 4 | BE, FE | 19 Oct | 30 Oct | 3 | High |
| 8 | New UI/UX on the MelonQ platform | 5 | FE | 19 Oct | 30 Oct | Designer phase 1 files | Medium |
| 9 | Front desk calendar: Room | 2 | FE | 1 Feb | 12 Feb | 8 | Low |
| 10 | API integrations: Google Hotel Center (GT, BK1). GT landing page moves to secure.bookdirect.ng now, for direct booking; BK1's landing page is bookdirect.ng; the BK1 connection follows a stable cutover | 3 | BE | 13 Oct | 13 Nov | Stable cutover for BK1 | High |
| 11 | Coupons and Promos | 2 | FS | 2 Nov | 13 Nov | 3 | Low |
| 12 | Upsells and Retail engine | 4 | BE, FE | 2 Nov | 20 Nov | 6, 7 | Medium |
| 13 | AI Rate Match, manual | 3 | FS | 2 Nov | 20 Nov | Rates data | Medium |
| 14 | Group module | 3 | BE | 4 Jan | 15 Jan | 3 | Medium |
| 15 | MelonQ website design and build | 3 | FE | 2 Nov | 20 Nov | Design files | Low |
| 16 | Loyalty and Members | 4 | BE, FE | 4 Jan | 15 Jan | 3 | Medium |
| 17 | Billing, collection and reconciliation (admin portal and hotel reconciliation feature) | 5 | BE | 2 Nov | 27 Nov | 3 | High |
| 18 | Insight and data | 5 | BE, FE | 4 Jan | 22 Jan | Events captured from 30 Oct | Medium |
| 19 | Mobile apps: MelonQ (6) and Bookdirect.ng (4), shared codebase; extra mobile engineers from January, launch 30 Mar 2027 | 10 | Mobile team | Jan | 30 Mar 2027 | 7, 16 | High |
| 20 | AI Website builder | 8 | FS | 4 Jan | 5 Feb | 15 | High |
| 21 | Guest Dashboard | 3 | FE | 9 Nov | 27 Nov | 16 | Low |
| 22 | Admin: Business Development portal with CRM integration | 4 | FS | 9 Nov | 27 Nov | CRM choice | Medium |
| 23 | Channel Management | 8 | BE | 4 Jan | 5 Feb | 3 | High |
| 24 | New UI/UX on Bookdirect.ng | 5 | FE | 9 Nov | 27 Nov | Designer files | Medium |
| 25 | Membership plan subscription | 2 | BE | 16 Nov | 27 Nov | 17 | Medium |
| 26 | AI Rate Match, automatic | 3 | FS | 16 Nov | 27 Nov | 13 | Medium |
| 27 | Events management | 3 | BE, FE | 18 Jan | 5 Feb | 3 | Low |
| 28 | Front desk calendars: Experience and Spa | 3 | FE | 8 Feb | 19 Feb | 9 | Medium |
| 29 | Guest Communication | 4 | BE | 9 Nov | 27 Nov | 3 | Medium |
| 30 | Hotel Marketing | 4 | FS | 25 Jan | 19 Feb | 29 | Medium |
| 31 | Channel Plus integration (includes BL) | 3 | BE | 8 Feb | 19 Feb | 23 | Medium |
| 32 | Staylier (corporate business travel management) | 8 | BE, FE, FS | 1 Feb | 3 Mar | 14, 17, 18 | High |
| 33 | Rebranding | Not sized | FE, brand | 4 Mar | 31 Mar | Staylier live | Low |
Sizes in rows 0 to 32 total 137 engineer-weeks, of which 10 (row 19) are built by the extra mobile engineers. Row 33 is not sized. The post-launch features are in the section above.
Non-engineering tracks
Engineering dates hold only if these inputs land one sprint ahead of the build.
| Role | Owns | Dates |
|---|---|---|
| Product management | Specs with a defined first shippable version for each module. | Release 1 specs this week. Specs for every Release 2 module signed by 23 Oct and for every Release 3 module by 18 Dec. Staylier spec by 18 Dec. |
| Product designer | Design files for each surface. | MelonQ platform, booking engines and admin by 19 Oct (later files slip the UI work, not the cutover). Website by 30 Oct. Mobile app designs by 15 Jan. Bookdirect.ng UI by 6 Nov. |
| Writers and support docs | Cutover runbook, partner notices, help centre, release notes, app store copy, Staylier help. | Partner notice about platform.melonq.com by 23 Oct. Docs for each module within a week of its acceptance. |
| Tester | Migration regression and rehearsal, then automated suites and per-module acceptance tests. | Rehearsal 26 to 27 Oct. Automated core suite by 13 Nov. Full regression 1 to 18 Dec. Release 3 regression 22 to 26 Feb. Staylier regression 22 Feb to 2 Mar. |
| CTO | Migration decision owner, architecture review, release gates, sign-off on estimates. | Estimates reviewed 16 Oct. Orders and cart design review 20 Oct. |
| Founder | Escalation, rebrand scope, Staylier pilot companies, partner communication. | Partner notice approved by 23 Oct. Rebrand scope by 29 Jan. Pilot companies by 24 Feb. |
Critical path and risks
A slip on the critical path is absorbed by the 22 to 26 February contingency week first; after that it moves the Staylier date, or a Release 3 module is cut.
- Cutover stable (31 Oct).
- Orders and cart hardened (23 Oct) and booking engines built (30 Oct).
- Billing code complete (27 Nov); Group and Insight accepted (29 Jan).
- Releases 1 and 2 accepted (18 Dec).
- Staylier built (24 Feb) and launched (3 Mar).
| Risk | Effect | Response |
|---|---|---|
| Team pace below plan | At the planning sizes, work due by 27 Nov is about four times what three engineers supply, and Release 3 about twice. | Checkpoints on 23 Oct, 29 Oct, 13 Nov, 27 Nov and 19 Feb. If behind, cut in this order, protecting the critical path: Channel Plus, Hotel Marketing, Experience and Spa calendars, AI Website builder, Events, AI Rate Match (automatic). |
| Merged scope raises cutover risk | The repo move, data migration and new engines land in the same three weeks. | Only migration-critical items gate the cutover. Rollback covers the domain redirects. Rehearse on 26 to 27 Oct. |
| Cutover slips past 31 Oct | Release 2 starts late. | Never force the cutover. Decide at the 29 Oct go/no-go and move work to Release 3. |
| Google Hotel Center price accuracy or landing page flag | Loss of metasearch traffic. | GT stays live through cutover. The GT landing page moves before cutover week and the BK1 connection follows on 2 to 13 Nov, each with before and after price checks. |
| Orders and cart design is wrong | Rework in Upsells, Coupons, Loyalty, Group, Billing and Staylier. | CTO design review on 20 Oct before any module builds on it. |
| Design files arrive late | UI work idles. | Build on design tokens and the existing screens, and apply new files as they land. |
| Channel certifications and app store reviews | Channels go live after 26 Feb; app store review runs up to the 30 Mar launch. | Submit the apps to the stores by 16 Mar. Treat each channel's go-live as separate from code complete. |
| December freeze | Production issues have no fast path. | Name an on-call engineer for 21 Dec to 1 Jan. Hotfixes only. |
Release gates
A module is done when it meets its first shippable version, has automated tests, has written help documentation, is monitored in production and is accepted by the business. Each release also passes a gate.
| Gate | Date | Must be true |
|---|---|---|
| Release 1 go/no-go | 29 Oct | Essential workflows pass end-to-end tests. Pending and live data reconciled. Backup and restore tested. Authentication, authorization and property-level access checked. Integrations and production configuration verified. platform.melonq.com serves the migrated data and the rollback covers the redirects. Cutover and rollback rehearsed with owners. A named decision owner approves. |
| Release 2 code complete | 27 Nov | Every Release 2 module code complete. Google Hotel Center verified for price accuracy and landing page. Billing totals reconcile against sample hotel data. |
| Full acceptance | 18 Dec | Full regression and security tests pass. Edge cases, integrations and failure recovery tested. UAT complete with no release-blocking defects. Documentation, monitoring, backup and recovery verified. Any exception approved in writing. |
| Release 3 acceptance | 26 Feb | Every Release 3 module accepted, or on the cut list with a date. Certification status recorded for each channel. |
| Staylier go/no-go | 1 Mar | Full regression and security tests pass. Pilot companies complete UAT. Company invoicing tested end to end. Rollback tested. Support documentation ready. |
| Rebrand complete | 31 Mar | Redirects, feeds and app listings verified under the new brand. |
| Mobile launch | 30 Mar | Both apps approved by the stores. Device regression and security tests pass. Apps use the design tokens. Release monitoring is in place. |