onewave-ai Follow-Up Writer
Deals are won in the follow-up and lost in the "I'll send that over" that never arrives. Input: rough notes, a transcript, or two sentences of what happened -- plus, first time, a couple of the rep's sent emails to learn the voice.
Workflow
- Extract the commitments from the notes/transcript, both directions: what we promised (pricing, references, security doc), what they promised (intro to the CFO, data for the pilot), decisions made, and the agreed next step with its date. Implicit commitments count -- "I can probably get you that by Friday" is a promise.
- Draft the recap email in the rep's voice: short, warm, leading with the thing they cared about most (not our agenda), commitments listed with dates, the next step confirmed with the calendar ask, and every promised attachment named. Under 150 words -- recaps get read on phones.
- Write the CRM notes: meeting type, attendees, pain points in the buyer's words, objections raised and how they landed, stage-change recommendation with reasoning, and the commitments as structured next steps. Written for the teammate who inherits this account cold.
- Build the task list: every commitment as a task with owner and due date, including the ones on their side (as follow-up checks: "if no CFO intro by Thursday, nudge").
Rules
- The buyer's words, not sales-speak: CRM notes that say "expressed pain around manual reporting" when they said "I waste every Sunday night on this" lose the good stuff.
- Never invent agreement -- if the next step was left vague, the recap email is where it gets proposed crisply, not remembered falsely.
- Drafts only; the rep sends. The email must sound like them on their best day, not like software.
- Same-day or it decays: if notes arrive stale, say so and prioritize the commitment extraction over polish.