What teams build with AgentBundle.
Real patterns where one agent gets authored by a head-of-function and used by every team across the org. 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 four steps. The agents differ; the shape doesn’t.
- One author who knows the domain. A head-of-function writes the agent. Marketing lead → brand voice. Customer-success lead → ticket triager. HR partner → onboarding buddy. The author is whoever owns the canonical playbook today.
- Canonical docs go in. The same docs that today live in a Notion page nobody reads — the brand guide, the qualification rubric, the handbook, the classification taxonomy. The agent references them through MCP connections, so it stays current as the docs change.
- One reviewer signs off, the agent publishes. Once approved, anyone in the org can use it from whichever AI runtime they work in — Claude, Cursor, Copilot, OpenCode, Gemini, Codex, Windsurf, or the AgentBundle dashboard.
- When the canonical updates, every team picks it up. The author re-publishes; the new version ships with a changelog. The audit log keeps the full history of what changed and who approved it.
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.
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.