ForEach Partners
ForEach Partners
Book a call

Claude Code, set up for your engineering team

You have

A team of developers who started using Claude Code, Cursor or Codex. Each of them set it up their own way, and no one checks what the agents change.

You worry about

  • Every developer sets up the agents differently
  • No shared rules the agents follow
  • Agent changes nobody reviews
  • Keys and production access in agent sessions
  • Pull requests too big to read
  • Agents coding without a written spec
  • No one sure what is safe to automate

We give you

A senior engineer for your team's agents

Works on your code, with your developers

Step 1$3,000 fixed

Reviews your setup in 5 days: shared rules, review agents and a session with your team. The report is yours.

Step 2, if you continuefrom $6,000 per month

  • Keeps the rules and agents up to datePart of the monthly support. Each month at $6,000 includes 30 hours of the engineer's work on your code and 20 hours with you: calls, chat and your questions. If a month needs more, we tell you first, and you decide.
  • Adds a check before every merge
  • Checks every month what the agents missed

You get

  • One setup for the whole team
  • Agent changes checked before merge
  • The setup stays in your repository
Book a 30-minute callSee what we check
  • The 30-minute call is free
  • You can stop after the review
  • Nothing starts until you say yes

How it works

This is not a course and not a tool you install. A senior engineer sets up Claude Code, Cursor or Codex for your team on your own code: the shared rules and project instructions every developer's agent follows, review agents for security, tests and design, and what the agents may and may not touch.

It starts with a review. In five working days, the engineer reads your repository and how your team works with the agents, writes the shared setup into your repository, and goes through it with your developers in a two-hour session on your code. The price is fixed.

After that, we can keep the setup working every month: new rules as your code changes, a check before every merge, and a monthly look at what the agents missed. Everything stays in your repository and keeps working if you stop.

This is for you if

  • Your developers started using Claude Code, and each of them set it up differently.
  • You want the agents to follow your rules, not each developer's guess.
  • You need agent changes reviewed before they reach production.
  • You want a setup your team owns, not a course they forget.
  • Your security team asks what the agents can access.

What we do not do

These rules keep your app safe and keep it yours.

We do not take your code from you

Your app belongs to you. We help you keep all of its code in an account under your name, so you do not lose it if a server fails, an AI tool stops working or your payment card is blocked.

We do not keep your code

When the work ends, we delete our copy and ask you to remove our access.

We do not rewrite your app from zero

You keep the app you already built. We fix what is wrong in it, because building it again costs much more and takes much longer.

We do not own your product

The product stays yours: the idea, the users and the money it makes. You decide what it does and keep building it. We check how it is built, and every check comes to you in writing, from an engineer you know by name.

We do not make you depend on us

You can stop working with us any month. Everything we did for your app stays with you and keeps working.

We do not only run an automatic check

A program can find a password that leaked. Our engineer also finds why it leaked and fixes the cause.

What we check

Nine areas: eight in the app, starting with its base, and the agents that guard it. For every problem, we tell you what it costs to leave it and what it costs to fix it.

01

How the app is built

How your app stores its data, whether it follows good practice, whether all its parts fit together as one system, and whether the technology is right for the job. Also what breaks when many users arrive, and whether you can leave the platform you started on.

02

Logins and accounts

Who can log in, what an attacker can do with a stolen login, and whether password reset and email confirmation really work.

03

Customer data kept apart

The access rules in Supabase, Firebase or your own code that decide whether one user can see another user's data.

04

Keys and passwords

The secret keys your app uses to reach other services: keys written into the code, keys anyone can see in the browser, and keys that stay in old versions of your code after you deleted them.

05

Ready-made code your app uses

Packages the AI made up, packages nobody updates anymore, and packages that run their own code when installed, without anyone checking it.

06

Backups and recovery

Whether backups exist, whether anyone has ever restored one, and what happens when a database change goes wrong.

07

Updates and tests

Whether the app has tests, whether you can try a change safely before users see it, and what happens when a change breaks the live app at night.

08

Costs and limits

Your monthly bills for hosting and AI services, the limits on how often your app can use them, and the limit that runs out at the worst moment.

09

Your agents and what they check

The rules and instructions behind your agents: what they catch, what they miss, and what nobody told them to check.

The cost of waiting

While you set up the agents yourself, your business waits

You can spend weeks on prompts and rules for your agents and still not know if they are right. We have done this many times and know what works. We set it up in days, and you get it in writing: what each agent checks and why.

How the review goes

Five working days of one senior engineer. Here is what happens before, during and after them, and what each side does.

  1. 01

    Before we start

    A free 30-minute call about your app. If the review makes sense, we usually start the next working day after we agree, and within a week at the latest. We sign an NDA first if you want one. Nothing starts until you say yes.

  2. 02

    What we need from you

    Access to read your code and a way to run the app. Before we start, we send you step-by-step instructions for your tools, such as Lovable, GitHub or Supabase. During the five days, quick answers when the engineer has a question. If we need more access, for example to the live app, we ask you first.

  3. 03

    During the five days

    The engineer goes through your app, and you keep working as usual. If we find something that cannot wait, such as a leaked key or customer data open to anyone, we tell you the same day.

  4. 04

    The report and the call

    At the end you get the written report. On a one-hour call the engineer goes through it with you, and you decide what to fix first. The call is recorded, so you can watch it again.

  5. 05

    After the fixes

    When the fixes are done, we check them once more, at no extra cost. Then you decide: stop there, or keep the same engineer every month.

