SUMMARIZATION
Turn a Closed Lost opportunity into a root-cause loss memo in Coda
When a Salesforce opportunity flips to Closed Lost, it analyzes the deal's full objection history and writes a single root-cause loss memo to Coda for the product and competitive…
How it runs
The automated pipeline, trigger to output.
- TriggerOpportunity moved to Closed LostSalesforce
- ActionRead objection history and close reasonSalesforce
- LogicBranch on objection signal depth
- ActionSynthesize root-cause loss memoOpenAI
- OutputAppend memo to Coda Loss LibraryCoda
What it does
The moment a deal is marked Closed Lost, this workflow reviews everything the prospect objected to across the deal's lifecycle and produces a one-page root-cause memo: the primary reason the deal died, the contributing factors, the competitor named (if any), and what would have had to be true to win it.
When to use it
Use it when you want a disciplined post-mortem on every lost deal without asking reps to write one. It is most valuable for teams tracking competitive losses and feature-gap losses that product should act on.
How it works
- 1A Salesforce trigger fires when an opportunity's stage changes to Closed Lost.
- 2The workflow reads the opportunity's objection notes, close reason, and competitor field.
- 3A logic step branches on whether enough objection signal exists; thin deals get a short stub instead of a full memo.
- 4OpenAI synthesizes a root-cause memo naming the primary loss driver and the win conditions that were missing.
- 5The memo is appended to a 'Loss Library' table in Coda, tagged by account and competitor.
Set it up
What you configure once, before turning it on.
- 1Connect SalesforceAccounts, opportunities, cases.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect CodaDocs, packs, automations.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Summarization workflows
On-submit Loom standup roll-up archived to Confluence
When a standup video is submitted via webhook, transcribes it, generates a per-person written summary, and appends it to a running team standup page in Confluence.
Front Escalation Handoff Doc in Notion
When a Front escalation closes, drafts a structured handoff document in Notion capturing the resolution, customer commitments, and open follow-ups, then alerts the AE in Slack.
Front Escalation War-Room Brief to Slack
On a Front escalation, posts a concise threat-assessment brief to a Slack channel only when the AI judges the situation high-severity.
VIP Front Escalation Instant Exec Page-Out
Detects escalations from VIP accounts in Front, generates a one-paragraph executive recap, and pages the named account exec via Slack and Salesforce task within minutes.
Release health note per Vercel deploy
When a Vercel deploy goes live, summarizes the Sentry errors observed in the release window into a plain-English health note that separates brand-new error classes…
Rollback recommendation when a deploy spikes errors
When a Sentry alert fires for an error spike, attributes it to the most recent deploy, summarizes whether the spike is dominated by new error classes introduced by that release.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.