Quotes sit open.
The customer asked for pricing, you sent it, and now the next action is buried in email, text, CRM, or somebody's head.
Free swipe pack · quote follow-up
Steal the quote follow-up cadence before another open estimate goes cold.
A practical follow-up pack for service businesses that send quotes, estimates, proposals, or approvals and then rely on memory to chase them. Use it manually today, or turn it into a human-reviewed automation.
Use this when
Follow-up feels awkward.
The business waits too long, writes each chase from scratch, or gives up because no one knows what to say next.
No one owns the queue.
There is no single view of quote sent date, value, customer objection, next touch, and close/lost reason.
7-day cadence
Follow up without sounding desperate.
Day 0
Send the quote with the decision deadline, one clear next step, and one sentence reminding them what problem it solves.
Owner reviews before sendDay 1
Confirm they received it and ask if anything is unclear before they compare options or go quiet.
Light touchDay 3
Restate the business outcome, not the price. Offer to adjust scope if timing/budget changed.
Value touchDay 5
Surface the next available start date, install window, production slot, or decision deadline.
Scarcity without hypeDay 7
Close the loop politely. Ask whether to keep it open, revise it, or archive it for later.
Clean queueGuardrail: do not automate final sends blindly. Draft the follow-ups, let a human approve them, and track replies/lost reasons.
Swipe copy
Day 1 · received?
Subject: Quick check on the quote
Hi [Name] — quick check that the quote came through cleanly.
If anything looks off, send me the question and I’ll tighten it up. If it looks good, the next step is [approve / deposit / pick a date].
— [Your Name]
Day 3 · value reminder
Subject: One note on the quote
Hi [Name] — one thing I wanted to call out: the quote is built around [main outcome], not just the line items.
If the budget or timing changed, I can show you the simplest version that still solves the core problem.
Day 5 · scheduling pressure
Subject: Start window for [project]
Hi [Name] — I still have [start window / production slot / install date] available for this.
Do you want me to hold it, revise the scope, or release the quote for now?
Day 7 · close the loop
Subject: Should I close this out?
Hi [Name] — should I keep this quote open, revise it, or close it out for now?
No pressure either way. I just don’t want to keep nudging you if the timing changed.
Automation map
Turn the swipe pack into a system.
The minimum viable build
- Quote sent date + quote value
- Customer email/phone + owner
- Next follow-up date
- Draft status: waiting / approved / sent
- Reply/lost reason capture
What AI should do
- Summarize the quote and customer context
- Draft the next follow-up in the right tone
- Flag stale quotes daily
- Suggest scope changes when budget/timing objections appear
- Never send sensitive messages without approval
Want this mapped against your real workflow?
If you want the DIY version, start with the $27 Operator Quickstart and build one human-reviewed queue. If you want me to map the quote leak, follow-up cadence, and first implementation spec, request the $499 Revenue Leak Audit.