What is in the report

  • A clear verdict on the first page: launch, launch after these fixes, or not yet. Signed by the engineer who did the work.
  • Every problem with proof: the exact place in the code, or the steps that show it. Not just a “high risk” label.
  • What each agent checks today, what it misses, and what it should check instead.
  • A written plan of how your agents should work: what they build and check against from now on.

How monthly support works

We set up the agents once and keep them working as your product changes. A senior engineer checks them, so you do not have to.

Agents updated as the product changesPart of the monthly support. Each month at $6,000 includes 30 hours of the engineer's work on your code and 20 hours with you: calls, chat and your questions. If a month needs more, we tell you first, and you decide.

New features need new rules for the review agents. We write them, not you.

What to build, written down and up to datePart of the monthly support. Each month at $6,000 includes 30 hours of the engineer's work on your code and 20 hours with you: calls, chat and your questions. If a month needs more, we tell you first, and you decide.

Your agents work from it. It stays with your code and follows our public method: spex on GitHub

A monthly check of what the agents missed

A senior engineer reads a sample of recent changes and fixes the rules that let problems through.

A strict check before every change goes live

Go live or not yet, with reasons, every time. Nobody skips it because they are tired.

A one-page report every month

What the agents caught, what they missed, and what we changed.

A direct chat when something looks wrongPart of the monthly support. Each month at $6,000 includes 30 hours of the engineer's work on your code and 20 hours with you: calls, chat and your questions. If a month needs more, we tell you first, and you decide.

We answer the same working day.

You can stop any month

The agents, the written instructions and the automatic checks stay yours and keep working.

What people often miss

Data protection rules in the review

If you sell in the EU, the UK or the US, laws like GDPR and CCPA may apply to your app. Almost every app with user accounts stores personal data, even if it is only email addresses. The review finds out which rules apply to you, then checks where the data is stored, what your privacy policy promises, how users can delete their data, and what you would do after a data leak.

Pricing

The review has a fixed price. Support is paid monthly, at a price that includes a set number of hours.

The review is a week of real work by a senior engineer, so it has a price. The 30-minute call before it is free.

Claude Code team review

$3,000fixed

5 working days

A senior engineer checks what your agents built: what to keep, what to fix, and how your agents should work together. The report is yours, even if you stop there.

  • All nine areas listed above
  • Every problem with proof
  • The shared setup written into your repository
  • A two-hour session with your team on your code, recorded
  • One more check after your fixes, included
Book a 30-minute call

Agent team, set up and maintained

from $6,000per month

monthly, cancel any time

30 hours a month of work on your code

20 hours a month with you

A bigger app may need more hours. Then we tell you the price after the review, before support starts.

We set up the agents that review, test and protect your product, and keep them working as it changes. A senior engineer checks their work every month.

  • Review agents for design, security and tests
  • A check before every change goes live
  • What to build, written down and kept up to datePart of the monthly support. Each month at $6,000 includes 30 hours of the engineer's work on your code and 20 hours with you: calls, chat and your questions. If a month needs more, we tell you first, and you decide.
  • A monthly check of what the agents missed
  • A chat answered the same dayPart of the monthly support. Each month at $6,000 includes 30 hours of the engineer's work on your code and 20 hours with you: calls, chat and your questions. If a month needs more, we tell you first, and you decide.
Book a 30-minute call

Who does the work

ForEach Partners is a team of engineers who do the work themselves. Every partner has solid experience of building software, proven on real projects. The partnership is run by senior partners with 20+ years in large companies as engineers, team leads and CTOs, on systems where a data leak meant trouble with regulators, not just a bug to fix. Our engineers still write code every day, with the same AI tools you use.

How we work is written down and open to anyone. It is called spex, and we use it on every project. It is written for engineers and AI tools, so you do not need to read it yourself: spex on GitHub

Questions before you book

Do you need access to my code?
Yes: access to read it, and a way to run the app. Before we start, we send you step-by-step instructions for your tools, such as Lovable, GitHub or Supabase, and you can remove the access at any time. If we need more, for example to fix a problem in the live app, we ask you first.
Will you sign an NDA?
Yes, before we see anything. You can send yours or use ours.
Who will I sign the contract with?
With one of the companies in our group. We sign contracts in Europe, the US and other jurisdictions, and we choose the country by where your company is. You get the company's name, country and registration before you sign anything. We work in English.
Who owns the report?
You do, even if you never work with us again.
What if you find nothing serious?
Then the report says so and shows every check we made, signed by the engineer. You can show it to a customer or an investor who asks.
Is there a free version of the review?
No. It is a week of a senior engineer's work. But the 30-minute call is free, and on it we tell you honestly whether you need the review at all.
Do I need the review before monthly support?
Yes. The review is how the engineer gets to know your app. Monthly support starts after it, with the same engineer.
How soon can you start?
Usually the next working day after we agree, and within a week of the call at the latest. The review then takes five working days.
Is this a training course?
No. The engineer works on your code with your developers. The two-hour session at the end of the review goes through the setup we wrote for your repository.
Do we need Claude Code Team or Enterprise?
No. We work with the plans and tools your team already has: Claude Code, Cursor or Codex.

Find the problems before your users do

A 30-minute call about your team's setup, without a sales presentation. Tell us what you built and what worries you. After the call, you will know if you need the review, the support, or nothing at all.

Book a 30-minute callsales@foreachpartners.com
ForEach PartnersForEach Partnerssales@foreachpartners.com

© 2026 ForEach Partners

Privacy