CRM Update Diff Builder

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

Pastes in the current CRM record (as JSON) plus new context (a call transcript, an email thread, or meeting notes) and 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. This distills the diff-before-write safety pattern from Gumloop's CRM Agent: the model never writes to the CRM and never claims to have updated anything, it only proposes a side-by-side diff for a human or a separate write step to review and approve. It differs from Call Notes to CRM, which extracts a fresh MEDDIC-shaped record from a transcript alone. This template takes an existing record as an input, reasons about what specifically should change against it, and outputs an auditable diff rather than a full replacement record, which is what makes it safe to sit in front of an actual CRM write. 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." }