The rollout
Roll Claude out to every team, not just the keen ones.
You bought the licences. In 30 or 60 days we turn them into workflows your teams actually run, with the setup and controls your IT lead signs off, and we measure what changes.
Book a 30-minute fit call01 Sound familiar
Three people use it daily. Everyone else tried it once.
Nobody owns it, so nobody is sure what is allowed.
Leadership asks what we are getting for it. There is no answer.
A rollout fixes all three: an owner, a policy, and workflows with a number attached.
02 What we roll out
Your work, not generic demos.
03 How it runs
30 or 60 days, with IT and the teams moving together.
Two tracks run side by side: the setup and controls your IT lead signs off, and the teams learning on their own work. We measure a baseline before anything changes and measure again at each stop.
- Day 0Baseline measured
- Day 3030-Day Team Launch ends here
- MapFirst week
- ProveTo Day 30
- ScaleDay 30 to Day 60
Day 60: Company Rollout ends here
- Day 0Access and adminWorkspace, admin roles and who can use what.
- By Day 30Connectors and data rulesThe tools Claude can reach and the rules for which data goes where, agreed with your IT lead.
- By Day 60HandoverAdmin training, a usage review cadence and a runbook your team owns.
- Day 0BaselineHow long the chosen work takes today, and who uses Claude for it.
- By Day 30First team liveTwo workflows running on real work, measured against the baseline.
- By Day 60Every team trainedTraining for each team that will use it, measured again at the end.
Map
We review your Claude setup, your team's fluency, your data policies and the tools your workflows depend on, then pick the workflows worth doing first.
You keep: a rollout plan and a use policy.
Prove
One team builds two real workflows, such as proposals, inquiry follow-up or regular reports, and we measure them against the baseline.
You keep: working workflows and a measured result.
Scale
Each team learns the workflows and tools relevant to its work, and an internal owner takes over running it.
You keep: trained teams, an owner and a number for leadership.
04 What's included
Everything a rollout needs, in one engagement.
- A review of your Claude setup, data policies and tools
- A use policy and a named internal owner
- Workspace, admin and connector setup, agreed with your IT lead
- Workflows built on your team's real work
- Hands-on training for each team, in English or French
- A baseline at Day 0 and a measure at each stop
- A runbook and an admin handover
05 Client story
He understood it in the first meeting.
A legal technology company came to us already deep in Claude. They build on Anthropic's models, so their engineers were fluent. The founder's question was different: what about everyone else?
He saw immediately that Claude was not an engineering tool. It was a way for sales, marketing, and operations to compete at a level a company that size normally cannot, and to give more back to the customers they serve. We set the foundation, proved value on real work, then trained the whole company across two cities.
Today people across the company delegate to Claude as part of the job. They are more ambitious about what they take on, and the founder has a team that runs on Claude rather than a handful of engineers who do.
06 Engagements
Start with one team, then the rest.
- A first group, any team size
Fluency Workshops
One to four sessionsThe fastest start: hands-on sessions on your own work.
Fixed price, quoted in CAD - One team, up to about 15 people
30-Day Team Launch
30 daysOne team, two real workflows, measured against a baseline.
Setup is reviewed with your IT lead before the team starts.
Fixed price, quoted in CAD - Several teams, up to the whole company on Claude Team
Company Rollout
60 days / Core engagementA shared practice your teams can run without us.
Admin setup, connectors and data rules are agreed with your IT lead.
Fixed price, quoted in CAD - 100+ people on Claude for Enterprise
Enterprise Rollout
Scoped on the callEnterprise controls in place, then rolled out team by team.
Your IT and security leads sign off on the configuration.
Enterprise deploymentsScoped and quoted after the call, in CAD
Every engagement includes
- A principal on every engagement, from the first call
- A fixed price, in CAD
- Delivery in English or French
- Work on your real tasks, not generic demos
- A measure before and after
What moves the price
- Number of people and teams
- Number of workflows
- On-site days
- French delivery
07 Questions
What leaders ask about a rollout.
Is it 30 days or 60 days?
One team is a 30-Day Team Launch. Several teams, up to the whole company on Claude Team, is a 60-day Company Rollout. Over 100 people on Claude for Enterprise, we scope it on the call.
What does our IT lead need to do?
Review the setup, approve the connectors and agree the data rules with us. On Claude for Enterprise they also sign off single sign-on and provisioning.
Our staff are not technical. Will this work?
Yes. Most of our training time goes to people who do not write code. They learn on their own tasks, with the files and tools they use every day.
We have not bought Claude yet. Is that too early?
Not necessarily. Most clients have already chosen Claude. If you are still deciding, a Fluency Workshop lets your team try it on real work first.
How do we show leadership it worked?
We measure a baseline before the first workflow is built and measure again after. You get a before and after for each workflow, in terms your leadership already tracks.
Can you deliver in French?
Yes. Training and materials can be delivered in English or French.
08 Book
Which team should go first?
30 minutes with a principal. A written plan after the call, whether or not you work with us.
- Bring the team and the work you have in mind.
- We tell you honestly whether there is a fit.
- A written plan follows the call.
Prefer email? Write to info@antfluent.com
Pick a time
Open the calendar in a new tab