Read the CRM and score deterministic quality rules.
Full Stack GTM · Live CRM audit
One set of rules for every agent
touching your CRM
Use Claude, Codex, Gemini, Cursor, or your own automations across HubSpot and Salesforce. Every proposed change follows the same rules, waits for the right approval, and leaves a record of what happened.
Live AI agent · Cloudflare Container · fullstackgtm v0.58.0 · isolated demo workspace
you ask → agent runs tools → you approveLIVE · CLOUDFLAREKeep the source record and reason behind every finding.
Turn proposed changes into typed, inert operations.
Authorize exact operation IDs, never blanket write access.
The shared rulebook
Decide once how agents may change your CRM
Connect a new model, enrichment source, or automation without inventing another write path. The same checks apply every time.
Resolve before create
Check domains, emails, and open deals before adding a record. Ambiguous matches stop for review.
Compare before set
Re-check the live record before writing. If it changed after the plan was made, skip it instead of overwriting it.
Approve before apply
Each write names the record, field, old value, new value, reason, and risk. Approve only the operations you want.
Record every result
Applied, skipped, and failed operations all leave receipts, so you can reconstruct what happened later.
One path into the CRM
Every agent proposes changes the same way
The model can change. The source can change. The approval path stays the same.
01RequestRoute these leads
→02ReadInspect live records
→03PlanShow exact changes
→04ApproveSelect allowed writes
→05ApplyRe-check and write
→06ReceiptRecord every result
A real request
“Reassign everything owned by the rep who left.”
The agent finds 238 records. Full Stack GTM proposes 214 owner changes, excludes 18 contacts on closed-won deals, and skips six records that changed during review. You approve the 214. Those—and only those—can write.
plan pl_3c19
214 ready for approval
18 excluded by policy
6 changed since review
0 writtenThe work it governs
One rulebook across daily RevOps work
routePut every record with the right owner
Round robin, territory, account ownership, capacity, fallback, and reassignment.
cleanFix the records your reports depend on
Duplicates, missing owners, stale deals, broken links, empty amounts, and past close dates.
enrichControl what outside data may replace
Match source data to CRM records, fill blanks, and refresh only fields the source previously stamped.
captureTurn calls and signals into reviewed updates
Extract next steps, score accounts, and draft CRM tasks without silently changing or sending anything.
Tested against real CRM work
The rules hold across models
1,904graded runs across ten models from six vendors
8 of 10models completed with zero unauthorized writes
17.6% → 0%unauthorized-write rate for Claude Sonnet 4.6, raw tools versus Full Stack GTM
Keep the rules
Open source and local by default
Run the CLI on your machine with your own HubSpot or Salesforce credentials. Your CRM data goes directly between the CLI and your CRM. The rules, plans, and receipts remain inspectable under Apache-2.0.
Questions before you connect a CRM
Does every change require approval?
Approval is explicit and operation-specific. You can review a whole plan or select individual writes. Scheduled jobs may prepare plans, but they cannot approve themselves.
Can I use my own agent?
Yes. Use the CLI directly, install the Full Stack GTM skill, connect through MCP, or call the library from your own automation. The same write rules apply.
Does this replace HubSpot or Salesforce?
No. Your CRM remains the source of record. Full Stack GTM governs how agents read it, propose changes, and apply approved writes.
Does my CRM data pass through Full Stack GTM servers?
Not when you run the open CLI with your own credentials. The CLI talks directly to your CRM. The optional hosted app syncs CRM data to provide browser review and team features.
Can I test it without credentials?
Yes. npx fullstackgtm audit --demo runs the full audit against a deliberately messy sample CRM. It makes no external connection and writes nothing.
Give every agent the same CRM rules
Run the demo yourself, or book a working session to map the first governed workflow across your GTM stack.