Cloud migration
- AWS, Azure or GCP, chosen for the workload
- Cutover planned so the business keeps running
- Cost modelled before anything moves
Scope
Six places we are brought in.
System architecture
- Monolith or services, decided on evidence
- Data model, APIs and failure modes
- A design the next team can extend
Legacy modernisation
- Phased replacement, not a big-bang rewrite
- Risk named before the first migration
- Vendors coordinated against one plan
Vendor selection
- Build, buy or configure, with the trade-off written down
- Shortlist scored against your constraints
- ROI that survives contact with finance
Roadmap and budget
- A 3–5 year sequence, not a slide of logos
- Initiatives ranked by what they unblock
- Spend tied to an outcome
Security posture
- Where the real exposure is
- ISO 27001 and PDPA mapped to actual systems
- Controls a team can operate
Engagement
Three phases. Then you own the plan.
01
Discovery
Two to four weeks. Current systems, the people who actually use them, and the metric that would make this worth doing.
02
Strategy
Three to six weeks. The architecture, the vendor comparison, the sequence, and what it costs.
03
Execution
We hand it to your team, stay as advisor, or manage the vendors. You choose after the plan exists.
Fit
The operations we take on.
Typical brief
- A manufacturer moving off spreadsheets into a real system of record
- A logistics firm whose tracking no longer matches the operation
- An agency planning a digital programme it can actually fund
- A retailer running more than one point of sale
- A clinic or practice reconciling payments, bookings and staff by hand
See the pattern in production: an AI front desk and back office for a TCM clinic.
Related: business automation · fractional CTO · consultancy