Claude live, governed
and cost-controlled.
For organisations that have bought Claude but haven’t started, and for enterprises that need a partner to set up the platform, guardrails and budget controls before scaling.
Sound familiar?
Adoption has stalled
You have Claude seats, but many sit idle and teams don’t know where to start.
Guardrails before scale
IT and security need SSO, roles, data controls and approved connectors before anyone scales.
Predictable spend
Leadership wants spend limits, chargeback and a clear view of the value Claude delivers.
Five phases from licence to live.
- Immerse · 1–2 weeks
Immerse
Executive workshop, use-case discovery and prioritisation, a data and security readiness check, success metrics and the rollout plan.
- Set up · 1–2 weeks
Platform and guardrails
SSO and SCIM provisioning, roles mapped to identity groups, Claude Code managed settings, approved connectors and MCP servers, a private plugin marketplace, network allowlists and telemetry to your SIEM.
- Control · from day one
Budget control
Group and organisation spend limits, usage dashboards, department chargeback, alert thresholds and a monthly cost review.
- Enable · 2–3 weeks
Champion tracks
Engineering track: Claude Code with repository conventions, hooks and CI/CD. Business track: Claude and Cowork with department workflows, plugins and skills.
- Go live · 2 weeks
Go live and hypercare
Go-live support, an adoption dashboard, a 30-day value report, and handover to your team or to Claude Managed Services.
Deliverables you keep.
- Immerse readout and rollout plan
- Platform and guardrail design document
- Configured Claude tenant
- Budget-control model
- Trained champion network
- Adoption dashboard and 30-day value report
Sized to your scope.
One track, one business unit
A focused start for one team or function.
Both tracks, several units
Engineering and business teams together.
Multi-region or regulated
With Claude Managed Services handover built in.
Scope and fees are agreed per engagement.
Commitments written into your statement of work.
- Platform and guardrail design signed off before users are added
- SSO enforced only after roles are tested
- Approved connectors only
- Baseline and success metrics agreed in Immerse
- Spend limits from day one
- A 30-day value report
- Claude added into the tools you already run
- No parallel stack to maintain
- Smartify, not rip-and-replace