When should you use it?
- You run a small agency and are the bottleneck
- Client knowledge lives in your head
- You produce similar ads and reports for many accounts
Not for: Agencies without someone to review output; Clients whose contracts forbid AI-generated work
What do you need, and what do you get?
You need
- Client briefs and offers
- Your ad frameworks and report templates
- A repository for the knowledge folder
You get
- A knowledge base with a file index
- Ad sets in themed groups
- Agency and client report versions
How does it work, step by step?
- Collect what you knowPut briefs, frameworks, benchmarks and checklists into one versioned folder.
- Keep files short and rankedLimit each context file's length and state which level overrides which.
- Route by taskWrite a skill that decides which files to read for each kind of request.
- Make skills phasedFor copy: gather client data, build buyer profiles, write hooks, then full ads.
- Ask before reportingHave the report skill confirm campaign type and target metric before generating.
The prompt
The original prompt by Victor Chazarra, word for word, with a link to where it was published. Below it is our adapted version with fill-in blanks, if you want it. Works in Claude Code. Values in lime are placeholders.
Original prompt by Victor Chazarra
I want to build a knowledge base for my marketing agency. Create a git repository called Fan-Convert-Brain with this structure: identity/ for who we are, processes/ for SOPs, strategy/ for our frameworks, benchmarks/ for performance data, tech-stack/ for tool docs, admin/ for services and billing, team/ for team priorities, clients/ for client workspaces, skills/ for AI capabilities, and tools/ for production software. Create a CLAUDE.md at the root that acts as a router, telling you which folder to check depending on the type of question.
Exactly as published by Victor Chazarra in How to Run a Marketing Agency With AI (Claude Code Workflow) | Sucana.
Our adapted version (optional)
You are working in our agency knowledge folder. Read CLAUDE.md first, then only the files the routing skill lists for this task: [task]. Client-level files override agency-level ones. For ad copy, follow the four phases: client data, buyer profiles, hooks, full ads. Produce [10] ads in [2] themed groups. Do not change any context file without my approval.
What can go wrong?
- One giant context file is a listed anti-pattern; split by concern.
- Context changes should need explicit human approval.
Our take
Victor Chazarra's interesting contribution is discipline around context, not the claim of replacing hires. Short files, an explicit hierarchy of which document wins when they conflict, and a routing skill that picks files by task are what keep output consistent across eight clients. That structure is worth copying for any agency or consultancy work. Keep a human review on every ad before it goes live, because ad platforms punish policy mistakes and brand damage is hard to undo. Measure output quality against your previous work for at least a month before deciding it is better: click-through, approval rate from clients and time to first draft are fair metrics. Store client-specific briefs separately from shared frameworks so one client's strategy never leaks into another's ads. Version the knowledge folder in Git as he did, so you can see when a framework changed. Ask clarifying questions before reporting, as his reporting skill does, rather than inventing numbers.
Where the time goes back: Repeated agency work stops depending on the founder, so growth no longer requires new hires for every account.
FAQ
Who runs it day to day?
Was it tested on real work?
Source and credit
The original prompt on this page is by Victor Chazarra, shown word for word with a link to where it was published. The summary, notes and adapted version are ours.
- Original
- How to Run a Marketing Agency With AI (Claude Code Workflow) | Sucana
- Creator
- Victor Chazarra
- Published on
- sucana.ai
- Original date
- Mar 24, 2026
- License
- Not openly licensed; the original prompt is shown word for word with credit and a link to the original
- Originally for
- Claude Code
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.