For CTO and VP Engineering
Claude Code Pod
Your engineers on Claude Code under managed settings, with before-and-after numbers, in six weeks.
Installs the Code module of the Mode2 Foundation
- One team
- $50,000
- Two teams
- $90,000
- First two clients, reference price
- $30,000
- Duration
- 6 weeks
Why you're here
Your engineers already use Claude Code, and many of them pay for it on personal cards. You cannot see who uses it, govern what it can touch, or measure whether it ships more work. Security wants settings you control. Finance wants one bill.
What you get
- Installs the Code module (about 160 engineer hours for one team, 260 for two, falling with each release)
- Your engineering teams on Claude Code with managed settings
- Permissions set for your repos and tools
- Review gates on the work Claude Code produces
- A test harness the work runs against
- Measured by Anthropic's analytics: sessions, lines, commits and PRs
- Measured by your Git and tracker: cycle time and defect rate, before and after
How the weeks run
- Week 1
- Baseline from your Git and tracker; cycle time and defect rate recorded
- Current Claude Code use mapped, including personal accounts
- Week 2
- Managed settings and permissions from the admin console
- Endpoint settings through your MDM where you need them
- Week 3
- Review gates and the test harness wired into your repos
- Week 4
- Working sessions with each engineer on your own backlog
- Week 5
- Settings and gates tuned on what weeks 3 and 4 showed
- Week 6
- The same measures taken again; before-and-after report to your sponsor
- Settings handed over with how to change them
Price and terms
| One team | $50,000 |
|---|---|
| Two teams | $90,000 |
| First two clients, reference price | $30,000 |
| Duration | 6 weeks |
| Foundation module | Installs the Code module |
What moves the price
- About 160 engineer hours for one team, 260 for two, falling with each release.
- The first two clients pay the reference price in exchange for a named public case study with before-and-after metrics.
What we need from you
- Owner or admin access to your Claude Team or Enterprise console
- Read access to your Git host and issue tracker
- An engineering leader who sponsors the Pod
- The named team, with time from each engineer for working sessions
What happens after
Code Ops keeps the Code module, the settings and the numbers current each month. Agent Build takes the next workflow to production.
Questions buyers ask on the first call
Our engineers are on personal plans. Where do we start?
Server-managed settings run from the admin console on Team and Enterprise. Moving the team onto one of those plans is the first thing we plan with you in week 1.
What exactly do you measure?
Sessions, lines added and removed, commits and PRs from Anthropic's Claude Code analytics. Cycle time and defect rate from your own Git and tracker. We record both in week 1 and again in week 6.
What does the reference price ask of us?
A named public case study with before-and-after metrics. It is open to the first two clients only.
Can we run two teams at once?
Yes. Two teams is one Pod at the two-team price, about 260 engineer hours over the same six weeks.
Book a 30-minute scoping call about the Claude Code Pod.
Thirty minutes on what you need, which offer fits, and the fixed price for it.