How to Roll Out Claude in 90 Days: A Partner-Led Plan

Claude

AI

Anthropic

Anthropic S-1 analysis: $40 trillion addressable market, about 1% of enterprises penetrated

Free AI at Work Playbook for managers using ChatGPT, Claude and Gemini.

Free AI at Work Playbook for managers using ChatGPT, Claude and Gemini.

➔ Download the Playbook

A successful enterprise Claude rollout takes about 90 days, in three phases with a decision gate at the end of each.

Phase

Days

What happens

Lay the foundations

0–30

Identity, security, access, sponsorship, spend controls and a baseline

Activate

30–60

A first wave of whole teams is trained, supported by champions and measured weekly

Prove and decide

60–90

Results are measured against the baseline, and the sponsor decides to scale, extend, adjust or stop

Generation Digital is a certified partner in Anthropic's Claude Partner Network. This is how we plan and run Claude rollouts for enterprises in the UK, US and Canada, in line with Anthropic's best practice.

Get the free Claude 90-Day Rollout Planner → (PDF and editable Excel)

Key takeaways

  • 90 days, three gates. Day 30 opens the first wave, day 60 checks adoption, and day 90 is the decision to scale.

  • Foundations come before licences. Identity, security review, permissions, spend caps and named owners are settled in the first 30 days, before most people get access.

  • Start with whole teams, not scattered volunteers. A first wave of a few complete teams, including one under the sponsoring executive, shows how Claude changes real work.

  • Measure people, not switches. Weekly active users over assigned seats, how many go beyond chat, and one work metric per team, all against a day-0 baseline.

  • The sponsor owns the decision. At day 90 the executive sponsor, not the vendor or partner, presents the results and makes one call: scale, extend, adjust or stop.

  • A partner shortens the path. An experienced Claude partner brings the checklists, the governance patterns and the change programme, so you spend 90 days proving value rather than working out the method.

Why plan a Claude rollout in 90 days?

Ninety days is long enough to prove value and short enough to keep momentum. Anthropic's Enterprise AI Transformation Guide recommends focused pilots of 8 to 12 weeks, with efficiency gains usually visible by weeks 4 to 6. It also notes that 92% of companies plan to invest in generative AI over the next three years, but only 1% say their investments have reached full maturity.

The gap between those two numbers is rarely the technology. It's everything around it:

  • unclear ownership

  • security reviews that drag on

  • licences handed out without training

  • no baseline to measure against

  • no one with the authority to decide what happens next

A 90-day plan with fixed gates closes that gap. Every week, everyone can see which decisions are live, who owns them and what evidence closes each gate.

What does the 90-day Claude rollout plan look like?

Gate

When

What must be true

Wave one opens

Day 30

Security review closed on evidence; identity and provisioning done; roles, seat tiers and spend caps set; data retention agreed; sponsor, budget owner and admin owners named in writing; day-0 baseline recorded; first teams chosen

Adoption checkpoint

Day 60

Adoption read against agreed milestones; teams that are falling behind diagnosed and helped within two weeks; dashboards and alerts live

Readout and scale gate

Day 90

Value shown against the baseline; adoption and spend by week; wins told by the people who achieved them; one decision with an owner, an action and a date

Eight workstreams run across the three phases:

#

Workstream

What it settles

Days

1

Organisation and identity

One Claude organisation or several; single sign-on; automatic provisioning from your directory

0–30

2

Security posture

Security review cleared; connector permissions; posture for Claude Code by team

0–30

3

Access and governance

Roles and permissions, approved connectors, who can build and publish skills and plugins, data retention

0–30

4

Sponsorship and escalation

Executive sponsor, budget owner and admin owners in writing; an escalation path with owners and dates

0–14

5

Cost governance

Spend caps in layers, and who approves going over them

0–30

6

Visibility

Usage and spend reporting; Claude Code telemetry into your own monitoring

0–90

7

Enablement and champions

Training for everyone, hands-on sessions per team, automation skills for power users; a champion network

