How deployment engagement actually unfolds.
Five stages, named architects, written deliverables. The cadence below is what enterprise + public-sector procurement reviewers expect to see on Page 1 of a deployment plan.
- EP.01Week 1
Initial scoping
Solution architect reviews the deployment intake, validates fit, and confirms feasibility against your timeline and sovereignty constraints. Output is a one-page fit memo: in/out of scope, recommended modules, recommended deployment mode, open architectural questions.
Deliverable·Fit memo - EP.02Weeks 2–3
Architecture alignment
Module selection (Identra · Payvera · Transify · Workverge · Civitas · EduPro · Ledgera) mapped against your data, identity, and integration topology. Output is a reference-architecture diagram + interoperability contract per integration boundary.
Deliverable·Reference architecture - EP.03Weeks 3–4
Environment selection
FlyttGo-managed (DM.01), customer-cloud (DM.02), or sovereign datacenter (DM.03). Selected against procurement framework, residency policy, and operational ownership model. Output is a signed environment commitment plus the contracting framework (DPS / G-Cloud / OJEU / national framework).
Deliverable·DM.0X commitment - EP.04Weeks 4–8
Pilot rollout planning
Bounded pilot scope — single city, single agency, or single operator. Success metrics, cutover plan, and operational runbook signed before any code ships. Output is a Pilot SOW with explicit success thresholds and a runbook.
Deliverable·Pilot SOW - EP.05Quarter 2+
National scaling roadmap
Pilot graduates into staged regional or cross-border rollout. Output is the regional rollout plan: onboarding cadence, regulatory checkpoints per jurisdiction, and Ledgera-backed financial reporting alignment for each jurisdiction.
Deliverable·Regional rollout plan
Artefacts shipped per stage.
| Code | Artefact | Owner | Stage |
|---|---|---|---|
| AR.FIT | Fit memo | Solution architect | EP.01 |
| AR.ARC | Reference architecture | Architecture team | EP.02 |
| AR.ENV | Environment commitment | Deployment engineering | EP.03 |
| AR.SOW | Pilot SOW | Deployment + customer | EP.04 |
| AR.ROL | Regional rollout plan | Programme office | EP.05 |
Every artefact is signed before the stage closes — gates are deliverable-based, not calendar-based.