Skip to Content
Trips Enjoy
Delivery Plan

Milestones

The phase ladder from foundation to scale — tasks per phase, definitions of done and the open decisions that gate each phase.

Each phase closes on its definition of done (BRD section 3.3) with every Must task verified against its acceptance criteria. Task counts come from the generated phase pages; re-run bun scripts/generate-plan.ts after requirement changes to refresh them.

The ladder

PhaseTasks (M/S/C)Definition of doneDecisions to close
P1 — Foundation41 (41M / 0S / 0C)An organization can apply, be approved and sign in to an empty workspace.OD-03, OD-12, OD-21, OD-23
P2 — Single-vehicle pilot (Egypt)31 (30M / 1S / 0C)One pilot organization sells one trip to real travelers with real payments.OD-07
P3 — Operational depth40 (37M / 3S / 0C)A three-bus trip with about 120 passengers runs end to end.OD-25
P4 — Marketplace supply33 (32M / 1S / 0C)Organizations book platform suppliers through deals and deliver albums with all privacy modes.OD-13, OD-24
P5 — Monetization and Gulf launch36 (33M / 3S / 0C)Recurring revenue is measurable, limits are enforced, and the Gulf markets are live once OD-10 is decided.OD-28
P6 — Family and scale26 (17M / 5S / 4C)Parents see their children live; organizations get analytics and integrations.—

Reading the ladder

  • A phase gate needs all of its Must tasks green; Should and Could may trail into the next phase without blocking it.
  • The decisions column lists open decisions cited by that phase's requirements — close them before the phase starts, not during.
  • Cross-cutting platform tasks (CI, environments, integrations) sit at the top of each phase page and gate the same milestone.

On this page