The 30-day Claude Code rolloutFor CTOs and engineering leads
Your whole team on Claude Code. One safe workflow.
For teams of 10 to 100 engineers. In 30 days, every engineer uses Claude Code through one shared, safe workflow. You get numbers to show leadership.
First shared workflow live in week 1. About 2 hours a week from you.
$ tree --shared CLAUDE.md # project instructions .claude/skills/ # team skills .claude/hooks/ # checks on each change .claude/settings.json # permission rules ci/guardrails.yml # enforced in CI $ ci guardrails pass least-privilege permissions pass no production secrets pass hooks run on every PR merged 5 agent-assisted PRs (eng 07)
The problem
Ten engineers. Ten ways to use an agent.
Without a shared setup, each engineer writes their own prompts, sets their own permissions and keeps their own habits. Nobody can show leadership what changed. This rollout gives the team one workflow, with guardrails in CI and a report on day 30.
Private prompts and habits
Shared project instructions, skills and hooks in the repo.
Permissions left to each engineer
Permission and security guardrails, enforced in CI.
“It feels faster”
Baseline delivery numbers on day 1. A trend report on day 30.
The 30 days
Live in week 1. Rolled out by day 30.
We work in your repo, on your real tickets. You give about 2 hours a week. We do not promise a speed gain inside 30 days. We measure, and we show you the trend.
Week 1
Baseline and setup
- Baseline delivery numbers
- Project instructions, skills and hooks
- Guardrails enforced in CI
- First shared workflow live
Weeks 2 to 3
Pairing on live tickets
- Pair with engineers on real work
- Fix the workflow where it fails
- Bring more engineers in
Week 4
The team playbook
- A written playbook for the team
- Every engineer on the shared workflow
Day 30
The report
- Baseline and trend, ready for leadership
- What to do next
What you get
Everything stays in your repo.
When we leave, the workflow, the guardrails and the playbook stay with your team.
- Baseline delivery numbers before anything changes.
- Repo setup: project instructions, skills and hooks.
- Permission and security guardrails, enforced in CI.
- Pairing on live tickets with your engineers.
- A team playbook the next hire can follow.
- A day-30 report of baseline and trend.
Security
The questions you will ask first.
We cover these before we touch your code.
Confidentiality
We sign an NDA.
Signed before any repo access.
Repo access
Least-privilege access only.
We get the access the work needs, and nothing more.
Your data
We check the data-retention terms of your Claude plan.
You know what is kept, and for how long, before the team starts.
Secrets
No production secrets.
The workflow does not use them, and the guardrails help keep them out.
The guarantee
A number you can check on day 30.
By day 30
At least 80% of your engineers have merged at least 5 agent-assisted pull requests through the shared workflow.
If not, we give up to 30 more days of support free.
- Condition
- The engineering lead's 2 hours a week happened.
- Not promised
- A speed gain inside 30 days. We report the trend honestly.
Price
£9,000
Fixed, per team of up to 10 engineers.
See everything included ↑- Baseline delivery numbersIncluded
- Repo setup and CI guardrailsIncluded
- Pairing on live ticketsIncluded
- Team playbookIncluded
- Day-30 reportIncluded
Hashin Panakkaparambil
Founder and engineer
Who does the work
An engineer who has changed how teams work.
Hashin Panakkaparambil has been a software engineer since 2005. He has led teams through new practices: domain-driven design, clean architecture, and monolith to services. He runs a multi-agent Claude Code setup every day. He works in your repo, on real tickets.
Hashin's engineering work includes
Travelodge. Lead Engineer on the booking platform upgrade, handling millions of transactions. Led the team through new practices.
LexisNexis. Moved insurance data processing to cloud-native AWS. Led the team through new practices.
Specsavers. Moved monolithic systems to microservices on AWS, with CI/CD. Led the team through new practices.
Paymentsense. Payment integrations across e-commerce platforms.
- Super Payments
Super Payments. Payment platform upgrade and API integration.
Sainsbury's, WorldFirst, AOL. Trained engineering teams in domain-driven design and clean architecture.
Questions
Straight answers.
If your question is not here, ask it on the call.
Will you sign an NDA?
Yes. We sign your NDA before we see any code.
What happens to our code and data?
That depends on the data-retention terms of your Claude plan. We read those terms with you before the team starts, so you know what is kept and for how long. Repo access is least-privilege, and no production secrets go into the workflow.
Who pays for the Claude seats?
You do. Seats and usage stay on your own Claude plan and account. The price on this page covers the rollout only.
We have more than 10 engineers. How does that work?
The price is £9,000 per team of up to 10 engineers. A larger group is more than one team. We agree the order of the teams on the call.
Do you promise a speed gain?
No. We do not promise a speed gain inside 30 days. We measure a baseline on day 1 and report the trend on day 30. The guarantee is about adoption: at least 80% of engineers merging at least 5 agent-assisted pull requests through the shared workflow.
How much time does it take from me?
About 2 hours a week from the engineering lead. The guarantee depends on those hours happening.
One workflow for the whole team, in 30 days.
Book a call. Tell us about your team, your repo and your Claude plan. We will tell you plainly if the rollout fits.