What teams build with AgentBundle.
Real patterns where one person on the team builds an agent and the whole org uses it. The marketing lead writes a brand voice agent; engineers, sales, and support all run outbound through it. The customer-success lead writes a triage agent; engineering bug-triage, product, and marketing all consume the same classification.
What these examples have in common
Every story below follows the same three steps. The agents differ; the shape doesn’t.
- One person who knows the work. The founder, head of marketing, customer-success lead, HR partner — whoever owns the canonical playbook today. They click New Agent in the dashboard, pick a starting template (or start from scratch). No engineer in the loop.
- The documents that already guide the work go in. The brand guide, the qualification rubric, the handbook, the classification taxonomy — the same docs that today live in a Notion page nobody reads. The agent references them through MCP connections, so it stays current as the docs change.
- One reviewer signs off, the whole team installs it. Each teammate installs into whichever runtime they already use — Claude Code, Cursor, Copilot, OpenCode, Gemini, Codex, Windsurf, or the AgentBundle dashboard. When the original author updates the canonical, every team’s next invocation picks up the new version on next sync.
Brand voice agent
An on-brand writing assistant the marketing lead authors once. Engineering, sales, and support all run outbound through the same lens.
Customer research synthesizer
A research agent that turns transcripts and surveys into themed summaries with quote evidence. Authored by research, used by product, marketing, sales, exec.
Founder-mode handoff agent
A founder bottles their playbook into one agent. The next hire inherits it on day one — same approach, same voice, same instincts.
Internal policy answerer
A people-ops agent that surfaces existing company policy from the handbook. Authored by HR; used by every employee — surfaces published docs only.
Onboarding buddy
An onboarding agent the HR partner authors once. Every new hire across every department uses it for the basics, day one.
Sales call coach
A coaching agent the head of sales authors once. AEs use it before calls; sales managers use it during 1:1s; enablement uses it to refresh the playbook.
Ticket triager
A triage agent authored once by CS. Support routes, engineering bug-triages, product surfaces pain points, marketing finds quotes.
Every use case assumes the governance to back it — N-required reviewers on the canonical version, an audit trail across every change, and policy that travels with the agent. See /security for the governance surface and /pricing for the reviewer-workflow features available on Business and above.
More use cases land as they ship. → /blog for product writeups.
Pick one. Build it. Hand it to your team.
Same flow whether your team is three people or thirty.
Free for teams up to 5. No credit card.