30–90

8

Success criteria and readout

Adoption and business results against the baseline; the sponsor's decision

60–90

Days 0 to 30: how do you lay the foundations?

The first 30 days decide whether the next 60 run smoothly. Most of this work is invisible to end users, and that's the point. When people get access, it should just work, safely.

  • Name the owners first (by day 14). An executive sponsor, a budget owner and admin owners, in writing. Agree the escalation path: what gets escalated, to whom, and by when.

  • Set up identity properly. Decide on one Claude organisation or several. Connect single sign-on and automatic provisioning from your directory, so access follows people's roles and ends when they leave.

  • Close the security review on evidence. Map data flows, connector permissions and retention settings, then give your security team the evidence they need to sign off. Don't rely on assurances.

  • Decide who can build what. Choose which connectors are approved, and who may create and publish skills and plugins. These are the controls that matter as Claude moves from chat into real workflows. For apps Claude can act inside, see who should approve what Claude does inside your apps.

  • Put spend caps in layers. Set limits at organisation, team and user level, and decide who approves an overage, so cost never becomes the reason a rollout stalls. We cover this in who owns the Claude budget once every team is using it.

  • Record a baseline. Measure how the target work happens today: time per task, volumes, quality, satisfaction. Without a day-0 baseline, day 90 becomes an argument about opinions.

  • Choose the first wave. We typically recommend a few whole teams rather than scattered individuals, with at least one team under the sponsoring executive. Whole teams change how work flows; individuals only change their own tasks.

Free download: the Claude 90-Day Rollout Planner. Checklists for every workstream, sign-off for the day 30, 60 and 90 gates, a baseline and adoption tracker, and a readout template. Get the planner →

Days 30 to 60: how do you drive real adoption?

Wave one opens at day 30. From here, the work is about people.

  • Train in layers.

  • Everyone: AI fluency, covering what Claude is good at, where it isn't, and how to check its work.

  • Each team: hands-on sessions built around the tools and tasks that team actually uses.

  • Power users: automation, building skills and connecting Claude to workflows.

  • Build a champion network. Champions are respected colleagues in each team, not just enthusiasts. They answer questions, share what works, and turn proven workflows into shared skills that everyone can reuse. Our guide to deploying Claude Skills at scale explains how.

  • Measure weekly. The core measure is weekly active users over assigned seats. Alongside it, track how many people work beyond simple chat and one work metric per team. Agree your milestones before wave one starts.

  • Act on quiet teams fast. When a team falls behind, find out why within days. The cause might be the wrong use case, missing access, unclear permission or a manager who isn't on board. Fix it within two weeks.

  • Expect a dip. Usage often rises at launch, dips as novelty wears off, then recovers as people build real habits. Plan for it, and don't panic at it.

Days 60 to 90: how do you prove value and decide?

The day-90 readout is a business decision, not a demo.

  • Show value against the baseline. Lead with the measure that is furthest behind. Credibility comes from honesty. See moving beyond pilots to real ROI for how to frame value.

  • Show adoption and spend by week, including the dip and the recovery.

  • Let the owners tell the wins. Three real examples, told by the people who achieved them, persuade more than any chart.

  • Have the sponsor present. A readout delivered by a vendor or partner reads like a sales document. The sponsor owns the result.

  • Make one decision. Scale, extend, adjust or stop, with a next action, an owner and a date. Agree up front what happens if the answer is no.

Pre-brief the decision-makers a week before. Nobody should see the numbers for the first time in the room.

What does a 90-day rollout mean for leaders, data, security and people?

For leaders

Claude stops being an IT project and becomes a leadership commitment. The sponsor's job is to remove blockers, be visibly involved (one of the first-wave teams should be their own) and make a clear decision at day 90. Anthropic's guide is direct on this: success depends on a C-suite sponsor, a cross-functional steering group and champions at every level.

For the organisation

