Playbook · Sales Ops
Proposal Follow-up Cadence
Automate and optimize your sales proposal follow-up to increase engagement and close rates.
I wrote the standard for making websites AI-operable. Learn More
Playbook · Sales Ops
Automate and optimize your sales proposal follow-up to increase engagement and close rates.
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.
What you'll need to run this — tools, time, and money.
The first 3 steps — enough to confirm this is the right approach for your situation.
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.
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.
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.
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.
Other workflows in the Sales Ops category.
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
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.