Follow-up

Draft the follow-up for the call in "$ARGUMENTS".

Compute with code. Perform every calculation (totals, balances, ratios, variances, projections) with a script — Bash, Python or a spreadsheet formula written to a file — and include the computation alongside the result. Never do arithmetic mentally.

Prerequisites

The call notes, pasted or as a file. When $ARGUMENTS or the request names a deal, use that name as <deal> whether or not its folder exists yet in .singularskills/sales/. With no deal named: with exactly one deal folder there (not playbook), use it; with several, ask which; with none, read none and continue.

Process

1. What you heard: the buyer's situation and pains, in their words from the notes, so they can correct anything wrong.

2. What was agreed: decisions, materials promised by either side, and who does what.

3. The next step, with a date; if none was agreed, propose one.

4. Promise nothing the notes do not support, and nothing beyond the policy: no discount, date or feature that was not agreed. Honest selling. No false urgency, no fake scarcity, no misrepresentation of the product or a competitor, and no commitment (discount, term, date, feature) beyond the policy the user stated; anything beyond it is marked for approval, with who approves.

5. Keep it short: a few sentences per part, in the seller's voice, with the buyer's name only as the user supplied it.

Output

In chat: the email, ready to send, and a list of anything you flagged (an unclear commitment, a missing date). This skill writes no file.