The people who scope your engagement
are the people in your stand-ups
There is no pyramid here. We are deliberately mid-sized so that a partner-level consultant is close enough to every engagement to answer for the outcome — and so that whoever writes your proposal is still on the project in month six.
We do not publish individual biographies. The people assigned to your engagement are named in your proposal, with their certifications and relevant experience — shared with you directly, rather than posted publicly.
That is a deliberate choice. Public consultant profiles mostly serve recruiters, and the useful version of that information is engagement-specific: who is actually available for your timeline, with experience that actually matches your problem. You get that in writing before you commit, and you meet them before the engagement starts.
The relevant question is not who is on our website. It is who will be in your stand-up on the second Tuesday of month four.
Four practices and a delivery office
Each practice owns its standards, its quality review and its certification pathway. The delivery office owns estimates, schedules and the named lead on every engagement.
Cloud Practice
Landing zones, migration architecture and FinOps. Owns the control-to-code approach that underpins our CPS 234 and Essential Eight work, and the standards every migration wave plan is reviewed against.
- Led by an AWS Solutions Architect – Professional
- Architecture review required before any wave plan is issued
AI & Data Practice
Generative AI, machine learning and data platforms. Owns our evaluation methodology, the responsible AI framework and the stage gates that make stopping an initiative cheap.
- Led by a machine learning engineer, not a strategist
- No AI system ships without an evaluation harness
Security Practice
Posture assessment, detection engineering and evidence automation. Holds a standing veto on any design that would take a client backwards on their control baseline.
- Led by an AWS Security – Specialty holder
- Security review is a gate, not a comment
Managed Services
The run function: SLOs, incident response, transition onboarding and the quarterly improvement backlog. Accepts the pager only after a shadow period, never on a handover document.
- Six-week structured onboarding before service commencement
- Monthly reporting written for leadership, not exported from a tool
The Delivery Office
Estimates, wave plans, steering committees and the schedule nobody else wants to own. Every engagement is assigned one named delivery lead who is accountable to your program office for the whole of it — not a rotating account manager. The delivery office also writes the post-engagement review: what we promised, what we delivered, and what we got wrong.
- One accountable lead per engagement
- Fortnightly steering committee, weekly delivery stand-up
- Written post-engagement review, shared with the client
The named people are the assigned people
The oldest complaint about consulting is that the people in the pitch are not the people on the project. Our answer is procedural rather than aspirational.
Ask who would run your engagementProposals name individuals
Not roles, not "a senior architect". Named people, with their certifications and the comparable engagements they have worked on — provided to you directly.
Availability is confirmed first
If someone is not genuinely free for your timeline, they are not in your proposal. We would rather decline the work than fill the gap with whoever is on the bench.
Changes are raised before they happen
People leave and circumstances change. When they do, you hear it before the engagement starts — not in a status report three months later.
You meet them before you sign
The technical conversation is with the people who would do the work. The commercial conversation happens afterwards.
What the team holds, in aggregate
Certifications are the entry ticket rather than the argument — but you are entitled to know the depth of the bench before you commit to a program.
Meet the people who would run it
The first conversation is with a consultant who works in your domain — not a sales development representative working from a script.