A 90-day plan creates one shared calendar for IT, security, HR, finance and the business. It also creates a repeatable pattern. Once the first wave is proven, each new team or region follows the same gates. Over time, a simple map of which functions are at which stage becomes your roadmap for scaling Claude across the enterprise. Build a monthly release review into it too, because new Claude features arrive fast and some switch on by default. Claude Meetings, Sheets, Whiteboards and Data is a recent example.

For data

Claude is only as useful as the context it can reach, and only as safe as the controls around that context. The foundations phase decides:

  • which connectors are approved

  • what data Claude can access

  • how long conversations are kept

  • who can see usage reporting

Decide these on purpose, with your data owners, not by default.

For security

Security moves from "is this tool safe?" to "is this configuration safe for our people and data?" Single sign-on, automatic provisioning, connector permissions, retention, spend caps and monitoring are all settled before wave one. Security sign-off rests on evidence, not assurances. Bringing security in early pays off, as we explain in why security teams must go first. Our Claude governance work covers each control.

For the people who use Claude, most of all

Every gate in this plan is really a question about people. Do they have access that works? Do they know how to use Claude well? Do they feel safe trying it? Does their manager back them? Is their work getting better, not just faster?

  • Psychological safety. People need permission to experiment and to say when Claude gets something wrong. Champions and managers set that tone.

  • Relevance. Generic training doesn't change habits. Hands-on sessions built on each team's real tasks do.

  • Trust. People trust Claude more when they know what it can and can't access, and that their data is handled properly. Explain the controls; don't just enforce them.

  • Recognition. At day 90, the people who achieved the wins tell their own stories. That builds pride and pulls others in.

  • Workload. Time saved should go into better work, learning or recovery, not just more output. Ask people what they'd do with the time.

  • Choice. A "stop" or "adjust" decision for a team isn't a failure. It respects that some work isn't a good fit yet.

Regular AI use is still the exception for most workforces. Rollouts succeed when people experience Claude as something that helps them, not something done to them. We explore this further in human-led AI adoption: lessons from Deloitte's 2026 report.

How do you measure a successful Claude rollout?

Measure

What it tells you

When

Weekly active users over assigned seats

Whether people are using Claude regularly

Weekly from day 30

Share of users working beyond chat

Whether use is deepening (projects, connectors, skills, automation)

Weekly from day 30

One work metric per team

Whether the work itself changed: time, volume, quality

Against the day-0 baseline

User satisfaction

Whether people find it helpful

Day 45 and day 85

Spend against caps

Whether cost is predictable

Weekly

Agree the milestones and the denominator before wave one, and state them in the readout. Anthropic's guide recommends tracking adoption, efficiency, quality and satisfaction weekly and reviewing them monthly.

Why use a Claude partner for your rollout?

A partner turns 90 days of working out how into 90 days of getting value. You can run a Claude rollout yourself. A certified partner makes it faster, safer and more likely to scale.

Benefit

What it means in practice

Speed to value

A proven 90-day plan, checklists and templates from day one, so foundations close on time and wave one opens at day 30

Lower risk

Security, identity, retention, connector and spend controls designed from experience, with evidence ready for your security review

Higher adoption

Training in layers, a champion network and fast help for quiet teams. This is where most rollouts succeed or stall

Credible results

A baseline from day 0 and a readout your sponsor can stand behind, so the scale decision is based on evidence

Competitive advantage

Getting to production use months earlier compounds. Teams build skills, shared workflows and confidence while competitors are still piloting

Access to Anthropic

As a certified partner in Anthropic's Claude Partner Network, we work alongside Anthropic's teams and best practice

One partner across your stack

We connect Claude to the tools your people already use, including Asana, Miro, Canva, Glean and Google

Talk it through with a Claude partner. Book a free 45-minute 90-Day Claude Rollout Planning Session. We'll review where you are, sketch your first 30 days and flag the risks to fix before wave one. Book a planning session →

When you might not need a partner: if you have an experienced internal AI team, a strong change function and a small, single-team rollout, you can follow the same plan yourself. Partners add most value in multi-team, multi-region or regulated rollouts.

