Running a claude code system for every client

Hey there,

Matteo here from Kinetyca.

Someone asked me last week how we stop Claude giving a different answer about the same client two weeks apart. Fair question, and the honest answer has nothing to do with the model. It is where we put the files.

So here is the shape we run, because it is the least glamorous part of our system and the one that changed the most.

01The shape

Every client account we run lives in its own GitHub repo, and every one has the same folder structure. Open any account and you already know where to look. That was the point.

There is no code inside. The skills that run the work sit in a separate repo. A client folder holds what we know about that client and what we have done for them. Credentials live in neither one, they get resolved at the moment they are needed.

The part doing the real work is git. Every change is a commit, with a name on it and a message saying what it was. Nothing below this holds without that.

02Three things sit inside

• The foundation. Who they are, what they sell, the broad ICP, the proof we can use, how they talk. We write this once, at the start, and every campaign after that reads from it instead of rebuilding its own.
• The campaigns. One folder per campaign, grouped by engine: targeting, copy, personalisation, the sequence, and the rules that decide when it scales or stops.
• The record. One dated file per decision, every Slack thread and call transcript captured raw, and the reporting on top.

03The four rules that keep it from rotting

• One home each. The broad ICP, the type of company we go after for that client, lives in the foundation. The narrow one, the exact segment a single campaign targets, lives in that campaign's file. When the ICP moves, we edit one file.
• No version numbers in folder names, and nothing moves to an archive when a campaign winds down. The status goes at the top of the file instead. Move a folder and every reference to it breaks.
• Nothing in the record gets edited after the fact. A transcript goes in the way it came out and stays that way. We only ever add to it.
• Decisions get their own file the day we make them. Each one carries the date, who made the call, and which earlier decision it replaces.

Plenty of this writes itself. The Slack ingest drops new replies straight into comms, each one as its own commit, so the record fills in without anyone maintaining it.

04Claude works in there the same way we do

It branches, does the work, and opens a pull request. It cannot push to main by itself. One of us approves the merge.

That constraint is doing more work than it looks like. It means an agent operating on a live client account leaves the same trail a person does, and a bad change is one revert away rather than a forensics exercise.

05Why we hold the shape

Because of what it does to our decisions.

When we ask Claude about a client, it reads the whole account before it answers:

• the foundation, so it knows what we promised them
• the campaign, so it knows what is live right now
• every decision on record, so it does not propose what we already ruled out
• the raw comms, so it works from what the client actually said

The time goes into the decision instead of the reconstruction. That gap is most of what people are actually paying for when they hire an agency, and most of what quietly disappears when the context lives in someone's head.

Same for a person. The README tells you which order to read the folders in, so someone new on an account is not waiting on a call to explain it.

And the same shape across every account is what makes it repeatable. A skill we write once knows where the ICP, the copy and the reporting live in all of them.

Every decision on a client account gets made with everything we know about that client already in the room.

I am curious where this sits on your side. Most teams I talk to have the knowledge, it is just spread across a CRM, a drive, and three people. Hit reply and tell me where yours actually lives.

PS. If you want a Claude system like this mapped for your setup, book a call with us here