Named roles, not named individuals we can't guarantee will still be around in six months. Here's the honest split between dedicated and shared.
Plenty of delivery models put an experienced-looking name on the proposal slide and staff the actual work with whoever's free that week. We'd rather tell you plainly how dedicated versus shared our own model is, since that's the number that actually predicts how the project feels to work with.
A specialist like the AI & automation lead is shared across projects because most engagements don't need that role full-time, and pretending otherwise would mean charging you for capacity you're not using. What we will commit to is telling you exactly which roles are shared, and roughly what share of their time you're getting, before you sign anything.
Through Diagnose, Design, and Build, yes, barring a genuine, disclosed exception. Continuity there is deliberate, not accidental.
Yes. We'll introduce the proposed engagement lead and functional consultant during scoping, not just a generic company overview.
We'll tell you immediately and name the replacement along with how much handover time they've had, rather than quietly substituting someone.
During Build, Data, and Prove, largely yes. Outside that window they may be shared with one other engagement, which we'll disclose against your specific timeline.
Scale often means more shared, pooled staffing by necessity. We stay deliberately smaller so the dedicated-role commitments above are actually true for most engagements we take on, not an exception.
Tell us the scope you're considering. We'll tell you honestly which roles would be dedicated and which would be shared.
With someone who has run this before.
The six stages this page fits into, end to end.