Claude services · Rollout & Activation

Claude configured, launched, and supported through go-live.

We set up the tenant, SSO, and SCIM, design seat allocation and roles, configure a baseline workspace, train champions, run onboarding sessions, and support go-live with an adoption baseline you can measure against.

What you getAll Claude services
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 the launch configured, governed, and supported.
What you walk away with
A configured Claude tenant, trained champions, and a launched user base with support in place.

What you get

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

  1. 01A first enterprise-wide Claude launch across several thousand seats
  2. 02A department pilot configured properly so it can survive scrutiny and scale
  3. 03Re-launching after an unmanaged rollout that stalled

Scope

What you need, and what is not included.

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)

The engagement

  1. 01Step 1

    Technical setup with IT and identity: tenant, SSO, SCIM, and governance settings

  2. 02Step 2

    Champion enablement and configuration of the baseline workspace

  3. 03Step 3

    Launch: onboarding sessions, comms, and the first wave of users

  4. 04Step 4

    Go-live support, adoption baseline, and handover to your champions

  • An Anthropic Select 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 the Claude work is connected to the systems you run.
  • Every engagement ends with training and documentation, so your team runs it without us.

Questions

Frequently asked questions.

We already turned Claude on. Is this still relevant?

Often, yes. This is the engagement for a launch where seats went out but usage did not follow. We start from your current configuration and usage data.

How many users can you launch at once?

From a single team to a full organisation. Larger populations are launched in waves, with each wave informing the next.

Who pays for Claude licences?

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.

Does our data train Anthropic's models?

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.

Next step

Book a discovery call.

Tell us where you are with Claude and what you want from Rollout & Activation. You leave the call knowing whether it fits and what the fixed-fee proposal will cover.

Email hello@workiflow.com

30 minutes. No commitment.