The repo structure for agencies and consultants: one Claude Code workspace, every client

With AI, the hard part of agency work isn't the prompt. It's keeping six clients' context apart, and keeping it current. This workspace gives every client a folder Claude reads before it writes, and your own agency one too.

What's inside:

• my-agency/: your own context (positioning, offers, voice, goals) and outputs, so your agency's marketing runs on the same system as your clients'.

• clients/active, previous and prospects, plus clients/_template: copy it for each new client and you get nine context folders and nine output lanes, each with a one-page CLAUDE.md.

• An example client, Pulse Analytics, with every context file filled in.

• 11 skills that build a client's context in order: /company-context, /icp-research, /competitor-research, /win-loss, /expert-pov, /tov-guidelines, /brand-kit, /positioning, /messaging, /funnel-strategy and /goals. Plus /level, a quiz on how far your setup has come.

• House rules that make Claude ask which client before it reads or writes, cite a source for every claim, and mask personal data in call transcripts.

• latest.md and history.md per client, so you can hand a client to a teammate, or to tomorrow's session, without a briefing.

Connecting your apps:

Exa web search is wired in .mcp.json with a free key. GA4, Search Console, Granola, Slack and Firecrawl are ready to switch on in the same file, and .claude/connections.md explains 12 connectors and how to add each.

For agencies, consultants and fractional marketers.

If onboarding a new client takes you a week of copy-pasting, copy clients/_template and run /company-context on their website. Week 1 of Marketing Engineering University builds this with you.