Five phases.
No surprises.

THE FIVE PHASES · IN FULL

From map to handover

Two rules govern all five phases. Nothing executes without your sign-off, and every step has a rollback that was tested before it was needed. The result is that the riskiest moment of the project, the switch, is also the most rehearsed.

1. I

   Discovery & Audit

   I map your infrastructure: every system, every data flow, every dependency, what each costs per year, and where GDPR and AI expose you. This phase is pure investigation; nothing in your environment is touched, and most of your involvement is a kickoff conversation and a walkthrough.

   • You see & approvethe findings, before anything is planned on top of them.
   • Rollbacknothing to roll back; nothing was changed.
   • You holda written audit report that stays useful even if we never work together again. Sold on its own for €850, excl. btw, fully credited against a migration signed within 60 days.
2. II

   Architecture & Planning

   The audit findings become a target design and a step-by-step migration runbook: which system moves when, in what order, with what dependencies, and what happens if a step fails. Every step gets its own rollback written before we start, not improvised at midnight. This is also where the proposal lands: a fixed project fee and a fixed monthly price, and neither moves.

   • You see & approvethe design, the runbook, the timeline and the numbers. Nothing executes without your sign-off.
   • Rollbackstill nothing running; declining the proposal is the rollback, and the audit report remains yours.
   • You holdthe runbook itself, written for your team, not for me.
3. III

   Migration Execution

   The new environment is built and filled next to your production, which keeps running untouched. Server hardening, the systems from the design, the wiring between them, backups with tested restores, and monitoring, all constructed and loaded with real data copies while your business notices nothing.

   • You see & approveprogress against the runbook, and working previews you can log into and poke at.
   • Rollbacktrivial by design: production has not been touched. The build can pause or stop at any point with zero operational impact.
   • You holda complete parallel environment, under your accounts, from the first day of the build.
4. IV

   Validation & Cutover

   Full testing against the real workload: your documents open, your workflows run, your team's daily tasks work in the new environment, verified before the switch rather than discovered after it. Then the switch itself, in a window you approve, usually outside business hours, followed by days of close monitoring.

   • You see & approvethe validation results and the switch window. The go/no-go is yours.
   • Rollbackthe tested plan: the old environment is still intact and can be restored to primary in minutes, not rebuilt in days.
   • You holda live environment that has already proven itself, and an old one still standing as the safety net.
5. V

   Handover & Retainer

   Documentation, knowledge transfer, and a trained team: your people learn the new systems from me, not from a PDF alone. The old environment is safely decommissioned only after the new one has earned trust, and its subscriptions are cancelled with receipts. From here, Managed Sovereignty takes over: updates, backups, monitoring and a monthly report, from €150 a month with the exit clause applying every single month.

   • You see & approvethe handover checklist and the decommissioning of the old environment, item by item.
   • Rollbackthe exit clause itself: everything is yours, so you can continue with me, alone, or with anyone else, from the runbook.
   • You holdeverything. Server, accounts, domains, documentation, and a team that knows how to use it. That is the point.