The 8-month plan

Goal: go-live at M+8 — four months ahead of your roadmap horizon. Design stays one sprint ahead of development; three tracks advance in parallel, one per engineer.

Delivery plan — 8 months

M+8 · go-live

/0Framing

Mockups OK

/1Foundation

Demo 1

/2Steering & payments

Demo 2

/3Site & media

Demo 3

/4Docs & comms

Demo 4

/5Hardening

Audit reports

/6Launch

Go-live 🚀

Backend / Architecture — Adama

Web / Design — Fatima

Mobile — Massar

Whole team

The seven phases and their acceptance milestones in detail:

Phase	Content	Period	Milestone
0 — Framing	Workshops, mockups, design system, infrastructure	M1	Approved mockups
1 — Foundation	2FA auth, 7 roles, projects, dashboard	M2–M3	Demo 1: you log into ERK+
2 — Steering & transactions	Timeline, budget, finance, quotes, payments	M3–M4	Demo 2: end-to-end financial journey
3 — Site & media	Site journal, materials, photos, videos, live camera	M3–M5	Demo 3: your site, live
4 — Documents & communication	Vault, e-signature, messaging, notifications	M5–M6	Demo 4: a contract signed in the vault
5 — Hardening	Reports, delivery, warranty; load & penetration tests	M6–M7	Audit reports delivered
6 — Launch	Full acceptance, store publication, training	M7–M8	Production 🚀

Why it is realistic. Three full-time engineers, a scope we have already built elsewhere (see our references), and an automated test suite that verifies every requirement on every code change.

Beyond V1

Your roadmap does not stop at launch. The V1 we deliver is the foundation of the next two versions — and we design it accordingly from day one.

Strategic horizon

Project management

0–12 months

ERK+ launch — Senegal & diaspora

Our scope

BTP & Real-estate marketplace

12–24 months

Multi-vendor + property listings

Architecture ready

Finance & AI

24–48 months

Financing, insurance, predictive AI, African expansion

Architecture ready

V1's module boundaries and payment ledger are designed today to host V2/V3 without a rebuild (CDC §2).

V1 is our only contractual scope here. But every module boundary, every line of the payment ledger is drawn knowing what comes next. That is the difference between a V1 you throw away to build V2, and a V1 that V2 rests on.