Claude Services / Rollout & Enablement
Claude live, configured, and actually being used.
SSO and tenant setup, seat provisioning, champion training and enablement, and go-live support — the difference between licences bought and Claude in daily use.
Engagement
Scoped to a fixed fee
Fixed scope
Typical timeframe
3–6 weeks
Who it's for · Organisations that have bought Claude seats and want a governed, well-adopted launch rather than an email with a link in it.
The engagement
- 01
Technical setup with IT and identity: tenant, SSO, SCIM, and governance settings
- 02
Champion enablement and configuration of the baseline workspace
- 03
Launch: onboarding sessions, comms, and the first wave of users
- 04
Go-live support, adoption baseline, and handover to your champions
What you walk away with
A configured Claude tenant, trained champions, and a launched user base with support in place.
What we deliver.
- Tenant and workspace setup, including data-retention and governance settings
- SSO and SCIM configuration with your identity provider, and directory-driven provisioning
- Seat allocation model, role design, and admin governance
- Baseline connectors, projects, and shared instructions so users start with something useful
- Champion programme — selection, deep-dive training, and a support playbook they can run
- Launch communications, onboarding sessions, and quick-reference guides for users
- Go-live support window plus an adoption baseline you can measure against
In practice
A first enterprise-wide Claude launch across several thousand seats
A department pilot configured properly so it can survive scrutiny and scale
Re-launching after an unmanaged rollout that stalled
Before you start.
What you'll need
- Claude seats purchased or ready to purchase
- Identity provider admin access for SSO and SCIM
- A named internal owner and candidate champions
Not included
- Anthropic seat licences and consumption
- Custom connectors to proprietary systems (that's Connectors, Plugins & API Integrations)
- Ongoing adoption management after the launch window (that's the Adoption / CoE Programme)
An Anthropic partner with Claude-certified architects — the people who scope your programme are the people who build it.
50+ specialists across strategy, implementation, automation, data, and custom development, so a Claude programme lands in your real systems.
Every engagement leaves your team trained and documented — you own the outcome after we go.
Questions, answered.
Frequently — this is the engagement that fixes a launch where seats went out but usage didn't follow. We'd start from your current configuration and usage data rather than from zero.
From a single team to a full organisation. Larger populations are launched in waves, with each wave informing the next.
Anthropic seats and API consumption are billed to you on your own account, so the environment and the data stay yours. We help you land on the right plan and model mix as part of the engagement.
No. Business and enterprise plans and API usage are excluded from model training by default. We configure your workspace to your data-retention and governance requirements and document what was set.
/ Start
Scope Rollout & Activation.
A configured Claude tenant, trained champions, and a launched user base with support in place.
30 minutes. You'll leave with a clear recommendation.