Your whole team on Claude Code and Codex. One shared workflow.

For 10 to 100 engineers. We install one shared workflow, then train your people on real tickets. We also set up ChatGPT for teams that already live in it.

Book a free call See the 30 days

your-repo · shared workflow

$ 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

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.

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.

Install the setup. Then train the people.

We work in your repo, on your real tickets. You give about 2 hours a week.

1
Install
Week 1
- Baseline delivery numbers
- Project instructions, skills and hooks
- Guardrails enforced in CI
- First shared workflow live
2
Train
Weeks 2 to 3
- Pair with engineers on real work
- Fix the workflow where it fails
- Bring more engineers in
3
Playbook
Week 4
- A written playbook for the team
- Every engineer on the shared workflow
4
Report
Day 30
- Baseline and trend, ready for leadership
- What to do next

Week 1first shared workflow live.

2 hrsa week from the engineering lead.

30 daysto full rollout.

Everything stays in your repo.

Claude Code and Codex rollout

from£9,000

Per team of up to 10 engineers. When we leave, the workflow, the guardrails and the playbook stay with your team.

Book a free call

What you get

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.

We run our own business on it.

Read the full case

Our own system

The Agent OS

A shared memory, a task queue and agents that plan and do the daily work across sales, content and operations, on Claude Code and Codex. A free starter kit is public on GitHub.

See the starter kit

Hands-on. I work in your repo.

Hash

Founder, architect and engineer

Hand-built by Hash. You deal with me, not a sales team.

Hash on LinkedIn

An engineer who has changed how teams work.

I'm Hash. I've built software since 2005 and worked as an architect since 2007. I've led teams through new practices: domain-driven design, clean architecture, monolith to services, and moves to AWS. On larger programmes I've built the delivery team too, hiring and leading the engineers for Travelodge's move from on-premise to AWS. I run a fleet of AI coding agents every day, and I review every line they write. I work in your repo, on real tickets. I build and sell my own AI products, and I teach other builders to use Claude Code.

What we roll out

Claude Code
Codex
MCP
CI checks

It fits the stack you already run, such as TypeScript, Python and AWS. No rewrite and no new platform.

Companies we've delivered for

The booking platform behind millions of hotel stays, moved from in-house servers to AWS.Led the on-premise to AWS migration and the booking platform upgrade, and hired and led the delivery team.
Insurance data processing modernised, so it grows with demand without buying more servers.Moved it to cloud-native AWS as part of a wider digital transformation.
Teams release faster and more safely, and one change no longer breaks everything.Split the monolith into microservices on AWS with automated releases, and brought in agile practices and process automation.
Merchants take card payments on the shop platform they already use.Payment integrations across e-commerce platforms.
Super Payments
Shoppers save on every order, and Super earns on every sale.Built bank-transfer payments that skip card fees. The saving goes to shoppers as a reward, and Super earns a commission. I also set up the greenfield projects with automated releases, so the team shipped often and got client feedback fast.

Questions

Anything else, ask on the call.

Does this work with Codex?

Yes. We roll out the same shared workflow, guardrails and training for teams that use Codex.

Who works on my project? What if the work grows?

You always work with me, and I stay your single point of contact. When a project needs more hands, I bring in engineers I've vetted myself, the same way I've built delivery teams for large AWS programmes. I review every piece of work before it reaches you, so quality doesn't drop as the team grows.

Who pays for the Claude and Codex seats?

You do. Seats and usage stay on your own 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 from £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.

How will we see what changed?

We measure your delivery numbers on day 1. On day 30 we report the trend, so you see the change in your own data.

One workflow for the whole team, in 30 days.

Book a call. Tell us about your team, your repo and your plan. We will tell you plainly if the rollout fits.