From AI experiments
to a verified Claude deployment.

The engagement journey

Four steps, in order. Each produces a deliverable you keep — not a report you file away.

1. Exhibit 01

   Entry audit

   An inventory of your organization’s AI surface — what tooling exists, what is claimed versus what is measured, and where drift lives between the two. We read the actual configuration, not the slide deck describing it.

   Deliverable A written state-of-play with evidence — what runs, what is unverified, what is missing.
2. Exhibit 02

   Claude Code activation

   We scope, deploy, configure, and run Claude Code activations end-to-end — workspace setup, permissions, MCP and tooling wiring, and team onboarding, so the activation is something your team can run without us in the room.

   Covers Workspace setup · permissions · MCP/tooling · team onboarding.
3. Exhibit 03

   Paid pilot

   A bounded engagement with visible deliverables: working automations built against your own workflows, a measured before/after, and reports you can rerun yourself — not a one-time demo.

   Deliverable Working automations · measured before/after · rerunnable reports.
4. Exhibit 04

   Rollout

   Two supported destinations — a genuine choice, not a foregone conclusion. Anything outside these two is a paid migration pilot of its own, not the default offer.

   Option A Local edition — runs on your own infrastructure.

   Option B Claude Enterprise — hosted org deployment.

   Anything else A scoped migration pilot — other clouds, homegrown infrastructure.

The practice runs on its own instruments

Every engagement is backed by the same tools we ship — not a slide, a running system.