You sent the proposal. The client sounded interested. Then the conversation stopped.
A useful freelance proposal follow-up is not about chasing someone until they answer. It is about keeping the opportunity visible, making the next decision easy and knowing when to stop spending attention on it.
When should you follow up after a freelance proposal?
Start with the decision date or review window the client gave you. If no timing was agreed, ask about their decision process and record a next contact date that allows them time to review. A simple offer and a proposal requiring several approvals need different follow-up plans.
| Situation | Useful next move |
|---|---|
| The client gave a decision date | Wait for that date. Follow up after it passes rather than interrupting the agreed window. |
| Simple proposal, no date given | A calm follow-up after a few business days is reasonable. |
| Complex proposal with several stakeholders | Allow more review time and ask about the decision process rather than demanding an answer. |
| Client asks you to check back later | Record the exact date and follow up then. |
| Client says no | Close the opportunity. Do not turn a clear decision into another follow-up sequence. |
A simple freelance proposal follow-up workflow
- Send the proposal. Record the sent date, amount or project value, and any decision date the client mentioned.
- Set the next follow-up immediately. Do not rely on remembering the proposal when your delivery work becomes busy.
- Follow up briefly. Keep the message tied to the project and make it easy for the client to reply with a question, decision or revised timeline.
- Update the opportunity. If they need more time, replace the old reminder with the new date. If scope changes, update the proposal rather than pretending the original offer still applies.
- Close the loop. After a reasonable number of unanswered attempts, move the lead out of your active follow-up queue.
What to say when the client has not replied
The exact wording matters less than three things: keep it short, reference the actual project and give the client an easy next step.
Example — first follow-up
Subject: Re: Website redesign proposal
Hi Maya — I wanted to bring the website proposal back to the top of your inbox. If anything around scope, timing or the next step needs clarifying, I’m happy to go through it with you. Let me know what would be most useful from me.
Example — after their decision date passes
Hi Maya — you mentioned Thursday as the likely decision point for the redesign, so I wanted to check where things landed. No problem if the timing has moved; if so, tell me when it makes sense to pick the conversation back up.
Example — closing the active follow-up
Hi Maya — I’ll close this out on my side for now so I’m not filling your inbox. If the project becomes active again, feel free to come back to me and we can confirm scope, timing and availability then.
Do not manufacture scarcity or claim another client is taking the slot unless that is actually true. A follow-up should reduce uncertainty, not create fake pressure.
What to track in a freelance CRM
You need enough context to know why the lead is waiting and what happens next. You do not need a giant sales system.
| Property | Purpose |
|---|---|
| Lead / client | Who the opportunity belongs to. |
| Project | What they are considering buying. |
| Stage | For example: discovery, proposal sent, waiting, won, lost or later. |
| Proposal sent | The date the offer entered their hands. |
| Proposal value | The commercial value you are waiting on. |
| Last contact | The last meaningful interaction. |
| Next follow-up | The date the opportunity should return to your attention. |
| Next action | The concrete thing you will do when that date arrives. |
| Notes | Decision process, objections, dependencies or commitments worth remembering. |
A view filtered to open opportunities with Next follow-up on or before today becomes a simple daily queue. That is more useful than scanning every contact in the CRM looking for somebody you might have forgotten.
For the broader structure, see how to track freelance leads and follow-ups without building a heavy CRM.
Worked example: six proposals, one clear queue
This fictional review is on 12 October 2026. The dates illustrate recorded decisions, not a universal contact schedule. Use Opportunity as Title, Stage as Select, Next follow-up as Date and Next action as Text.
| Opportunity | Stage | Next follow-up | Next action |
|---|---|---|---|
| Cedar · website | Waiting | 12 Oct | Ask whether decision date moved |
| Northline · branding | Proposal sent | 14 Oct | Offer to clarify deliverables |
| Paper House · brochure | Later | 2 Nov | Resume at requested time |
| Orbit · audit | Won | — | Move kickoff into delivery |
| Fieldwork · campaign | Lost | — | Record decline; stop follow-up |
| Acme · landing page | Waiting | Empty | Choose a next action or close |
Cedar · website
Ask whether the decision date moved.
Acme · landing page
Choose a date, pause or close the opportunity.
Northline: 14 October
Paper House: 2 November
Keep the agreed review window.
Illustrative result cards, not a CRM screenshot.
Reproduce the dated queue: combine Stage is not Won AND Stage is not Lost AND Next follow-up is on or before 12 October 2026. For this fixed-date exercise, only Cedar should appear. Create a separate view with the same stage exclusions and Next follow-up empty to catch Acme. Fixed date boundaries require manual updates.
Change Cedar’s date to 15 October: it should leave the dated queue while remaining in the pipeline. Restore 12 October after the test. Review the AND/OR filter guide if the results differ.
When should you stop following up?
Choose a stopping rule before the sequence becomes open-ended. Keep messages relevant, allow time between them and reassess whether the opportunity still deserves active attention.
Stop the active chase when the client clearly declines, asks you not to follow up, the opportunity is no longer valid, or repeated well-spaced messages receive no response. If the project may return later, keep the relationship in your CRM without keeping it in today’s action queue.
Do not confuse “later” with “active”
If a client says “come back in November”, that is useful information. Move the opportunity to Later and set one November reminder. Do not keep it sitting in Proposal sent for six weeks making the pipeline look healthier than it is.
Do not confuse silence with a project
An unanswered proposal is an opportunity, not booked revenue. Keep delivery planning and sales pipeline planning separate until the client actually commits.
The rule worth keeping
Every open proposal should have one of three things: a decision, a next follow-up date or a reason it has been closed.
If it has none of those, it is not being managed. It is simply being remembered.
Frequently asked questions
When should I follow up after sending a proposal?
Start with the client’s stated decision date or review window. If none was agreed, ask about timing and record your next contact date. There is no single schedule that fits every proposal.
Should I offer a discount when the client goes quiet?
Silence does not identify the objection. Ask whether scope, timing or another question needs clarification before changing the offer. If the offer changes, record what changed.
What if the client asks me to contact them next month?
Record the requested date, move the opportunity to Later and use one reminder for that date. Respect the pause rather than keeping it in the daily contact queue.
Does an unanswered proposal count as booked work?
No. Keep it in the sales pipeline until the client commits. Confirm the agreed scope, timing and next step before treating the opportunity as delivery work.
If a reply changes the deliverables, follow the change request workflow before agreeing extra work. After acceptance, use the multiple-client workflow to plan delivery.