The 60-Day Claude Rollout™
What happens, week by week.
A rollout from start to finish — the two intakes that shape it, the training series, the workflow builds running in parallel, and the measurement that bookends it. Toggle between the 60-day flagship and the 90-day extended option to see how the arc changes.
Looking at the offer itself? The 60/90-Day Rollout · The Claude Adoption Framework
The flagship. One forcing function in view — an LP meeting, a board update, a fiscal deadline. Three foundations, two build sessions, 3–5 workflow builds delivered.
~6–8 weeks · 5 sessions (3 × 60 foundations + 2 × 90 builds) · 3–5 workflow builds
Week 0
Pre-engagement
Two intakes + baselineThe two intakes, access, and baseline
Intake — two passes
A firmwide skills assessment goes to every staff member, and a department-head intake runs for each function. Together they shape the session sequence and name the workflows the builds will replace.
Setup & baseline
Claude access and data guardrails configured. Baseline engagement captured before any training runs — either screenshots of your Claude analytics page or a read-only seat in your workspace so we can pull the telemetry directly.
Deliverables
- Maturity baseline per function + recommended session sequence
- Access and data guardrails live
- Baseline snapshot — analytics screenshots or read-only seat
Week 1
Days 1–7
Strategy & scopingScope the work, name the builds
Strategy & scoping
Scoping call with leadership. Name the 3–5 workflow builds where the upside is, set the target metric per axis, and lock the session calendar. Draft the AI-use policy against your real document patterns.
Deliverables
- Scoping brief + 3–5 named build targets
- AI-use policy (draft)
- Locked session calendar
Week 2
Days 8–14
Foundation 01 · 60 minFoundation — Fundamentals
Session 01 (60 min, all staff)
Why Claude and how it works, the surfaces (Claude.ai, Cowork, Code), models and the context window, account tiers and security — framed to your team's world.
Build 1
Discovery and workflow mapping on the highest-value build, with the people who own that workflow today.
Deliverables
- Session recording + foundation reference guide
- Private team microsite live (resources, prompts, recordings)
- Build 1 workflow mapped
Week 3
Days 15–21
Foundation 02 · 60 minFoundation — Prompting
Session 02 (60 min, all staff)
Treating Claude like an intern, the BRIEF framework, iterating well, plus the data-security standard — what goes in Claude and what doesn't — demonstrated on real documents.
Build 1
Build 1 moves into construction as a Claude Project + Skill.
Deliverables
- Session recording + prompting / data-security quick reference
Week 4
Days 22–28
Foundation 03 · 60 minFoundation — The architecture + mid-rollout survey
Session 03 (60 min, all staff)
The layers — Global, Projects, Skills, Memory — where each thing lives, and writing Project Instructions. Foundations complete; the team is ready to build.
Builds 1 & 2
Build 1 delivered into the environment. Build 2 discovery begins.
Mid-rollout survey
A short engagement survey plus a usage read at the halfway mark, so we can course-correct before the build sessions.
Deliverables
- Build 1 live in your Claude environment
- Session recording + architecture reference (layers + instruction hierarchy)
- Mid-rollout survey results
Week 5
Days 29–38
Build session 01 · 90 minBuild a Skill — hands-on
Build session 01 (90 min, hands-on)
Your named workflows become live Claude Projects and Skills, built in the room and tuned to the functions where the upside is. Ninety minutes because building needs room to iterate.
Builds 2 & 3
Build 2 delivered. Build 3 moves into construction.
Deliverables
- Build 2 live in the environment
- Skills library consolidated on the microsite
Week 6
Days 39–52
Build session 02 · 90 minCowork, dashboards & champions — hands-on
Build session 02 (90 min, hands-on)
Turn the built Skills into scheduled, self-running workflows and a live dashboard. Your early adopters build alongside us and take ownership — the session that makes adoption self-sustaining.
Builds 3–5
Remaining builds delivered into the environment.
Deliverables
- Final builds live — your named workflows delivered
- Internal champions enabled to own ongoing curation
- Additional-automations blueprint (what to build next)
Weeks 7–8
~Day 60
Re-measure & reportProve it landed, then stay on call
Final survey + analytics export
A closing survey plus a screenshot or export of your Claude analytics page. We compute the delta against the Week-0 baseline and deliver the final measurement report — the readout that confirms the rollout moved adoption, enablement, and ROI, not just attendance.
Support
1:1 sessions as needed (up to an agreed cap), plus a 14-day async support window so questions don't stall once the room closes.
Deliverables — 60-Day Rollout complete
- Final measurement report — baseline → Day-60 delta across Adoption / Enablement / ROI
- Final survey + analytics screenshot or export
- 1:1 sessions as needed (up to the agreed cap)
- Prioritized roadmap of additional automations
- AI-use policy + data-security standard finalized
- 14-day async support window
Illustrative arc — the exact session sequence and the number of builds lock in the scoping call, shaped by the firmwide assessment and the department-head intakes. Platform-telemetry measurement requires Claude Enterprise; Team-tier teams are measured on the same axes via available admin metrics and in-session observation.
Want this mapped to your team?
The week-by-week is the shape. The scoping call turns it into your sequence — your departments, your workflows, your forcing function.