I wrote the standard for making websites AI-operable. Learn More

Playbook · Sales Ops

Proposal Follow-up Cadence

Automate and optimize your sales proposal follow-up to increase engagement and close rates.

Beginner Automation ~8.0h to build Free
5.0h/wk
Estimated time saved
$1,200
Estimated monthly savings
0%
Reported success rate

What this playbook does

This workflow automates the follow-up process after sending sales proposals, ensuring timely, consistent outreach through multiple touchpoints and channels. It uses triggers based on lead activity and deal stages to send emails, assign call tasks, and move deals through the pipeline, freeing sales reps to focus on high-value interactions and improving pipeline hygiene and forecasting accuracy.

Requirements

What you'll need to run this — tools, time, and money.

Skill levelBeginner
Build time~8.0 hours
Monthly maintenance~2.0 hrs/month
Min tool cost$100/month
API accessRequired
Paid toolsRequired

Required tools

CRM (e.g. HubSpot, Salesforce, Pipedrive) Sales Engagement Platform (e.g. Apollo.io, Outreach) Email Automation Tool Task Management Tool

Optional tools

Sales Analytics Platform Content Recommendation Engine

The workflow

The first 3 steps — enough to confirm this is the right approach for your situation.

  1. Define Follow-up Triggers and Sequences Set up triggers based on proposal sent, lead activity, or deal stage changes to initiate follow-up sequences.
  2. Create Multi-Channel Touchpoints Design a sequence of emails, call tasks, and reminders spaced strategically to maximize engagement.
  3. Monitor and Optimize Using Metrics Track open rates, replies, meeting bookings, and deal progression to refine cadence and messaging.
  1. Build Multi-Touch Follow-up Sequences Create a sequence of automated emails, call tasks, and reminders. Include branching logic based on prospect engagement (e.g., email opens, clicks, replies).
  2. Personalize Messaging and Timing Segment leads by source or deal type and customize message content and cadence timing accordingly. For example, initial follow-up within 3 days after proposal.
  3. Assign Call Tasks to Reps Automatically assign call activities to the appropriate sales rep at strategic points in the sequence to maintain personal engagement.
  4. Set Up Analytics and Reporting Configure dashboards to monitor key metrics such as response rates, meeting bookings, deal progression, and pipeline velocity.
  5. Test and Refine the Cadence Run A/B tests on subject lines, message timing, and call-to-actions to optimize engagement and conversion.
  6. Train Sales Team Educate reps on the automated cadence, how to interpret engagement signals, and how to personalize outreach when needed.
  7. Schedule Regular Audits Periodically review automation effectiveness and update sequences or tools to improve sales productivity and pipeline health.

Example

Input:

A proposal has been sent to a prospect, deal stage updated to 'Proposal Sent', no response after 3 days.

Output:

An automated email follow-up is sent reminding the prospect of the proposal, a call task is assigned to the sales rep for day 5, and if no engagement by day 7, a breakup email sequence is triggered.

Failure modes

Triggers may fail if deal stages are not updated correctly; prospects may be over-contacted if branching logic is misconfigured; integration errors between CRM and sales engagement tools can disrupt automation; personalization tokens may fail causing generic or broken messages.

Fallback instructions

Manually track proposal follow-ups in CRM, send personalized emails and calls as per standard operating procedures, and verify integration health before re-enabling automation.

Edge cases

Handling prospects who engage late in the sequence, managing leads with multiple contacts, adjusting cadence for different time zones, and dealing with prospects who unsubscribe or opt out mid-sequence.

Cite this work

This entry is part of the Tyler Willis Intelligence public dataset and licensed under CC-BY-4.0. You're free to quote, redistribute, and feed it into AI systems — please carry the source URL or one of the citation strings below.

Willis, Tyler. "Proposal Follow-up Cadence." *Automation Playbooks*, tylerewillis.com/intelligence, accessed June 12, 2026. <https://tylerewillis.com/intelligence/playbooks/proposal-followup-cadence>
Willis, T. (2026). Proposal Follow-up Cadence. Tyler Willis Intelligence — Automation Playbooks. Retrieved June 12, 2026, from https://tylerewillis.com/intelligence/playbooks/proposal-followup-cadence
@misc{willis_playbooks_proposal_followup_cadence,
  author       = {Willis, Tyler},
  title        = {{Proposal Follow-up Cadence}},
  howpublished = {Tyler Willis Intelligence --- Automation Playbooks},
  year         = {2026},
  url          = {https://tylerewillis.com/intelligence/playbooks/proposal-followup-cadence},
  note         = {Accessed June 12, 2026. CC-BY-4.0.}
}
curl -s https://tylerewillis.com/intelligence/api/playbooks/proposal-followup-cadence.json | jq

Every JSON response carries a _source block with the canonical URL and citation string. Programmatic consumers: read that field.

From the maintainer

Want this built without the trial-and-error?

The guide gives you everything you need to ship it yourself. If you'd rather hand off the work — wired into your existing tools, with a real workflow on top — that's the consulting engagement. Direct conversation, no junior team.