Proposal Follow-Up Emails: A 4-Step Cadence and Templates for Small Agencies

Most small agencies do not lose deals to a competitor. They lose them to silence.

You send the proposal on a Tuesday. The client says "great, we'll review this week." You go back to delivering the three projects already paying the bills. By Thursday the thread has dropped off the first screen of Gmail. Three weeks later you remember, send an awkward "just checking in," and get nothing, or "we went another way."

Nobody did anything wrong. There was simply no system between "proposal sent" and "decision," and in a 1-to-10-person studio the founder is the sales team and half the delivery team. This article is that system: a four-email follow-up cadence, the pipeline stages and five fields to track, and how to run it in Gmail.

Why agencies lose deals after the proposal

Agency sales has a shape spreadsheets handle badly. The deal lives in one long email thread. The decision involves someone who never appears in it. The proposal is a PDF on message 14 of 22. And it all happens alongside delivery, so your attention is elsewhere exactly when the follow-up is due.

A spreadsheet row knows the client's name and the value. It does not know the thread has been quiet for nine days, or that you promised a revised scope and never sent it. Those facts live in Gmail, so the tracking should too.

The proposal follow-up cadence

Four touches over twenty days. Each is short, each gives the client a reason to reply, and none sounds like a chase. If the client said "we decide at the end of the month," shift the dates so the day-10 email lands a few days before that.

Day 2: the check-in

Hi Dana, quick one: did the proposal come through and open fine on your end? Happy to walk through any section on a 15-minute call if that's easier than reading. No rush on a decision, just making sure nothing got stuck in spam.

Purely logistical. It confirms receipt and gives the client an easy first reply.

Day 5: the value-add

Hi Dana, one thing I meant to include: here's the case study from the rebrand we did for a similar-sized firm last year, including what the first 90 days looked like. Thought it might help when you discuss it internally.

Send something useful that costs you nothing: a relevant example, a short video walking through one part of the scope, or an answer to a question from the call.

Day 10: the soft close

Hi Dana, checking in on where things stand. If the timing or scope isn't right, that's genuinely fine, and it helps me plan the studio's schedule to know. If it's a yes, I can hold the November start date until Friday.

A real constraint (your calendar) plus a blameless way to say no. A fast no beats a slow silence.

Day 20: close the loop

Hi Dana, I'll assume the timing didn't work out on this one, so I'll close the file on my side. If it comes back around, the proposal stands for 60 days and I'd be glad to pick it up. All the best with the launch either way.

A surprising share of these get "sorry, it's been chaotic, we're still in." That is the deal you would have lost to silence.

Pipeline stages that fit agency work

Enterprise CRMs ship with eight stages. An agency needs five:

Lead → Discovery call → Proposal sent → Follow-up → Won / Lost

Follow-up is the stage the whole system exists for: the proposal is out, the client has not decided, and someone owes an action. Give every Lost deal a one-line reason, because "went with a cheaper freelancer" three times in a quarter is useful information.

What to track per deal: five fields

Fewer fields means you actually fill them in:

1. Value – the proposal total, or monthly value times twelve for a retainer.
2. Decision date – what the client said, not what you hope.
3. Who else is deciding – the person not on the thread.
4. Next action date – the most important field. Every open deal has one.
5. Stage – one of the five above.

Skip lead source and probability percentages until you have more than 30 deals a year to analyse.

Version one: Gmail labels plus a Google Sheet

For a solo freelancer this works, and it is free. Create one Gmail label per stage (1-Lead, 2-Discovery, 3-Proposal, 4-Follow-up) and move the thread between them. Use snooze to bring the thread back on the next action date. Keep a sheet with one row per deal and the five fields, and check the Follow-up label against it weekly.

It breaks at predictable points. A second person: labels are per inbox, so when a producer also talks to clients, nobody sees the whole pipeline. Fifteen or more open proposals: snooze holds one date per thread, and the sheet and Gmail drift apart because every update happens twice. Reporting: "what did we send in Q3 and what closed?" means rebuilding the sheet by hand.

If you are solo with under ten open proposals, stay here.

Version two: a Gmail CRM

Whichever tool you pick, the shape is the same: a pipeline board inside Gmail, each deal a card attached to its email thread, follow-up tasks on the card, templates a click from the compose window, and the same board for everyone on the team.

In Teamopipe, our product, it works like this:

1. Create the deal from the proposal thread in the Gmail sidebar. Nothing is copied into a spreadsheet, and the thread stays linked.
2. Add the five fields as custom fields on the pipeline.
3. Automate the cadence. One automation: when a deal's stage changes to Proposal sent, create four tasks due on days 2, 5, 10 and 20. The follow-ups are scheduled the moment you move the card.
4. Save the four emails as templates. Insert, change the name and the one specific detail, send.
5. Work the task list daily. Overdue tasks show on the deal and in the Tasks section, so a quiet thread stays visible even when it is buried in your inbox.

Streak and NetHunt follow the same pattern with their own boards, tasks and snippets, so the method transfers directly.

What it costs

Per user per month, as listed on each vendor's pricing page in October 2026:

Streak's free plan no longer includes pipelines, so a shared pipeline there starts at Pro. NetHunt's sequences and reports start on its $60 Business plan. Teamopipe Starter covers pipelines, tasks, templates and 3 automations; reporting and automatic email sequences are on Growth at $29.

If your team already lives in Streak, the switching cost probably outweighs the price gap. NetHunt is the pick if you want LinkedIn integration and will pay for Business. Teamopipe has a smaller integration catalogue and no native mobile apps; the trade is price, simplicity and direct support. See the Streak and NetHunt comparisons, or how other studios set it up on our agencies page.

Retainer renewals as a second pipeline

Renewals are lost the same way proposals are: the date passes while everyone is heads-down on the work.

Run a second, smaller pipeline: Active → Renewal in 60 days → Renewal conversation → Renewed / Churned, with a task on each retainer 60 days before the end date. The day-5 value-add becomes a results summary of the last period, and the day-10 soft close becomes a scope conversation for the next one. A renewal raised at 60 days is a planning conversation; at 5 days it is a price negotiation.

15-minute setup checklist

1. Create the pipeline with the five stages (2 minutes).
2. Add the five fields (3 minutes).
3. Save the four follow-up emails as templates, in your own words (5 minutes).
4. Add the automation that creates the four follow-up tasks (2 minutes).
5. Create cards from the last ten proposal threads in Sent, or import them from your sheet via CSV, and give each a next action date (3 minutes).

Then once a day: open the task list, work what is due, close it.

FAQ

How soon should you follow up after sending a proposal?

Two days. A short logistical check-in confirms the proposal arrived and surfaces early questions. Follow with a value-add on day 5, a soft close on day 10 and a close-the-loop email on day 20, adjusted to the client's stated decision date.

What should a proposal follow-up email say?

Three or four sentences, something specific to the client, and an easy reason to reply: offering a short call, sharing a relevant example, or making "no" an acceptable answer. Avoid "just checking in" as the only content.

How many times should you follow up on a proposal?

Four times over about three weeks is enough for most agency deals. After the close-the-loop email, mark the deal lost with a reason and move on.

What is the best way to track proposals for a small agency?

Track each proposal as a deal card attached to its email thread, with five fields: value, decision date, who else is deciding, next action date and stage. A solo freelancer can use Gmail labels and a sheet; a team, or anyone with 15 or more open proposals, usually needs a Gmail CRM.

What pipeline stages should an agency use?

Lead, Discovery call, Proposal sent, Follow-up, and Won or Lost, with an optional second pipeline for retainer renewals.