How we work
Value, feasibility, risk and adoption, in the same conversation from day one.
A stage-gated, co-delivery model. At each gate, client and consulting leads explicitly decide to continue, revise, pause or stop. This prevents sunk-cost momentum from replacing evidence.
Delivery principles
Six commitments that shape every engagement
Value before volume
Prioritize a small number of measurable opportunities.
Evidence before scale
Test value, quality, safety and behavior, not technical feasibility alone.
Humans stay accountable
Design oversight and escalation around consequence and uncertainty.
Reuse before rebuild
Work with the client's platforms and standards where they are fit.
Open by design
Use clear architecture, portable knowledge and explicit vendor trade-offs.
Transfer from day one
Pair, document and teach throughout, not only at handover.
The journey
Eight stages, three decision gates
Phase 0
Onboarding
Agree outcomes, scope, ways of working and access.
- Charter
- Success measures
- Governance cadence
- Access/data plan
- RAID log
Phase 1
Discovery
Understand work, users, data, platforms, controls and constraints. Establish the foundation.
- Current State to Future State Mapping
- Data and Systems Audit
- Regulation and Compliance
- Adoption Plan
- Project Scope & Risks
Phase 2
System Blueprint
Design the architecture and operation boundaries.
- Architecture Design and System Integration.
- AI Model Selection and Agentic layer Design
- Safe Operation within Approved Boundaries
Phase 3
Build
Engineer the production capability and connect it to real systems and controls.
- Tested product
- Integrations
- Telemetry
- Documentation
- Release evidence
Phase 4
Transfer
Embed the capability in roles, decisions and daily work.
- Training
- Champions
- Communications
- Support model
- Ownership handover
Phase 5
Track
Sustain quality, manage risk and compound value.
- Monitoring
- Service reviews
- Improvement backlog
- Quarterly value report
- Exit plan
Governance & co-delivery
Three connected levels keep decisions close to evidence
| Level | Participants | Cadence | Focus |
|---|---|---|---|
| Executive steering | Executive sponsor, accountable business owner, CIO/CDO/risk as relevant, consulting partner | Monthly or at major gates | Value, risk, investment, dependencies and decisions |
| Product & value team | Product owner, process owner, data/technology leads, change lead, consulting lead | Weekly | Priorities, measures, user feedback, readiness and blockers |
| Delivery squad | Client SMEs and cross-functional consultants: product, process, data, engineering, UX, risk/change | Daily collaboration; 1–2 week sprints | Design, build, evaluate, integrate, document and transfer |
Our responsibilities
- Challenge the problem and value hypothesis.
- Bring senior business, product, data and engineering capability.
- Make trade-offs and risks visible early.
- Design for security, adoption and operations.
- Document decisions and transfer capability.
- Report evidence honestly, including failed assumptions.
Client responsibilities
- Name an accountable sponsor and empowered product owner.
- Provide timely SME, user, data and system access.
- Engage security, legal, risk, HR and procurement early.
- Own business decisions and organizational change.
- Validate measures, controls and release decisions.
- Plan internal ownership before production.
Engagement formats
A credible first step and a visible route to scale
| Format | Best for | Indicative shape | Core output |
|---|---|---|---|
| Executive AI briefing | Leadership alignment and decision framing | 1–2 facilitated sessions | Shared context, opportunity themes and decisions required |
| AI opportunity & readiness sprint | Moving from broad ambition to priorities | 2–4 weeks | Readiness baseline, prioritized use cases and 90-day action plan |
| Value proof | Testing value, feasibility, risk and adoption before scale | 6–10 weeks | Working pilot, evidence scorecard and scale/no-scale decision |
| Build & scale program | Production delivery across systems and teams | Multi-phase, typically 3–9 months | Production capability, controls, adoption and ownership transfer |
| Embedded AI squad | Adding senior cross-functional capacity to a client program | Dedicated team, sprint cadence | Prioritized delivery backlog and integrated capability |
| Fractional CAIO / advisory | Ongoing executive leadership without a full-time role | Monthly retainer | Portfolio direction, governance, vendor and investment decisions |
| Managed AI improvement | Operating and improving live AI products | Ongoing service with agreed levels | Monitoring, evaluation, optimization, support and value reviews |
Durations are indicative. Actual scope depends on access, data readiness, risk level, integrations, procurement and client availability.
Aftercare
Operate & improve: sold as stewardship, run on evidence
Aftercare is active product stewardship, not a vague support promise.
Launch stabilization
Typical period: first 30 days after release.
- · Priority incident and user support
- · Usage, latency, cost and quality observation
- · Knowledge and retrieval tuning
- · Workflow and escalation refinements
- · Daily/weekly launch review as appropriate
Managed improvement
Typical period: ongoing, with defined service levels.
- · Automated and human quality evaluation
- · Model, prompt, agent and knowledge changes
- · Security and misuse monitoring
- · Adoption and business-value analysis
- · Prioritized improvement releases
Minimum operating scorecard
| Dimension | Illustrative measures |
|---|---|
| Business value | Cycle time, avoided effort, conversion, service level, decision latency or revenue influence |
| Adoption | Eligible vs. active users, repeat use, task completion, abandonment and satisfaction |
| Quality | Task success, groundedness, accuracy, escalation, false positives/negatives and human acceptance |
| Risk & safety | Policy violations, sensitive-data events, harmful outputs, control failures and incidents |
| Reliability | Availability, latency, integration failures and recovery time |
| Economics | Cost per task/outcome, token/model cost, support effort and infrastructure utilization |
Every quarter we reconfirm the business baseline, benefits, risks, user behavior, technical health, cost and ownership, and agree what to improve, scale, retire or redesign next.