08 · Delivery
Roadmap
Estimated at 50 working days (excluding weekends and public holidays). Phases are sequential and each is demonstrable on completion. The Status & Ownership Engine is deliberately first — everything else depends on it.
Timeline — 50 working days
| Phase | Focus | Key deliverables | Working days |
|---|---|---|---|
| 0 | Setup & Finalization | Requirement sign-off, environment, DB schema & migrations | 4 |
| 1 | Foundation | Status & Ownership Engine, Auth/RBAC + hierarchy, Lead Mgmt, Opportunity | 13 |
| 2 | Deal Flow | Quotation, Sampling, Tasks & SLA, Escalation, drip engine | 12 |
| 3 | Conversion | Contract, document service, customer conversion | 8 |
| 4 | Operate | Post-Sales ops, Buyer Portal, KPI dashboard | 10 |
| 5 | UAT & Handover | Testing, bug-fixing, deployment, training & handover | 3 |
| Total | 50 | ||
0
Phase 0 — Setup & Finalization 4 days
Lock requirements and stand up the ground.
- Requirement sign-off with the Client Company
- Development / staging environment provisioning
- Database schema & initial EF Core migrations
Exit: requirements are frozen, environments are live, and the data model is migrated.
1
Phase 1 — Foundation 13 days
The tracking backbone + first two stages.
- Data model & migrations (deal, stage entities, status_history, activity_log, user, team)
- Status & Ownership Engine: state machine, transition contract, owner hand-off, audit
- Auth + RBAC + hierarchy (ASP.NET Core Identity, policy-based permissions, EF Core scoping)
- Module 1 (Lead Management) + Module 2 (Opportunity & Pre-Sales)
- Communications Hub + basic per-user work queue
Exit: a lead can be created, enriched, approved, assigned, converted — with status
and owner tracked and logged at each step.
2
Phase 2 — Deal Flow 12 days
Quotation, sampling, and the task/escalation system.
- Module 3 (Quotation) + Module 4 (Sampling)
- Task service + SLA timers
- Escalation chain (individual → manager → top management) + notifications
- Drip campaign engine
Exit: a deal moves quote → sample → decision across teams, with deadlines and
automatic escalation on breach. Mid-project milestone — approx. working day 29.
3
Phase 3 — Conversion 8 days
Close the deal into a customer.
- Module 5 (Vendor Approval & Contract)
- CONTRACT_CONFIRMED converts the deal to Customer
- Document service (store/serve contracts & certificates)
Exit: a client can approve documents and the deal converts to a customer with full
history intact.
4
Phase 4 — Operate 10 days
Post-sales operations and the two reporting surfaces.
- Module 6 (Post-Sales Operations)
- Buyer Portal (tracking, documents, one order number)
- KPI dashboard (funnel, TAT, aging, workload, post-sales metrics) with drip metrics
Exit: an order is fulfilled end-to-end, the client self-serves status & documents,
and leadership sees live KPIs.
5
Phase 5 — UAT & Handover 3 days
Prove it, deploy it, hand it over.
- User acceptance testing & bug-fixing
- Production deployment
- Training & handover of source, database, and documentation
Exit: UAT sign-off, live deployment, and full handover to the Client Company —
triggering the final payment milestone.
Open decisions
Decided: .NET + SQL Server · ASP.NET Core MVC (Razor) + HTMX front-end ·
policy-based RBAC · Email as the committed integration.
Deferred to a later phase: AI enrichment (local model when enabled) ·
SAP integration (see Services & APIs).