Guides · Proposal follow-ups

Proposal follow up cadence (D+3 / D+7 / D+14) for freelancers

Updated Nov 2, 2026 · ~7 min read · FollowRail

You sent the proposal on Monday. They replied “this looks great—circling back after internal review.” It is now Thursday. Your calendar has a blank. Your brain has a low-grade itch you keep calling “give them space.” Space without a next chase date is how proposals die politely. This proposal follow up cadence is narrow on purpose: three follow-ups, two tones, and a Follow-ups row so the next nudge is a date—not a mood.

What you are actually following up on

A proposal chase is not the same as an overdue-invoice chase. Mixing the two is how you sound needy on a warm deal—or soft when cash is late. Keep them as two Types in one Follow-ups database. Same “today” view. Different scripts.

• Proposal nudge — Trigger: stage is Proposal sent (or Negotiation with silence). Goal: restart a decision, not collect cash. Tone risk: sounding needy. Success: a reply, a call, or a clear Lost.
• Invoice chase — Trigger: status is Sent / Partial and the due date has passed. Goal: collect or clarify timing. Tone risk: sounding aggressive. Success: Paid, a Partial plan, or Void.

For the broader system that holds both next to the same clients, see the companion guide on a client follow up tracker.

The D+3 / D+7 / D+14 ladder

Count from the Proposal sent date (or from the last client reply if they asked for time). Put the next Due date on a Follow-ups row the moment you mark Stage = Proposal sent. That is the whole habit: the next date exists before you close the tab.

D+3 — friendly landing check

Assume email filters and busy weeks, not rejection.

Hi [Name], just checking this landed. Happy to resend the PDF or jump on a 15-minute call if useful. No rush if you are still gathering feedback.

Goal: confirm receipt and offer a low-friction next step. Do not re-pitch the whole scope.

D+7 — firm, still short

They had a week. Ask for a decision shape, not a compliment.

Hi [Name], following up on the proposal sent [date]. Are you leaning yes / need a revision / pausing for now? Any of those answers helps me plan the next two weeks.

Goal: force a bucket. Yes, revise, or pause are all wins. Silence is the only failure mode.

D+14 — firm + boundary

Protect your calendar without a guilt trip.

Hi [Name], still holding the [start window / rate] from the proposal. If timing slipped, I can send a revised start date; if the project is paused, I will close this one as Lost on my side so we both have a clean slate. Either way works.

Then update Stage: Negotiation, Won, or Lost. Create the next Follow-up only if they are still open. Optional D+30 is for long enterprise cycles only. Most solos should stop at D+14 and recycle energy into new pipeline.

Where this lives in Notion (four pieces, not a life OS)

You need a small desk—not twelve databases:

1. Deals — Stage includes Proposal sent; store Proposal sent date and Value.
2. Follow-ups — Type = Proposal nudge; Due date; Status Open / Done / Skipped; Cadence tag D+3 / D+7 / D+14; Script snippet.
3. Clients — so every chase has a person, not an orphan deal.
4. Dashboard — linked view: Follow up today (Due ≤ today, Status = Open).

When you mark a Follow-up Done, immediately create the next cadence row or close the deal. The product is the habit of writing the next date—not a prettier board.

Two tones, not an email blast tool

Keep two short snippets as templates or a text property default:

• Friendly: receipt check; offer to resend or call.
• Firm: ask for yes / revise / pause; then boundary at D+14.

Copy into your own inbox. Notion will not send the message—and that boundary is intentional. You keep tone control; the database only stops you from forgetting. A proposal follow up template freelancer setup should track dates and scripts, not pretend to be a mail server.

Mistakes that kill the cadence

• Waiting for “the right energy” instead of setting a Due date on send day.
• Writing a novel every nudge (re-attaching the full deck every time).
• Mixing invoice language into a proposal chase (“payment was due”).
• Ten databases and a habit tracker so you never open Follow up today.
• Infinite D+30s for a solo client who already ghosted twice.

How FollowRail fits

FollowRail is a focused freelance CRM Notion template built for that desk: clients, proposal stages, a follow-ups view for today / upcoming / overdue, and invoice status next to the same people. You store cadence tags and script snippets so D+3, D+7, and D+14 are rows—not sticky notes.

Delivery is simple: pay once ($23.99), open the Duplicate link, and set up in about five minutes. It stays in your Notion workspace—yours to keep and tweak. It does not email clients for you; you paste the nudge from your own mail client on purpose.

Copy-paste Start Here (about ten minutes)

1. Add Proposal sent date on Deals.
2. Add Follow-ups Type + Cadence + Script snippet.
3. Build a Follow up today view (Due ≤ today, Status = Open).
4. For one live proposal: set Stage = Proposal sent, create D+3 due in three days with the friendly snippet.
5. When D+3 is Done, create D+7 the same minute.

If setup takes longer than about ten minutes, delete properties until it does not.

Honesty checklist

• This cadence does not email clients for you.
• It does not replace a full CRM if you need portals, e-sign, and card checkout in one login.
• Lost is a valid Stage. Clearing dead proposals is progress.
• Invoice overdue tracking is a sibling workflow—not a substitute for proposal nudges.

More on FollowRail: product overview · client follow up tracker guide · what’s included · FAQ