Client stories
Names and sectors are used with permission. Outcomes describe what happened after the engagement, not marketing guarantees.
We booked the five-day code review two months before a Azure move. The workshop on Wednesday was blunt about our session store—exactly what we needed. Took us another sprint to fix, but cutover stayed on the original date.
— Thabo M., engineering manager, logistics API (Durban)
The roadmap did not pretend we could lift-and-shift everything. Having “leave on-prem until Q3” written down stopped leadership from adding scope every week.
— Aisha P., product owner, agricultural exports portal
Report was thorough; formatting was drier than our internal wiki prefers. We restructured the appendix ourselves, which was fine because the findings table was clear.
— Chris L., tech lead, student bursary platform
Architecture assessment surfaced that our “microservices” still shared a database schema. Painful to hear, cheaper than learning it during failover testing.
— Fatima H., CTO, regional insurer digital team
Case: provincial licensing backlog system
Engagement: Cloud code review plus a two-week migration roadmap.
Constraint: Nightly batch jobs could not slip without breaching SLA letters to municipalities.
Interaction: CloudGrove paired with the on-call engineer during log review and sat in on a change advisory board meeting to hear freeze windows.
Outcome: Team phased read-only services first, moved the batch runner last, and documented rollback steps that were exercised once in staging. No production rollback was needed on cutover weekend.
Case: fintech card-provisioning service
Engagement: Architecture assessment only.
Constraint: PCI scope meant certain components had to remain in a dedicated zone.
Interaction: Half-day on-site in Cape Town with security and engineering; remote follow-up for diagram updates.
Outcome: Client kept the card vault path unchanged, replatformed only the customer-facing API tier, and used our decision log in their vendor RFP.