Claude Code rollout
Every engineer shipping with Claude Code.
One managed setup for the whole team, trained on your own repo, with review built in and usage measured.
- About 4 weeks
- to live on real traffic
- Founder-led
- no handoff to juniors
- Fixed price
- agreed before work starts
| Role | Team | Policy | Status |
|---|
| BEBackend engineer | Payments | Standard | InvitedActive |
| MLMobile lead | Mobile | Standard | Active |
| DEData engineer | Data | Standard | Active |
| SEStaff engineer | Platform | Extended | Active |
| QAQA engineer | Payments | Standard | Active |
| FEFrontend engineer | Web | Standard | Active |
| SRSRE | Platform | Extended | Active |
The seats are bought and a few engineers rely on them
The rest of the team never gets past the first week, because each person set it up alone and nobody wrote down the rules.
of developers distrust the accuracy of AI tools.
Sourcesurvey.stackoverflow.co
of developers spend more time fixing AI code that is almost right.
Sourcestackoverflow.blog
of developers have little or no trust in AI-generated code.
Sourcecloud.google.com
Every engineer works from one setup, and you see what it changes.
| What changes | Without it | With it |
|---|---|---|
| Setup | Each engineer set it up alone. | One managed setup on every seat. |
| Rules | Nobody wrote what agents may touch. | Written rules with a named owner. |
| Usage | Nobody knows who uses it, or for what. | Usage and cost measured per team. |
What we build
What changes for your teams. We pick the tools to fit the systems you already run.
| Role | Team | Policy | Status |
|---|
| BEBackend engineer | Payments | Standard | InvitedActive |
| MLMobile lead | Mobile | Standard | Active |
| DEData engineer | Data | Standard | Active |
| SEStaff engineer | Platform | Extended | Active |
| QAQA engineer | Payments | Standard | Active |
| FEFrontend engineer | Web | Standard | Active |
| SRSRE | Platform | Extended | Active |
| Role | Team | Policy | Status |
|---|
| BEBackend engineer | Payments | Standard | InvitedActive |
| MLMobile lead | Mobile | Standard | Active |
| DEData engineer | Data | Standard | Active |
| SEStaff engineer | Platform | Extended | Active |
| QAQA engineer | Payments | Standard | Active |
| FEFrontend engineer | Web | Standard | Active |
| SRSRE | Platform | Extended | Active |
Measured against where you started
What changes at a company like Acme Inc
Illustrative figures, not a client result. Your own baseline is taken in the first week.
How others built it
Another company built the same kind of system and wrote publicly about how it went.
- SalesforceHow Salesforce Engineering became truly agentic
What they learned
Agents pay off when a whole engineering org runs them one shared way, not seat by seat.
In April 2026, work items completed per developer were up 50.8% on April 2025.
Everything runs in your cloud, and stays yours
You own the config, the tests and the runbooks, so you can swap any part later.
Written rules for what agents may touch, with a named owner.
| Role | Team | Policy | Status |
|---|
| BEBackend engineer | Payments | Standard | InvitedActive |
| MLMobile lead | Mobile | Standard | Active |
| DEData engineer | Data | Standard | Active |
| SEStaff engineer | Platform | Extended | Active |
| QAQA engineer | Payments | Standard | Active |
| FEFrontend engineer | Web | Standard | Active |
| SRSRE | Platform | Extended | Active |
Training on your own code, and a report on what changed since the start.
Departments and whole engineering orgs take 60 or 90 days, quoted after the call.
Typical building blocks: Server-managed settings, a private plugin marketplace, managed locks, Claude Code Review, OTel usage metrics, and model traffic through the LLM gateway.
Alternatives: MDM managed settings plus claude-code-action, for teams on Bedrock or Vertex, or teams that cannot reach the hosted service.
Live in about 4 weeks
The work happens in your cloud, with the people who will own it.
- Week 1Take a baseline before anything changes, then push the managed setup.
- Weeks 2 to 3Train the team on its own code and pair on real tickets.
- Week 4Report against the baseline and hand over the playbook.
- After thatRunning on real traffic
Every engineer on one managed setup.
Before we start
- Seats for the team, or a plan to buy them.
- Admin access to the repos and to the managed settings.
- An engineering lead who owns the rules, and about 4 hours a week from each engineer.
Is this the right first build?
It fits when
- Every engineer’s setup is different.
- Nobody wrote what agents may touch.
- A team on your side will own it after we leave.
It does not fit when
- You want a hosted tool picked and resold to you.
- You want a strategy deck in place of working software.
- Nobody on your side can own it after we leave.
What’s included and what isn’t
Included
- One team of up to 10 engineers.
- One managed setup with written rules, in up to 3 repos.
- Up to 4 training sessions on your own code.
- A measure of where you start, and a report at the end on what changed.
Not included
- Seats and licences, which you buy directly.
- Departments and whole engineering orgs, quoted after the call.
- Changes to your pipeline beyond the review step.
About 4 weeks. You get a price range before the call and one fixed number after it. That number is the invoice.
- If the work takes longer than we planned, we absorb the cost.
- You pay 50% at the start and 50% at acceptance. Builds of 6 weeks or more pay 40% at the start, 30% at the midpoint and 30% at acceptance.
- If a build starts within 60 days of your Audit results, the full Audit fee comes off its price.
- We start three new projects a quarter, so your start date depends on when you book.
Questions teams ask before they book
What is a Claude Code rollout?
We take a team from scattered seats, each engineer set up their own way, to one managed Claude Code setup with written rules and training on your own code.
Which settings and tools do you use?
We pick the one that fits the systems you already run. You own the config, the tests and the runbooks, so you can swap any part later. Most often server-managed settings, a private plugin marketplace, Claude Code Review and OTel metrics; MDM managed settings and claude-code-action for teams on Bedrock or Vertex.
How long does a rollout take?
About 4 weeks for one team of up to ten engineers. Sixty or 90 days when it spreads across a department or the whole engineering org.
Do we need Claude Enterprise first?
No. We work with the seats you have and tell you on the call if a plan change would help.
How do we know it worked?
We take a baseline at the start and report against it at the end, including where it fell short.
What stays with us?
The managed setup, the rules with a named owner, a playbook the next team starts from and the final report.
Claude Code rollout, running in your cloud in about 4 weeks.
Every engineer on one managed setup. You own the config, the tests and the runbooks.