Skip to content

Our approach

From a first look
to everyday use.

A practical path for putting Claude to work. Establish where it fits, prove one use case, and build the controls and operating practices needed to use it with confidence.

A path from opportunity to operation

Select a stage to explore

Ways to engage

STAGE 01

First Light

See where AI fits.

Establish a practical starting point before committing to a larger engagement.

ENGAGEMENT 01

AI Readiness Check + Engineer Walkthrough

3-minute check + 30-minute review

For teams exploring where Claude could help and what needs to be in place first.

WHAT THE ENGAGEMENT PRODUCES

  • A readiness score across seven dimensions, with no email required to see it.
  • An engineer-led review of the results and current priorities.
  • Recommended next steps for a focused engagement.

THE DECISION IT SUPPORTS

Choose whether to explore an opportunity, address readiness gaps or defer implementation.

Take the readiness check

STAGE 02

True North

Set the course.

Turn broad interest into a defined use case, a delivery plan and the controls needed to proceed.

ENGAGEMENT 02

AI Opportunity Workshop

Half day or full day

For business and technology teams deciding which operational problems are worth pursuing.

WHAT THE ENGAGEMENT PRODUCES

  • Review of real workflows and approved sample documents.
  • Three to five use cases ranked by value and feasibility.
  • A recommended starting point and the assumptions to test.

THE DECISION IT SUPPORTS

Select the first use case and nominate the business owner.

Discuss a workshop
ENGAGEMENT 03

Readiness & Roadmap Assessment

Typically 2–4 weeks

For organizations that need a defensible implementation plan before assigning delivery resources.

WHAT THE ENGAGEMENT PRODUCES

  • Review of data, security, integration and team readiness.
  • Scored use cases with supporting business cases.
  • A 90-day roadmap with dependencies and responsibilities.

THE DECISION IT SUPPORTS

Agree the sequence of work and the readiness gaps to resolve.

Discuss an assessment
ENGAGEMENT 04

Governance & Compliance Pack

Typically 2–4 weeks

For teams that need clear rules for AI use and evidence that internal reviewers can inspect.

WHAT THE ENGAGEMENT PRODUCES

  • An inventory of AI tools within the agreed scope.
  • Use policies, risk tiers and assigned control owners.
  • An evidence pack supporting internal risk and compliance review.

THE DECISION IT SUPPORTS

Agree permitted uses, review responsibilities and controls before rollout.

Discuss governance requirements

STAGE 03

Lift-Off

Prove the approach.

Test one bounded use case against an agreed goal before expanding the implementation.

ENGAGEMENT 05

Governed Pilot

Typically 4–8 weeks

For teams with a defined use case that need evidence of feasibility and operational fit.

WHAT THE ENGAGEMENT PRODUCES

  • One working use case in an approved environment.
  • Written acceptance criteria and representative test results.
  • Documented limitations and a recommendation for the next step.

THE DECISION IT SUPPORTS

Proceed, revise or stop based on the agreed criteria and the observed results.

See how the pilot runs

STAGE 04

Ascent

Build it into everyday work.

Turn an agreed direction into a working capability, with the training, controls and ownership needed for daily use.

ENGAGEMENT 06

Claude Rollout & Enablement

Typically 4–8 weeks

For organizations preparing teams to use Claude within approved workflows and access boundaries.

WHAT THE ENGAGEMENT PRODUCES

  • Documented Claude Enterprise configuration and access rules.
  • Role-based training using relevant work.
  • An adoption baseline and a plan for reviewing use.

THE DECISION IT SUPPORTS

Confirm teams are ready for wider use and assign ongoing ownership.

Explore AI enablement
ENGAGEMENT 07

Workflow Automation Build

Typically 6–12 weeks

For teams ready to connect a proven use case to the systems and decisions it supports.

WHAT THE ENGAGEMENT PRODUCES

  • A production implementation with agreed integrations.
  • Human review, exception handling and monitoring.
  • Acceptance results and an operating runbook.

THE DECISION IT SUPPORTS

Authorize release against the agreed acceptance criteria and support plan.

Explore document workflows
ENGAGEMENT 08

Application Modernization

Defined by the agreed scope

For organizations changing essential software while preserving the business behavior that matters.

WHAT THE ENGAGEMENT PRODUCES

  • A map of legacy code, dependencies and business rules.
  • One defined part of the application migrated or rebuilt.
  • Tests comparing the new implementation with current behavior.

THE DECISION IT SUPPORTS

Accept the migrated scope and decide which part should follow.

Explore application modernization

STAGE 05

Orbit

Operate and improve.

Keep the implementation under review as usage, business requirements and models change.

ENGAGEMENT 09

Managed AI Operations & Advisory

Ongoing monthly engagement

For teams that need continued engineering support and a structured review of an operating AI service.

WHAT THE ENGAGEMENT PRODUCES

  • Review of quality, usage, operating cost and errors.
  • Regression testing when models or workflows change.
  • A quarterly roadmap review and agreed improvement priorities.

THE DECISION IT SUPPORTS

Prioritize changes using operating evidence and decide when to expand or retire a capability.

Discuss ongoing operations

Timelines are indicative. Scope, access requirements, responsibilities and acceptance criteria are agreed before delivery.

Inside a governed pilot

A working solution.
A decision supported by evidence.

A pilot answers a specific question before a broader commitment. Business owners and engineers review the same evidence at each step.

  1. 01

    Agree the goal

    Define the workflow, baseline and success criteria in writing.

    Work productScope & acceptance brief
  2. 02

    Build one use case

    Implement a working slice in an approved environment, with defined access and review points.

    Work productWorking implementation
  3. 03

    Test the difficult cases

    Evaluate representative records, exceptions and failures against the agreed criteria.

    Work productTest results & limitations
  4. 04

    Make the next decision

    Review the evidence and choose whether to proceed, revise the scope or stop.

    Work productDecision & next-step plan

Built for ownership

The work stays
with the team.

Forward-deployed engineers work directly with business and technical owners. The handover is part of delivery from the start.

Implementation
Code, configuration and integration documentation for the agreed scope.
Evaluation
Repeatable tests, acceptance results and a record of known limitations.
Operation
A runbook, named owners and a plan for reviewing material changes.

A useful first conversation

Bring one workflow.
Leave with a clearer next step.

Start with the readiness check or discuss a specific implementation need.

Take the readiness assessment Discuss an engagement