Outreach Drafting Agent
Personalized sequences ready for rep approval in minutes.
A ready-to-build governance package for Sales & CRM. Your runtime enforces it; Agent Bob does not run the agent.
Purpose
You want personalized outreach sequences drafted for every qualified lead. This agent writes drafts into your outreach tool. A rep reviews and approves each sequence before it is activated.
It will
- Draft-only write to outreach tool — no send, no sequence activation without approval
It won't
- Send outbound messages autonomously, add contacts to sequences without opt-in confirmation, draft messages that omit unsubscribe mechanism
It asks a person first
- Sales rep must review and approve each outreach sequence before activation
Tools
- Database updates
- Document writing
- Database updates: Change records in a database.
- Document writing: Create or edit Word / Google Docs / Notion pages.
✋ Every outbound action needs your approval
Budget defaults
- Per task
- $0.20
- Per month
- $25
- Actions a day
- 50
The runtime pauses the agent at a limit. You can change every number in the builder.
Memory and autonomy
Session only. Nothing is kept once the session ends.
ClawMaven policy: session-only — prospect contact data and message content not retained after draft handoff
Acts within limits: low-risk steps on its own, everything gated still stops for a person.
What you get
The 8-file governed package your runtime loads and enforces. On the paid tier the trust manifest is signed, so your runtime can verify nothing was changed after you approved it.
HANDOFF.mdWhat your runtime has to enforce, file by fileagent-blueprint.jsonThe agent's purpose, tools and settingspolicy.jsonHard limits: autonomy, budget, memory, tools, loop boundstrust-manifest.jsonThe integrity manifest your runtime can verifyrouting.rules.jsonWhich tools need approval before userun-report-template.jsonWhat every run reports backapproval-gates.mdThe moments that must pause for a persondeployment-checklist.mdWhat to check before it goes live
This is a governance specification, not a running agent. The rules in these files do not enforce themselves: your runtime has to implement them.
Start from this package
Bob pre-fills the builder with it and drafts the rest. You confirm every step.