Marketing team
- Web chat
- Slack
- Notion
- Resend
- Typefully
A team of marketing agents: a lead routes work to specialists for positioning, long-form content, social, SEO, and email, publishing through Notion, Typefully, and Resend.
- Web chat
- Slack
- Notion
- Resend
- Typefully
agent/agent.tstypescriptimport { defineAgent } from "eve";
/**
* Root agent runtime configuration.
*
* @remarks
* Sets the model for the marketing team lead; the rest of the agent's surface (channels,
* connections, tools, skills, subagents) is discovered from the filesystem under `agent/`. This
* agent routes work to specialists rather than producing deliverables itself, so it is the first
* place to try a cheaper model tier if cost matters more than routing quality. Conversation history
* is compacted once it reaches 90% of the context window.
*/
export default defineAgent({
compaction: { thresholdPercent: 0.9 },
model: "anthropic/claude-opus-5",
});
Marketing Team eve Template
Run a team of marketing agents built on eve. You bring work to a team lead: a launch to plan, posts to write, or a page that isn't converting. The lead briefs the right specialist and hands back what they produced.
You talk to it in Slack or a terminal. It delivers real work in the tools you already use: blog drafts in Notion, social posts in Typefully, email campaigns in Resend.
What using it looks like
You: We're launching workspace templates next Thursday. Can you draft the announcement posts?
Lead: On it. I'll check the brand context and brief the social media coordinator.
Lead: Done. Three drafts are in your Typefully queue: an X thread, a LinkedIn post, and a Bluesky post. Nothing is scheduled yet, so review them and tell me when to queue them for launch morning.
Anything irreversible, like sending an email campaign or publishing a scheduled post, pauses for your approval first. You get an approve or deny button in Slack or the terminal before it goes out.
Deploy
The one-click deploy provisions and wires up everything the team needs:
Before your first email campaign
Verify a sending domain and create at least one segment in the Resend dashboard. The agent sees your verified domains and segments and picks from them, but it cannot create a domain or verify DNS for you.
Quick start with an AI coding agent
Working in Claude Code or Cursor? Paste this:
The team
The team shares one piece of state: the brand context document, a short file describing what your product is, who it's for, and what the team claims about it. The product marketer maintains it; every other specialist reads it at the start of a task. Because it's the team's only shared state, it has a single owner.
Each specialist has a distinct job: the product marketer decides what the team claims, the content marketer writes long-form copy, seo decides which pages should exist, and social-media-coordinator and email publish to an audience. Newsletters route through two of them: the content marketer writes the prose, then the email specialist adapts it for the inbox and sends it through Resend, so newsletters still get the content marketer's planning and editing passes.
How it works
- One lead, five specialists. The lead loads the brand context and your preferences, writes a brief for the right specialist, and hands back what they produce. It never writes deliverables itself.
- Every brief is self-contained. Specialists start fresh each time, with no shared conversation history, so the lead's brief carries everything and each specialist reads the brand context itself.
- Delegation goes one level deep. Specialists do their own research and edit their own drafts against a written rubric rather than spawning further agents.
- Nothing irreversible happens without you. Sends and deletes in Resend, deletes and scheduled publishes in Typefully, and page moves in Notion all wait for your approval. Drafting stays friction-free. The email specialist also only sees 47 of Resend's roughly 85 tools, so account administration is out of reach entirely.
- Slack pins four starter prompts in a fresh conversation, one per specialist: sharpen our positioning, write a blog post, draft social posts, review a page's SEO.
The full approval matrix, the credential model, and the reasoning behind each boundary live in docs/ARCHITECTURE.md.
Local development
Link the project you deployed, or a fresh one, and pull its environment:
Under the hood
Customizing
The agent auto-updates as you edit these files. docs/CUSTOMIZING.md is the full walkthrough, with recipes for adding a specialist, skill, tool, or connection.
Specialists don't have to live in this repo. eve's remote agents let the lead delegate to an agent in its own deployment, with its own skills, connections, and release cycle:
Set PAID_ADS_AGENT_URL, and the lead picks the specialist up from its description exactly as it does the local ones. Useful when a specialist needs credentials or a release cycle you'd rather keep out of this repo, such as ad platform access.
Learn more
Deeper internals live in docs/ARCHITECTURE.md and agent guidance lives in AGENTS.md.