How does Generation Digital run a Claude rollout?

We're a human and business-led AI transformation consultancy. We run each phase of the plan with you:

We work across the UK, US and Canada, with local teams for US Claude consulting and Canadian Claude consulting. UK public sector buyers can buy Claude and our AI Transformation Services through G-Cloud 15. For the full framework behind this approach, download Anthropic's Enterprise AI Transformation Guide.

Ready to plan yours?

Common mistakes in Claude rollouts

  • Handing out licences before the foundations are done. Access without identity, permissions and training creates risk and disappointment.

  • No named sponsor. Without one person accountable, decisions drift and the day-90 gate has no owner.

  • Skipping the baseline. You can't prove value against a starting point you never measured.

  • Choosing volunteers, not teams. Scattered enthusiasts don't change how work flows.

  • Counting logins, not work. Measure what changed in the work, not just who opened the app.

  • Ignoring quiet teams. A team that's quiet at day 45 is usually missing something fixable.

  • Letting the vendor present the results. The sponsor's readout carries weight; a vendor's reads as a pitch.

FAQs

How long does an enterprise Claude rollout take?

A first enterprise Claude rollout typically takes about 90 days to reach a scale decision. It runs in three phases: laying the foundations (days 0 to 30), activating a first wave of teams (days 30 to 60), and proving value and deciding (days 60 to 90). Wider rollout then follows in waves.

What needs to be in place before users get Claude?

Before the first wave, settle identity and single sign-on, automatic provisioning, the security review, roles and permissions, approved connectors, data retention and spend caps. Also name an executive sponsor, a budget owner and admin owners in writing, and record a baseline of how the target work happens today.

How many people should be in the first wave?

Start with a few whole teams rather than scattered individuals, including one team under the sponsoring executive. Whole teams show how Claude changes the way work flows between people. Most organisations then expand in waves after the day-90 decision.

How do you measure Claude adoption?

The core measure is weekly active users over assigned seats. Pair it with the share of users working beyond simple chat, one work metric per team measured against a day-0 baseline, and user satisfaction. Agree the milestones before the first wave starts.

Who should present the day-90 readout?

The executive sponsor should present it. A readout delivered by a vendor or partner can read like a sales pitch. The sponsor shows value against the baseline, adoption by week and wins told by their owners, then makes one decision: scale, extend, adjust or stop.

Why use a Claude partner for a rollout?

A certified Claude partner brings a proven plan, governance patterns and a change programme, so you reach value faster and with less risk. Partners add most value in multi-team, multi-region or regulated rollouts, where security, adoption and measurement all need to come together.

How does a 90-day rollout affect employees?

Employees get access that works, training built on their real tasks, champions to help them, and a voice in the results. The plan protects them by settling data and security controls first, and recognises them by having the people who achieved wins tell their own stories at day 90.

Is there a template for a Claude rollout plan?

Yes. Generation Digital's free Claude 90-Day Rollout Planner includes checklists for each phase, sign-off criteria for the day 30, 60 and 90 gates, an owners template, a day-0 baseline, a weekly adoption tracker, a readout outline and a people pulse survey, as a PDF and an editable Excel workbook.

Who is Generation Digital?

Generation Digital is a human and business-led AI transformation consultancy and a certified partner in Anthropic's Claude Partner Network. We help enterprises in the UK, US and Canada roll out Claude, with strategy, governance, training and adoption support.

Sources

  • Anthropic, The Enterprise AI Transformation Guide (2025), co-branded and shared by Generation Digital

  • Generation Digital rollout methodology, informed by Anthropic deployment best practice

Put this into practice

Rolling out Claude or AI across your organisation?

Generation Digital is a certified partner in Anthropic’s Claude Partner Network. Talk to one of our Claude specialists about rollout, training and adoption.

Get weekly AI news and advice delivered to your inbox

By subscribing you consent to Generation Digital storing and processing your details in line with our privacy policy. You can read the full policy at gend.co/privacy.