Fixed scope
Fixed-scope engagements
Best for: Scoped assessments, initial roadmaps and architecture blueprints.
How it works: A defined scope, timeline and deliverable, agreed before work begins.
When to use: Top-of-funnel diagnostic work such as AI readiness assessments, workshops and
architecture blueprints.
Why it works: Low friction for enterprise procurement, because scope and risk are clearly
bounded. It builds trust before larger initiatives.
Our AI implementations run this way: a fixed scope, timeline and
handover, agreed before the build begins.
Milestones
Milestone-linked engagements
Best for: High-impact AI capability deployments and architecture reviews.
How it works: Work is organized around agreed technical or strategic milestones, such as
architecture sign-off, evaluation suite validation and governance framework completion.
When to use: Strategic advisory where you want measurable progress and clear deliverables rather
than open-ended effort.
Why it works: Clear acceptance criteria align everyone on what done means, so delivery risk
stays low and accountability is visible.
Longer implementations, such as Legacy Modernisation
or a First Production Agent, can also run against milestones.
Retainer
Advisory retainer
Best for: Ongoing strategic advisory, fractional CAIO support and architectural oversight.
How it works: A dedicated allocation of senior consultant time and availability on an ongoing
basis.
When to use: Long-term governance, executive coaching, technology board oversight, or an
independent technical advisor overseeing internal or vendor engineering teams.
Why it works: Continuous access to senior expertise, without having to scope each question as a
separate project.
Flexible
Capped flexible advisory
Best for: Dynamic technical governance, ad-hoc advisory and complex environments with shifting
requirements.
How it works: Senior consultant time used flexibly, within an agreed ceiling for each month or
quarter.
When to use: Deep technical audits, code reviews or governance oversight where the depth of
technical debt or complexity cannot be known upfront.
Why it works: You can reprioritize as technical discoveries are made, with guardrails that keep
scope from drifting.