Post-Call Follow-Up Email

Paste your messy call notes. You get the follow-up email a good rep sends within the hour: an accurate recap, the agreed next step with a date, and a short mutual action plan — plus a flag on everything you failed to establish on the call.

A Markdown deliverable containing: (1) a subject line referencing something specific from the call; (2) a follow-up email with a two-to-four-bullet recap in the prospect's words, the agreed next step with owner and date, an optional three-to-five-step mutual action plan, and a close; (3) [confirm: ...] markers wherever the notes are ambiguous; (4) below a horizontal rule, an internal 'What the notes do not establish' section listing unanswered questions and the single priority for the next call.

**Subject:** Tuesday re-planning and your telematics question

Hi Marta,

Thanks for the time this morning. Capturing what I heard so you can correct me:

- Route planning for 34 vans across 3 depots happens in a spreadsheet, and it takes one planner most of Monday.
- Your words: if a driver calls in sick on Tuesday, the whole day is manual. That mid-week re-plan is the part that costs you, more than the Monday build.
- You looked at something in this space around two years ago and did not proceed. [confirm: I did not ask what stopped it, and it would genuinely help me not to repeat someone else's pitch.]
- You asked whether we integrate with your telematics provider. I owe you that answer.

**Next step:** I will confirm the telematics integration and send you a short written answer by Thursday. [confirm: you mentioned finding time in a couple of weeks — shall I propose two slots for the week of the 14th?]

One thing I would ask before we go further: you mentioned Ravi would need to be involved. If it is useful, I can write the integration answer in a form you can forward to him rather than something aimed only at you.

Best,
[Your name]

---

## Internal — what the notes do not establish

- **Why the previous evaluation failed.** This is the single biggest risk in the deal. Whatever stopped it two years ago is probably still in the building, and you will meet it again at the same stage.
- **What Ravi's involvement actually means.** Approver, budget holder, technical veto or interested party are four different deals. The notes record the name and nothing else.
- **Any budget signal at all.** Not discussed. Also not urgent on a first call, but it cannot stay unknown past the next one.
- **The cost of the Tuesday re-plan.** She described the pain vividly but there is no number attached — no missed drops, no overtime, no cost per manual re-plan. Without one there is no business case to hand to Ravi.
- **Which telematics provider.** The notes say 'their telematics' without naming it, and the answer to her question depends entirely on which one it is. Ask before you promise anything.
- **What 'interested' means.** Recorded as a judgement, not as something she said or did. No commitment, no timeline, no internal action on her side.

**Priority for the next call:** find out what killed the previous evaluation. Everything else on this list can be gathered later; that one determines whether the deal is winnable at all.