Agent Bob logoAgent Bob
Sign inBuild
Moderate risk
Signed pack $29
GDPRCAN-SPAM

CRM Update Agent

An up-to-date CRM with no after-meeting admin.

A ready-to-build governance package for Sales & CRM. Your runtime enforces it; Agent Bob does not run the agent.

Build this packageHave it set up for you

Purpose

You want the CRM kept current after every meeting without reps typing notes. This agent reads meeting notes and calendar events and stages CRM updates. A rep confirms the staged changes before they are applied.

It will

  • Staged CRM record write only — changes require sales rep confirmation before committing; no delete or ownership transfer

It won't

  • Delete contact records, reassign account ownership, merge duplicate records without manager approval, write sensitive personal attributes outside approved fields

It asks a person first

  • Sales rep must confirm all staged updates before they are applied to the live CRM

Tools

  • Calendar scheduling
  • Database updates
  • CRM updates
  • Calendar scheduling: Suggest and place calendar holds.
  • Database updates: Change records in a database.
  • CRM updates: Update records in your CRM.

✋ You approve once at the start of each run

Budget defaults

Per task
$0.10
Per month
$25
Actions a day
100

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 — meeting notes and contact details not retained by agent after staged write 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.md What your runtime has to enforce, file by file
  • agent-blueprint.json The agent's purpose, tools and settings
  • policy.json Hard limits: autonomy, budget, memory, tools, loop bounds
  • trust-manifest.json The integrity manifest your runtime can verify
  • routing.rules.json Which tools need approval before use
  • run-report-template.json What every run reports back
  • approval-gates.md The moments that must pause for a person
  • deployment-checklist.md What 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.

Build this packageHave it set up for you