Claude Enterprise deployment and activation
We deploy Claude Enterprise across your company in 6 to 10 weeks, on five parallel tracks: platform setup, custom Projects, connectors, role-specific training and adoption tracking. We run the same playbook on ourselves, with six of our own departments on Claude. Deployment ends when your team is using Claude every week, not when the tenant is provisioned.
Phase 2 deployment at a glance
Softblues is a London-based AI practice and Registered Anthropic Partner Network member. We run a 6 to 10 week Claude Enterprise deployment across five parallel tracks (platform, Projects, connectors, training and adoption). It is complete only when the agreed activation criteria are met across functions, not when a tenant is provisioned.
Five tracks run together, with milestone reviews at weeks 4, 6, 8 and 10. Scope is fixed at kickoff, with no drift.
Platform, Projects, Connectors, Training, Adoption. Each has an owner and a weekly cadence.
Concrete conditions across usage, Projects, connectors, champions, training and leadership sign-off. Measured, not aspirational.
The adoption threshold for activation. Real use in functions, not licence counts. It is the metric we are paid against.
Why does Claude Enterprise deployment take 6 to 10 weeks?
Spinning up a Claude tenant takes a few clicks. Getting Claude into how your company actually works takes six to ten weeks of real engineering. Three reasons it matters.
Turning on the licence is the easy part
Setting up a tenant is a few clicks. The real work is getting identity, governance and security right for your business. We handle that in week one, so the rest of the deployment can focus on what makes your company different.
Without Projects and connectors, Claude is just a chat window
A standard tenant gives your team a capable general assistant. The leverage comes from custom Projects wired to your CRM, finance and support systems. Without them, people copy and paste. With them, work moves in and out of Claude on its own.
Adoption is what counts, not licences
Most enterprise AI rollouts stall because no one checked whether people actually used the tool. We call a deployment complete only when at least 70 percent of licensed users are active in Claude every week, across three or more teams.
What we do during deployment
Five parallel tracks, each with an owner and a weekly cadence. Milestone reviews at weeks 4, 6, 8 and 10.
Platform
Tenant setup, identity and SSO, the role and permission model, audit logging, data residency and retention, security baseline. Done in weeks 1 to 2.
Projects
Custom Claude Projects per function. Each bundles the system prompt, knowledge base, Skills and connectors for a role. Built and shipped weeks 2 to 8.
Connectors
MCP servers and direct integrations to Workspace or M365, CRM, finance, support, knowledge base and the industry systems your strategy identified.
Training
Role-specific paths for leadership, managers, individual contributors and engineering. Live and recorded. The champion programme runs in parallel.
Adoption
Weekly metrics by function. Office hours weekly. The champion network meets fortnightly. Activation criteria reviewed at weeks 4, 6, 8 and 10.
When is the deployment considered activated?
Not when the tenant is set up. Not when training is delivered. Activation requires six concrete conditions across usage, Projects, connectors, champions, training and leadership confirmation.
70%+ active users weekly
At least 70 percent of licensed users working in Claude every week across the first three deployed functions. Real usage, not log-ins.
Each Project hitting its 50% target
Every shipped Project used by at least half of its target audience within fourteen days of release. Tracked per Project.
All connectors live and monitored
Every planned connector in production with monitoring, error tracking and rate-limit management. No half-shipped integrations.
A champion in every function
A trained, certified internal champion in each deployed function. They own day-to-day adoption support after activation.
80%+ training completion
At least 80 percent of staff have finished their role-specific path. Tracked per cohort, with refreshers for stragglers.
Signed-off leadership readout
A final readout confirming the five tracks have hit target, signed off before activation is called.
Want to see how activation criteria apply to your deployment?
Book a scoping callWhat kinds of custom Claude Projects does Softblues build?
Six examples of what a typical deployment ships. The exact mix comes from the build catalogue in your Phase 1 strategy. Each Project bundles the system prompt, the knowledge base, the Skills and the connectors a role needs.
Sales proposal Project
Drafts proposals using your CRM, pricing rules and past wins. Cuts proposal time from days to hours.
Market research Project
Pulls competitive intel, industry signals and customer voice into briefs. Sharper, faster strategy work.
Customer email Project
Drafts and triages support and account email against your tone, history and policy. Better answers, faster.
Hiring panel Project
Generates role-specific interview kits, scorecards and candidate summaries from your ATS data.
Operations runbook Project
Turns SOPs and playbooks into queryable knowledge. Frontline teams get answers without escalation.
Compliance review Project
Drafts policy reviews, contract checks and audit responses against your control frameworks.
For ongoing build, tuning and quarterly capability reviews after activation, see our Phase 3: Continuous AI Partnership page. For the strategy that decides the build catalogue, see Phase 1: AI Strategy and Roadmap.
External reference: Anthropic publishes the Claude Projects documentation we build against.
Common questions about Claude Enterprise deployment
How long does Claude Enterprise deployment really take?
Six to ten weeks for a typical deployment. Smaller organisations with simpler stacks land closer to six. Larger organisations with regulated data and many connectors land closer to ten. Softblues sets the timeline at kickoff based on your scope.
What is included in the deployment fixed fee?
Platform setup, identity and SSO configuration, the connector set agreed at kickoff, the custom Projects in your build catalogue, the training programme delivery, and the adoption tracking through to activation. Softblues shares a fixed quote after Phase 1 strategy or after a scoping call.
Do we need an internal AI lead before we start?
No, but we recommend you nominate one during deployment. Softblues runs a champion programme that trains a small group of internal advocates across functions. By activation they own day-to-day adoption support, with us still available for builds and reviews.
What if the team does not adopt it?
Adoption is the metric we are paid against, so it is the metric we obsess over. Activation criteria require demonstrable usage across functions, not just a licence count. If adoption is lagging at week six, Softblues runs additional enablement, builds the missing Projects, and adjusts training before declaring deployment complete.
Which connectors do you typically build?
Google Workspace or Microsoft 365 for documents and email, your CRM (Salesforce, HubSpot, Pipedrive), your finance system (Xero, NetSuite, Sage), your support system (Zendesk, Intercom, Freshdesk), your knowledge base (Confluence, Notion, SharePoint), and one or two industry-specific systems. The exact set is decided in Phase 1 or at scoping.
Can deployment run in parallel with Phase 1 strategy?
No. Deployment depends on the prioritised use cases, build catalogue, and training plan that Phase 1 produces. If you already have an equivalent strategy from elsewhere, Softblues will assess it at kickoff and skip directly into deployment.
How can you start?
Book a 20-minute call
A no-pitch conversation about where Claude could fit in your business. A Softblues team member will be on the call.
Book a callTake the Claude Readiness Score
Score your company's readiness for Claude Enterprise and get a plan back.
Start the assessmentGet the Buyer's Guide
A reference on platform choice, governance, costs, rollout timing and the questions to ask any vendor.
Download the guide