Roadmap
Five phases from decisions and data clean-up to finance, analytics and AI. Each phase delivers something the business can use, lists what it depends on and says what done means.
Durations are estimates to be validated. They assume a small dedicated team and timely decisions by the owners. They are not commitments and carry no calendar dates; phase 0 produces the first real plan.
Timeline
Weeks from project start. Select a bar to jump to the phase.Decide and prepareSellDeliverOptimiseGo-live point
Sequence for the revision 5 Oct 2026 requirements
The ten requirements of the feedback brief, placed in the order the brief suggests. This is a dependency-based recommendation, not an instruction to omit later requirements, and it carries no dates or durations: the new work is not estimated. Reversible layout and workflow work can proceed; the parts that depend on an open decision wait for it.
| # | Step | Requirements | Screens in the prototype | Depends on | Open decisions gating the non-reversible part | Estimate |
|---|
Status of every step today: demonstrated in the prototype with sample data. Nothing here is implemented or verified in production. Evidence per requirement is in the completion matrix; the walk-throughs are on end-to-end scenarios.
Dependencies between phases
| This | Needs first | Why |
|---|---|---|
| Phase 1 public site and checkout | Decisions on front end, currency and payment gateway; clean course data | Pages, prices and checkout cannot be built on undecided foundations |
| Phase 2 certificates | Enrolments and attendance from phase 2 scheduling; ASME rules confirmed in phase 0 | A certificate is issued from an enrolment that met a rule |
| Phase 2 portals | Sign-in and learner records from phase 1 | Portals are views on existing records |
| Phase 3 corporate sales | Batches (phase 2) and orders (phase 1) | A won deal creates a private batch and an order |
| Phase 3 marketing journeys | Enrolment events from phase 1 and 2 | Journeys are triggered by what learners do |
| Phase 4 finance integration | E-invoicing decision; invoices and payments flowing since phase 1 | Books are fed from real transactions |
| Phase 4 AI layer | All modules writing to the hub for some months | Scoring and recommendations need history to read |
| Company P&L | Approved payroll cost (People & HR) and supplier bills (Purchasing & payables), each recorded once | Company profit is batch contribution less overhead; overhead without payroll and payables is incomplete |
| Year-end forecast | Tender award conversion and contracted future revenue kept apart from pipeline and planned programmes | An awarded line must leave the pipeline when it becomes a contracted batch, or its value is counted twice |
| Recovery plan | Risk register and action register with owners, due dates and escalation | A recovery action is an owned action with evidence and a measured effect |
| Accounting integration and statements | Decision DEC-01: internal accounting or a package | Mapping, export and reconciliation are built against the chosen ledger. |
| Payroll calculation | Decision DEC-08: provider, jurisdiction and employment policies | No statutory formula may be invented. |
| Website CMS build or hand-off | Decision DEC-09: WordPress retention and CMS ownership | The editing workflow is either built or handed to WordPress with status shown. |
| Enforced approvals and role scopes | Decision DEC-03 and the central approval policy; one role and scope model | Every module reads the same matrix. In the prototype hiding is static, not authorization. |
What could move the plan
Faster. Keeping WordPress for the public pages, launching with live and in-person only, and one currency all shorten phase 1.
Slower. Unresolved source data, Arabic interface at launch, a full on-demand catalog, or late answers on ASME requirements.
Order can change. If corporate sales is the urgent pain, the CRM part of phase 3 can run beside phase 2. The hub makes phases independent once phase 1 is live.