Claude Code · team setup
Whether your developers are just starting with AI or already use it on their own, I build a shared setup in your repo — instructions, skills, hooks and guardrails — so coding agents work the same way for everyone, and safely.
The problem
Everyone tries a different tool and a different prompt. Nobody has decided what the agent may change, what it may read, or who checks its work.
It works well for some and badly for others. The good instructions live in one person's config, secrets sit one prompt away, and review cannot keep up with what the agents produce.
What a harness is
A harness decides what the agent knows, what it may do, and what stops it. It lives in your repository, next to the code, so it is the same for every developer and every session — and it changes through review like the code does.
How your team builds, tests and reviews, written once and read by every agent at the start of every task.
Your recurring work — a release, a migration, a review — as tested steps the agent follows, not prompts people retype.
Checks that run before every tool call. Deleting data, rewriting history or pushing a secret is blocked before it happens.
Each task in its own clean checkout and branch, and nothing merges without a review round.
Services & pricing
Start with an assessment. The report it ends with is the fixed quote for the build.
Step 1
For: Teams deciding where to start.
100% upfront · credited if you order a build within 30 days
Step 2
For: Teams ready for one shared setup.
Fixed quote after the assessment · 50% at start, 50% at handover
Step 3
For: Teams that want the harness kept current.
Billed monthly in advance · unused time does not carry over
Prices excl. VAT. The assessment fee is credited if you order a build within 30 days.
How an engagement runs
I review the repository and how the team works with AI now.
The report ends with a fixed quote for the build.
Instructions, skills, hooks and guardrails, built and tested in your repository.
The team learns the setup on its own code.
New skills and updates as the models and the team change.
Invoices are due in 8 days. Prices excl. VAT. I take on work in the order it is confirmed, and tell you up front when I can start.
How I work
The numbers come from my own projects, with the date and method beside each one.
Measured on my own projects, Aug – Oct 2026. Method on the case study page.
About
I'm a software architect and backend tech lead with 15 years of building platforms and leading engineering teams of up to 13. Since coding agents became usable for real work, I have done my own development through them, on the setup this site describes, and I build the same kind of setup for other teams. I work remotely from Szeged, Hungary, in the EU time zone, and I take on a small number of teams at a time.
FAQ
No. If the team is just starting, the assessment covers which tool and plan fit you, and the build sets it up. The harness is built for Claude Code; if your team is set on another agent, tell me in the form and I'll say honestly whether I'm the right fit.
Yes, read access to the repository for the assessment, and write access to a branch for the build — everything I change arrives as pull requests your team reviews and merges. I don't need production systems, customer data or your secrets. Access is removed when the engagement ends, or kept for the Care Plan if you choose one.
I sign your NDA before the assessment starts. Keeping secrets away from the agent is part of every build: the harness limits what the agent can read, blocks it from printing or committing credentials, and scans outgoing code for secrets before it leaves the machine.
It depends on the repository and the team, and the assessment tells you. I work on a few engagements at a time, so I give you a start date before you order, not a promise I'd have to break.
The harness is yours: it lives in your repository and your team can change it like any other code. The Care Plan is optional — it is there if you want someone keeping it current as models and tools change.
Contact
A few questions by email first, then a short call if it's a fit. I reply within 2 business days.
Prefer email? [email protected]