Three steps from scoping to live deployment.
The same cadence applies across every capability tier. What changes between L.01 and L.06 is the sprint count, the integration depth and the regulator footprint — not the engagement shape.
Three steps from scoping to live deployment.
The same delivery cadence applies across every capability level. What changes between Level 1 and Level 6 is the sprint count, the integration depth and the regulator footprint — not the engagement shape.
- SE.D1Capability scope60 minutes · no obligation
A working session between the recipient's lead and the engineering division. Walks the recipient's programme against the six-level ladder, names the tier, and tests the add-on mix against the regulatory frame.
Output: assigned tier · add-on shortlist · indicative envelope - SE.D2Build scoping1 – 3 weeks · NDA-bound
Formal scoping engagement under NDA. Pins the feature list, integration anchors, deployment substrate, identity boundary and the build-sprint cadence. Output is a written build brief and a fixed-fee or tier-priced order form — both reviewable by the recipient procurement and legal.
Output: written build brief · order form · point pricing - SE.D3Build & deploymentPer level · 5 days – 18 months
Sprint-cadenced build under the agreed delivery schedule. Levels 1–3 ship in days to weeks; levels 4–6 ship in months under steering cadence. Every engagement closes with a written hand-over, optional ongoing operations and a documented audit trail.
Output: live deployment · written hand-over · operations runbook · audit trail
Institutional Systems Engineering · platform@flyttgotech.com · audit log retains every authentication and engagement event