The 90-Day Rollout

No. Nothing in the Rollout is a fixed module. The foundation arc exists because it usually stops people hearing the basics for the first time inside their own department's session, but if your team is already past that, the intakes will say so and we spend the time somewhere better. The number of sessions, which functions get their own, and how deep each goes are all set after the intakes.

No two have been. The nine workstreams are what the engagement can contain, not a checklist we run in order. A lighter, scoped-down version is available, and we will tell you plainly what comes out of it rather than quietly delivering less.

The intake. Team size and the number of functional groups in scope drive how many role-specific sessions and builds the engagement needs, and both come out of the department-head intakes before anything is quoted. It is confirmed on a scoping call, never off a menu.

Not to run the engagement. Sessions can be delivered without access to client material, and on our first enterprise Rollout they were - the firm did its own iteration on its own data afterward. If you want us working inside your documents, that is an NDA conversation and a separate scope.

Your team keeps the private portal for 90 days, including every session recording, so people who join around the engagement can catch up. Treat it as a head start rather than training that runs itself - Claude moves fast enough that recordings age. The Skills built during the engagement stay in your environment and are yours, with no time limit. Continuation work is scoped separately, and only if you want it.

B2B teams of roughly 5–50+ people already paying for Claude Teams or Enterprise with low or uneven adoption - especially leadership teams who need a real story for the next board, LP, or investor conversation, and regulated or compliance-sensitive organizations (PE, family offices, capital management, healthcare, insurance, legal) where data governance isn't optional. If your first AI workshop did nothing, this is the offer that installs the operating discipline instead of just raising the floor.

A workshop raises the floor - it teaches your team Claude basics and ends. The Rollout installs the operating layer: training across every department, three workflows built into your environment, a governance layer, and a measurable before/after adoption dashboard. A workshop is the place to start if you just want training. The Rollout is for teams who want the whole thing installed, with proof at the end. Start with the Workshop Series if you're not there yet.

We build them. Your three highest-ROI workflows are turned into Claude-native Projects + Skills and deployed into your environment where we have a provisioned seat - not demoed, integrated. For any workflow that falls outside Claude's native capability, you get a written plan instead. This is the one engagement where the builds are done for you, not just designed with you.

A written data-security protocol is part of the deliverables, and Projects + Skills are deployed into your AI portal or shared workspace with governance baked into the patterns themselves. We build for regulated environments. Formal regulatory review, LP communications counsel, and legal opinions on data handling stay with your existing advisors - we install the operating discipline, not the legal sign-off.

We capture a baseline before any training - platform telemetry plus a per-person enablement self-rating - and re-measure at Day 60 across three axes: adoption, enablement, and ROI. You get a delta dashboard and a wrap-up brief built to drop straight into a board or LP readout. Note: Claude's usage analytics run on a rolling ~90-day window (owner-exported on Team, or via the Analytics API on Enterprise, which holds data from Jan 1, 2026), so the baseline has to be captured before Session 01.

Async support runs across the engagement and for 14 days after. Additional automations from the roadmap can be scoped as separate workstreams, and PE firms or holding companies often roll the same shape out across portfolio companies. Continued advisory beyond the engagement can be scoped separately.

You keep everything. The roadmap, the dashboard, the workflow builds, the governance docs, the session recordings - none of it lives with us. It is built into your environment and handed over at Day 60. The 14-day async window after handoff is for questions while you are running it independently for the first time.

From $28,500, shaped from the intake - the 60-day Starter tier. The 90-day runs from $42,500. Team size and the number of functional groups in scope set where it lands, confirmed on the scoping call after the intake, never off a menu. In-person delivery and additional department tracks or workflow builds are available as add-ons. By comparison, a custom corporate AI program from a name-brand consultancy runs $150,000–$250,000+, and you get a deck, not built workflows.

A few things stay outside the scope of the engagement. Formal regulatory review, LP communications counsel, and legal opinions on data handling stay with your existing advisors - we install the operating discipline, not the legal sign-off. Full custom platform development (a bespoke internal UI built on top of Claude) is a separate engagement. Ongoing support beyond the 14-day async window is scoped separately. And more than the named workflow builds (3–5, or 5–7 on the 90-day) plus the roadmap - additional workstreams are scoped separately on the scoping call.

The Custom Program (From $9,500) trains your team and ships a handful of working builds over four to six weeks - the right size when nobody is asking you to prove adoption with a number. The Rollout is the full installation: a written roadmap, training across every department, the builds deployed and running, the governance, and the measurable adoption story for your next leadership / board / LP audience. The Rollout is what teams choose when they need the operating layer installed, not the menu sampled.

Two commitments, and deliberately not a guarantee. If the named workflow builds aren’t built, the delta report isn’t delivered, or the sessions in scope aren’t completed, we continue on the missed items at no additional cost, capped at 30 additional days - provided the materials, system access and attendance arrive on the schedule in the SOW, since those are the things we can’t do for you. And separately: you get the baseline, the mid-point checkpoint and the final delta report regardless of what they show. We don’t promise a specific business outcome, an hours-saved figure, or an adoption percentage, because nobody honestly can - what we commit to is completing the scope and handing you real numbers either way.

Claude occasionally has outages or degraded performance. If Claude is unavailable on a scheduled session date, we reschedule that session to the next mutually available time at no additional cost - it does not count against any reschedule limit. Anthropic occasionally suspends or restricts accounts for reasons that are not always clear or contestable. Elevate Online does not control Anthropic’s policies and is not responsible for account actions. If account issues prevent a session from running, we work with you to reschedule or adjust scope in good faith.