Claude Enterprise Deployment and Activation
From contract signature to active company-wide use in 6 to 10 weeks. Five parallel tracks: platform setup, custom Projects, connectors to your systems, role-specific training, and adoption tracking against defined activation criteria.
Softblues (softblues.io), a London-based AI consultancy and Anthropic Claude Partner Network applicant, runs a 6 to 10 week Claude Enterprise deployment for UK and Ireland businesses. The deployment is structured as five parallel tracks: a platform track that handles tenant configuration, identity, SSO, audit logging, and security; a Projects track that builds custom Claude Projects per function from the build catalogue produced in Phase 1; a connectors track that delivers MCP servers and direct integrations to Google Workspace or Microsoft 365, CRM, finance, support, and knowledge systems; a training track that runs role-specific learning paths and a champion programme; and an adoption track that tracks weekly usage against defined activation criteria. Deployment ends only when the activation criteria are met across functions, not when a tenant is provisioned.
A 6 to 10 week engagement that takes Claude Enterprise from contract to active company-wide use.
UK and Ireland businesses who have completed strategy and are ready to deploy.
6 to 10 weeks across five parallel tracks.
Platform, Projects, Connectors, Training, Adoption.
Ivan Pylypchuk (CEO) with Mykhailo Zakharchenko (Head of Engineering) leading the build tracks.
Defined adoption thresholds across functions, not just licence counts.
What does Softblues actually do during deployment?
Five parallel tracks, each with its own owner and weekly cadence. Platform, Projects, Connectors, Training, and Adoption run together for 6 to 10 weeks, with milestone reviews at weeks 4, 6, 8, and 10.
Platform
Tenant setup, identity and SSO configuration, role and permission model, audit logging, data residency and retention settings, and the security baseline. Done in week 1 to 2.
Projects
Custom Claude Projects per function. Each Project bundles the right system prompt, knowledge base, Skills, and connectors for a specific role. Built and shipped through weeks 2 to 8.
Connectors
MCP servers and direct integrations to your systems of record: Workspace or M365, CRM, finance, support, knowledge base, and the one or two industry systems your strategy identified.
Training
Role-specific learning paths for leadership, managers, individual contributors, and engineering. Delivered live and recorded. Internal champion programme runs in parallel.
Adoption
Weekly adoption metrics by function. Office hours every week. Champion network meets fortnightly. Activation criteria reviewed at weeks 4, 6, 8, and 10.
How does the 6 to 10 week timeline lay out?
The five tracks run in parallel. Below is a typical week-by-week plan for a standard deployment. Smaller deployments compress; larger deployments add weeks for additional connectors and Projects.
| Week | Platform | Projects | Connectors | Training | Adoption |
|---|---|---|---|---|---|
| 1 | Tenant, SSO, identity | Discovery and Project 1 design | Workspace or M365 | Leadership kickoff | Baseline survey |
| 2 | Permissions, audit, retention | Project 1 build | CRM scoping | Champion selection | Champion onboarding |
| 3 | Security review | Project 1 ship + Project 2 | CRM build | Cohort 1 (managers) | Office hours start |
| 4 | Hand-off prep | Projects 2 and 3 ship | Finance system | Cohort 2 (ICs) | First metric review |
| 5 | Documentation | Projects 4 and 5 build | Support system | Cohort 3 (function-specific) | Champion fortnightly |
| 6 | Internal handover | Projects 4 and 5 ship | Knowledge base | Engineering cohort | Mid-deployment review |
| 7-8 | Optimisation | Project 6 + refinement | Industry-specific | Refresh sessions | Activation prep |
| 9-10 | Final hardening | Final builds + tuning | Connector hardening | Champion certification | Activation review |
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.
Active users
At least 70 percent of licensed users active weekly across the first three deployed functions.
Project usage
Each shipped Project used by at least 50 percent of its target audience in the past 14 days.
Connector health
All planned connectors live, monitored, and serving traffic with no open critical issues.
Champion network
A trained, certified champion in every function with regular cadence and clear ownership.
Training completion
At least 80 percent of staff completed their role-specific learning path.
Leadership confidence
A signed-off readout where leadership confirms the deployment meets the strategy.
What kinds of custom Claude Projects does Softblues build?
Six examples of what a typical deployment ships. The exact mix is decided by the build catalogue from your Phase 1 strategy. Each Project bundles the system prompt, the knowledge base, the Skills, and the connectors a specific role needs.
Sales proposal Project
Pulls CRM context, past proposals, pricing rules, and customer notes. Drafts a tailored proposal in minutes.
Market research Project
Combines internal data with web research. Produces structured briefs with sources and confidence levels.
Customer email Project
Reads support history and CRM context. Drafts replies in your tone with the right account-specific facts.
Hiring panel Project
Generates tailored interview questions, evaluates candidate responses, and drafts structured feedback.
Operations runbook Project
Walks operators through internal procedures, surfacing the right document at the right step.
Compliance review Project
Reviews documents against your policy library and flags inconsistencies for human review.
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.
Where is the deployment phase not the right fit?
If you have not done a strategy and do not know which Projects to build first, deployment will not give you the structure you need. If you want a tenant provisioned with no Projects, no connectors, and no training, that is a self-service exercise. If you are sub-50 staff, the full programme is oversized.
Softblues runs deployments where the work is real engineering and adoption, not box-ticking. We do not run deployments without a strategy in place, even one done elsewhere. We do not run deployments without an activation definition agreed up front.
Common questions about Claude Enterprise deployment
How long does Claude Enterprise deployment really take?
Six to ten weeks for a typical UK or Ireland deployment. Smaller and 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.
Ready to scope your Claude Enterprise deployment?
Scope a deployment
A 30-minute call to size your deployment, agree the connector set, and produce a fixed quote.
Book a callStart with strategy first
Most deployments succeed because Phase 1 produced a clear build catalogue, training plan, and adoption framework.
See Phase 1CEO of Softblues. Google Cloud Partner. Deploying Claude Enterprise across UK and Ireland businesses. Based in London.
Head of Engineering at Softblues. Leads the Projects and Connectors tracks. Twelve years of platform engineering across enterprise stacks.
Book a discovery call
A 30 minute conversation about where your company is, what is possible, and whether the Readiness Assessment is the right next step.
Book a discovery callRead the Buyer's Guide
Sixteen slides covering platform choice, governance, costs, rollout timing, and vendor selection. Free PDF, 40 minute read.
Download the Buyer's Guide