Everyone thinks they’re using AI for marketing.
They’re not.
Only 8% of CMOs run campaigns where multiple agents work on their own.
Asking a chat to write a blog post isn’t using AI. That’s the default now.
Using AI for marketing means having a full team of agents running campaigns and workflows that speed up your whole org.
So I’m breaking down how to run a whole swarm of marketing agents in one single article. Who does what, how they talk to each other and which programs run it.
Bookmark it, because it’s long.
Hire agents the way you’d hire people
Most people pick a tool first and then look for something to automate.
I’d do it the other way around. Start from the job description.
Write down the hires you’d make if you had the budget. A content marketer, an SEO manager, an email marketer, an analyst. Then build one agent per role.
Each agent gets the same four things a new hire gets:
One job: “Writes first drafts in our voice”, and that’s it.
One owner: the human who approves its work and gets tagged when it breaks.
One output: a draft, a report, a flag or a queue.
One line it never crosses: usually “never send anything outside the team.”
An agent with three jobs does all of them badly.
An agent with one job manages its context way better.
The full team I use
Here’s the roster I’d start with. Seven agents, each one replacing a role most marketing teams hire for.
Press enter or click to view image in full size
1. Captain Takes every request, splits it into tasks and sends each one to the right agent. Every morning it posts one digest with what’s done, what’s stuck and what needs you.
2. Researcher Finds new opportunities based on your goals. Launches, funding news, “best tools for X” lists and threads where people ask for recommendations.
3. Competitor analyst Watches a fixed list of competitors. Learns from their wins and their mistakes, so you can react fast.
4. Writer Drafts posts, articles and briefs from what the researcher found. It learns your company’s voice and uses your marketing and writing skills.
5. SEO / GEO Tracks your rankings and how ChatGPT or Claude answer questions about your product. It flags when you drop out of an answer or a competitor shows up.
6. Outbound Finds the right moment to reach out, like a new hire, a launch or a podcast. It drafts the note and explains why it picked that person. A human sends it.
7. Analyst Pulls the weekly numbers, compares them to last month and writes three lines on what moved.
This is what a captain’s morning digest can look like:
Done: 3 drafts ready in approvals. Competitor check found 1 pricing change. Stuck: SEO agent can’t reach the rankings export. Tagging Leo.
Needs you: approve the launch post by 2 PM, Maria.
The roles I’d leave out for now are anything that posts publicly, spends money or talks to customers on its own.
Those agents can be useful. But anything that touches money needs a human in the loop most of the time.
How the agents talk to each other
This is where most setups break.
Seven agents that don’t talk to each other are just seven chat windows.
The structure I like has three levels:
Captains: each person on the team has one captain agent. It knows that person’s priorities, keeps a plan and talks to them directly.
Subagents: the captain splits big tasks into pieces and starts a subagent for each one. Checking 30 competitor pages becomes 30 small jobs running at the same time.
Captain to captain: captains can message each other. Your captain can hand work to a teammate’s captain, or ask it something only it knows.
For this to work, the whole team needs to follow a few habits.
Put the whole brief in the handoff
A subagent usually starts from its prompt alone. It hasn’t seen your chat or your earlier corrections. If the brief says “write the post we talked about”, it will guess.
A good handoff has four lines:
Task: draft a launch post for the new pricing page
Sources: pricing page, last 3 launch posts, rules file
Done means: under 200 words, one CTA, no claims without a source
Tag when done: Maria in the content channel
Write things down where everyone can read them
Agents share what they learn through files, docs and threads. Chat history doesn’t count. When the researcher finds a pricing change, it goes into shared memory, so the writer can use it the same day.
Keep one rules file for every agent
Tone, banned words, brands you never mention, claims you can’t make. Change a rule once and every agent follows it from the next task.
Slack is the main office
Agents need a room where humans can watch them work and give them context.
For most teams, that room is Slack.
A simple layout looks like this:
One channel per function, like content, SEO or lifecycle.
One agents channel for handoffs across teams.
One approvals channel for anything that needs a human yes before it leaves the team.
Press enter or click to view image in full size
The best part is that anyone can jump in. Tag an agent when you need info, when something needs a quick fix, or drop it in the middle of a discussion to get fresh ideas.
The stack I use to run my agent team
A lot of platforms let you create agents. These are the two I use.
Capy
Capy is built for engineering teams, but its Captains also run research and reports.
A Captain is a long-lived agent that splits work into threads, reads every report and only tells you what needs you.
Why it works for a team:
Captains are shared and can message each other, so your captain can hand work to a teammate’s captain.
You can message a specific Captain straight from Slack, like “captain=Content draft the launch post.”
Each Captain keeps its plan and rules in files, so it picks up where it left off days later.
It runs on a schedule, like “every weekday at 9, update the digest.”
It has its own virtual machine, so it can use a browser.
I use it for coordination, big research jobs that split into many subagents, and work that passes between teammates.
Grok Bot
In Bot you create one bot per job, each with its own memory.
Routines run a bot on a schedule or when something happens, like a Slack mention, a new email or a webhook. Connectors plug it into Slack, Notion, Gmail, Drive and more. Before anything like sending, it stops and asks for your approval.
I use it for the recurring jobs. The morning digest, the competitor watch, the weekly numbers and the inbox sweep.
The tools around them
Press enter or click to view image in full size
Agents, like humans, need the right tools. The ones I’d give them first:
Slack: the office.
Notion: the rules file, the playbooks and the task tracker.
Firecrawl: turns websites into clean data the agents can read, like competitor pricing pages and changelogs.
Posthog: what users actually do in your product.
Gmail: your inbox, for reading and drafting emails.
If you can only start with one, start with a single Grok Bot routine. Add captains once more than one person on your team is running agents.
The rules every agent inherits
Gartner expects over 40% of agentic AI projects to be canceled by the end of 2027.
So write these down before you add your second agent.
Nothing leaves the team without human approval: Emails, posts, replies, comments and anything that costs money. Agents draft, people send.
Agents never contact strangers: They can find the person and write the note. But if that person isn’t on the allowlist you gave them, reaching out is a human call.
Every agent has one human owner: Put the owner in its name or profile, so everyone knows who to tag when it breaks.
Each agent only gets the apps its job needs: The writer doesn’t need your inbox. The analyst doesn’t need your DMs. Less access, cleaner context.
Log everything: What ran, what it read, what it changed and who approved it. Your manager should be able to read last week without asking you.
Yes, approvals slow things down.
They’re also the reason you’ll still trust the setup a year from now.
Humans are still needed
Agents are smart. In a lot of things, smarter than us.
But they still miss the human part.
They can write ten versions of a post. Picking the right one is still on you.
People reply to people, not to agents.
Someone has to decide what good looks like.
And no agent will ever tell you a workflow stopped being worth it. You have to kill it yourself.
Want to blindly trust your agents? Go for it, but only on the low-stakes stuff.
Anything that touches revenue stays with humans.
How to start
Don’t build seven agents right away.
Build two or three. Give it one boring job each, like your morning digest.
Let them run for a few days. Fix what annoys you.
Only add the next agent when the last one gets boring. Boring means it works and you stopped checking it every hour.
You don’t need the full roster to start. You need things working.
Delegate, review, fix, repeat. That’s the ideal orchestration workflow.
I post about Growth and AI agents every week. Follow me if you want more of this.