Lead Qualification Agent
A prioritized lead list every morning.
A ready-to-build governance package for Sales & CRM. Your runtime enforces it; Agent Bob does not run the agent.
Purpose
You want reps spending time only on leads that fit. This agent reads your CRM and approved enrichment sources and scores and shortlists leads. It never writes to contact records or messages prospects.
It will
- Read-only CRM and approved enrichment API access — no contact record writes, outbound messaging, or list exports without approval
It won't
- Export prospect lists externally, use enrichment sources that violate GDPR consent requirements, write to CRM records without sales rep confirmation
It asks a person first
You approve once at the start of each run
Tools
- Database updates
- Web research
- Database updates: Change records in a database.
- Web research: Look things up online.
✋ You approve once at the start of each run
Budget defaults
- Per task
- $0.10
- Per month
- $30
- Actions a day
- 200
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 profile data not retained after shortlist handoff
Autonomous within the limits below, with the strongest governance.
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.