Client stories
Names and logos are withheld unless clients opt in. These accounts reference real engagement types we run from Walmer and remotely.
We hired Core Summit for a module boundary review on our invoicing slice after three failed attempts to “just extract a microservice.” Their map showed we were missing a shared rounding helper in a util package—obvious once highlighted, invisible when we stared at the service folder alone.
— Engineering manager, Cape Town freight billing
The readout was blunt about political landmines: two squads claimed ownership of customer profiles. That hurt in the meeting but saved us from drawing a boundary line that would have stalled in committee for months.
— Director of engineering, Johannesburg membership platform
Workshop facilitation kept our loudest architect from dominating the whiteboard. We left with one diagram everyone signed—not perfect, but usable. Follow-up assessment was smaller than we expected because the workshop surfaced the real disagreement early.
— VP product engineering, Durban insurance quoting
Report arrived on time; appendix diagrams were dense. Junior devs needed a lunch-and-learn to digest them, which we should have scheduled ourselves. Content held up six months later when auditors asked how we justified the split.
— Compliance-minded CTO, remote-first health records
Case note: regional retailer checkout
Constraint: Black Friday freeze in eight weeks; leadership wanted a payment provider swap without touching catalog modules.
Engagement: Two-week architecture assessment with emphasis on payment adapter boundaries and feature flags.
Interaction: Mid-week emerging themes call surfaced that catalog teams were importing payment DTOs for analytics—outside the stated freeze scope but a coupling risk.
Outcome: Recommendation to introduce a read-only checkout summary contract first, defer provider swap until January. Client followed that sequence; freeze held with one minor hotfix unrelated to boundaries.
Case note: merged SaaS backends
Constraint: Two products shared a repo after acquisition; duplicate notification stacks caused double emails in production.
Engagement: Module boundary review on notification paths plus a half-day workshop with squad leads.
Outcome: Boundary memo proposed a single outbound events module with namespaced topics. Teams estimated six sprints; actual delivery took eight, but duplicate sends stopped after sprint three when the shared module shipped behind a flag.