Professional services¶
Six engagement-based offerings. Unlike managed services (which run continuously), these are scoped projects with deliverables.
-
Cloud Migration (Lift-and-Shift)
Wave-planned migration from on-prem or other clouds.
-
Re-platforming and re-architecting toward cloud-native patterns.
-
Map your controls to BB ICT 4.0, ISO 27001, PCI DSS.
-
BIA → RTO/RPO → DR design → runbook → exercise.
-
Bespoke engineering — Terraform modules, integrations, automation.
-
Public and private training tracks, plus certification paths.
How a typical engagement runs¶
gantt
title Typical 12-week professional-services engagement
dateFormat YYYY-MM-DD
axisFormat Wk %V
section Discovery
Workshops & inventory :a1, 2026-06-01, 2w
section Design
Architecture design :a2, after a1, 3w
Sovereignty review :a3, after a1, 1w
section Build
Implementation :a4, after a2, 4w
section Cutover
Pilot wave :a5, after a4, 1w
section Stabilise
Production cutover :a6, after a5, 1w
Hyper-care :a7, after a6, 1w Smaller engagements (e.g., a single DR runbook) take 3–4 weeks; multi-application migrations can run 3–9 months across multiple waves.
Working agreement essentials¶
- Statement of Work with deliverables, acceptance criteria, exit criteria
- Time-and-materials or fixed-fee, your call (fixed-fee suits well-scoped migrations and runbooks; T&M suits open-ended modernization)
- All artefacts (Terraform, runbooks, design docs) belong to you at handover
- Hand-off to internal teams is a contractual deliverable; we do not lock you into ongoing dependence