Suede AI Agent StudioTemplatesStart buildingOpen workspace
Navigation menu

CRM Update Diff Builder

Sales template

Diff-before-write CRM updates: propose the change, never write blind.

Built for
RevOps and sales-ops teams (and CRM-writing agents ahead of a Salesforce/HubSpot API call) who need a reviewable, evidence-backed diff before any automated CRM write: paid per record, every call or thread processed.
  • Free to test
  • $0.09 per record, paid to you
  • You keep 100% of every sale

What CRM Update Diff Builder takes and returns

You give it

  • crmRecord text
  • context text

You get back

The crm diff, with these fields:

  • diff
  • summary

How the 3-step flow works

Keeps your CRM current with a reviewable, quote-backed diff. Paste in the current CRM record (as JSON) plus new context (a call transcript, an email thread, or meeting notes) and it returns a structured, field-by-field diff of what should change: current value, proposed value, the exact quote that justifies it, and a confidence score, plus a one-line summary. It follows the diff-before-write pattern: every change arrives as a side-by-side proposal for a human or a separate write step to approve, so each update to the record is one you signed off on. Where Call Notes to CRM builds a fresh MEDDIC-shaped record from a transcript, this template starts from the record you already have, reasons about exactly what should change, and outputs an auditable diff rather than a full replacement record, which makes it the right gate in front of a live CRM write. Input: current record { "stage": "Discovery", "champion": null, "budget": null } plus a call transcript where the prospect says "I'll be the one pushing this internally" and "we've got about $40k set aside for this." Output: { "diff": [ { "field": "champion", "currentValue": null, "proposedValue": "prospect (self-identified)", "sourceQuote": "I'll be the one pushing this internally", "confidence": 0.8 }, { "field": "budget", "currentValue": null, "proposedValue": "$40,000", "sourceQuote": "we've got about $40k set aside for this", "confidence": 0.85 } ], "summary": "Champion and budget identified from call; stage unchanged, no evidence for a stage move." }

  1. Input

    Takes the crm record and context.

  2. Claude

    Claude works as a CRM update proposer.

  3. Output

    Returns the crm diff.

The brief behind CRM Update Diff Builder

You are a CRM update proposer that never writes to a CRM and never claims to have written anything. You are given the current CRM record fields as JSON plus new context (a call transcript, an email thread, or meeting notes). Your only job is to propose a diff: for each field that should change, state the current value, the proposed new value, the exact quote from the context that justifies the change, and a confidence score. Never invent a current value that is not in the record, and never propose a change you cannot ground in a direct quote from the context. If the context does not clearly support a change to a field, leave that field out of the diff rather than guessing. You are a proposal layer only, a human or a separate write step approves and applies the diff; you never assert the CRM has been updated. Return only valid JSON.

The input contains two things: the current CRM record (JSON fields) and new context (a call transcript, email thread, or meeting notes). Compare them and propose exactly what should change, new stage, new or corrected fields, enrichment from the context. For each proposed change, output the field name, its currentValue (from the record, or null if the field does not exist yet), its proposedValue, the sourceQuote (the exact text from the context that justifies the change), and a confidence score from 0 to 1. Do not propose a change without a supporting sourceQuote. Do not fabricate a currentValue not present in the record. End with a one-line summary of the update. This is a proposal only, you are NOT writing to the CRM and must not phrase anything as already applied. Output strict JSON: { "diff": [{ "field": string, "currentValue": string|null, "proposedValue": string, "sourceQuote": string, "confidence": number }], "summary": string }. Example input: current record { "stage": "Discovery", "champion": null, "budget": null } plus a call transcript where the prospect says "I'll be the one pushing this internally" and "we've got about $40k set aside for this." Example output: { "diff": [ { "field": "champion", "currentValue": null, "proposedValue": "prospect (self-identified)", "sourceQuote": "I'll be the one pushing this internally", "confidence": 0.8 }, { "field": "budget", "currentValue": null, "proposedValue": "$40,000", "sourceQuote": "we've got about $40k set aside for this", "confidence": 0.85 } ], "summary": "Champion and budget identified from call; stage unchanged, no evidence for a stage move." }

What CRM Update Diff Builder can earn

Set your price per record. Callers pay in USDC over x402, and every settled call routes to your wallet.

Your price per record
Routes to your wallet each month$2703,000 paid calls at $0.09 · Suede AI takes 0% of the sale

Put CRM Update Diff Builder to work

All 3 steps open wired, priced at $0.09 per record.

Good work starts with a clear flow.

Give an agent a job. Connect the steps. See how the work becomes a service someone else can call.

Input
Reason
Output

A workflow you can inspect

Make the steps visible.

Start with a template or describe the job. Connect inputs, reasoning, and output on the canvas.

Explore templates
Canvas in motionProduct visualization · 20 sec
Read the visual description

A stylized organization chart opens into a workflow canvas. Input and reasoning nodes connect, the flow branches, and the run moves through its steps. The film ends with Suede AI Agent Studio. Music only; no spoken narration.