# How to Follow Up After Sending a Proposal

> Learn when and how to follow up on a proposal using verified client activity, smart timing, and six concise email templates.

## Follow Up After Sending a Proposal Without Guessing

To **follow up after sending a proposal** well, determine whether the client is busy, blocked, unconvinced, or unaware the proposal arrived. Silence, and a generic nudge, rarely tells you.

Match the message to verifiable activity. Signals include no recorded view, an identified visitor’s recent open, repeat visits, pricing-page activity, submitted feedback, or continued silence. TL;DR: Use verified activity to choose your timing and message. This guide offers a sensible schedule, six concise email templates, and a way to turn a PDF, folder, demo, or deck into a protected live link with access notifications and visitor analytics. The goal: make the next decision easier without seeming to watch over the client’s shoulder.

## Why a Proposal Follow-Up Email Matters

A strong **proposal follow up email** moves the decision forward by restoring context, answering one likely question, or offering a small next step. “Just checking in” instead makes the client reopen the thread and recall why the proposal mattered.

[Gong analyzed 304,174 follow-up prospecting emails](https://www.gong.io/blog/7-tips-for-writing-the-perfect-follow-up-sales-email-according-to-science) and found that very short “bubble-up” messages were **15 times less likely** to help book a meeting than follow-ups with useful context. The effective range was 30 to 150 words. A separate [Gong analysis of more than 28 million cold emails](https://www.gong.io/blog/does-cold-email-even-work-any-more-heres-what-the-data-says) found that the highest reply rates came from messages under 100 words and three to four sentences. Though not proposal-only studies, both favor concise, useful messages.

A useful follow-up:

- **Restore context:** Name the project, outcome, and proposal date.
- **Remove friction:** Reshare the link or explain an option.
- **Ask for one decision:** Request a reply, meeting, revision, or pause.
- **Respect the buyer:** Give them a comfortable way to say “later” or “no.”

A freelance designer seeing no verified view after two business days should first check access. Asking whether the link works is more useful than assuming the client has lost interest.

## Prepare the Proposal for a Useful Follow-Up Email

![Revdoku Tracking Links showing a named recipient link with separate views and visitors](/assets/blog/follow-up-after-sending-proposal/chrome-revdoku-recipient-links.webp)

Before sending, give the client an actionable document you can reliably keep current. In Revdoku, the standard route is: drag a PDF or project folder into a private bucket, choose access, and share the live link. AI agents, the API, or the CLI can automate repeat publishing later, but are optional.

Use this pre-send table:

| Item | What to Check | Why It Matters |
|------|---------------|----------------|
| **Decision details** | Scope, fee, dates, assumptions, and expiry date are explicit | The client can approve without another fact-finding round |
| **Next action** | The proposal names one reply, call, signature, or feedback step | A vague ending produces a vague delay |
| **Access mode** | Choose public, password-protected, or email-gated access | Protection and visitor identity are different needs |
| **Feedback route** | Add a clear contact path or built-in form | Questions can return without a separate backend |
| **Version control** | Test the live link and record the sent version | You can update the same link without creating link confusion |

An **email gate** can link access to a visitor-provided address. A password restricts entry but does not prove who opened the work. A public link suits low-risk material and is easiest to open, though visitor identity may remain unknown.

Consider an agency sending a deck, budget, and samples in one folder. It uses email-gated access, then corrects a date after sending. The client keeps the original link, avoiding another attachment thread. The stable link simplifies every later follow-up.

## Proposal Follow-Up Timing: When to Follow Up After Sending a Proposal

No hour suits every deal. Base proposal-follow-up timing on the deadline, client’s time zone, and promised decision process, not Tuesday-morning folklore. A default schedule prevents panic and neglect.

| Verified situation | Sensible timing | Purpose |
|--------------------|-----------------|---------|
| No recorded view | After **2 business days** | Check delivery and access |
| Recent identified view | Later that day or next business morning | Offer relevant help without hovering |
| Repeat identified engagement | Within **1 business day** | Resolve a likely open question |
| Pricing page or pricing link visited | Within a few hours or next business day | Clarify options and assumptions |
| Feedback form submitted | Within **4 business hours**, or by the next day | Confirm receipt and ownership |
| No response after a useful follow-up | After **3 to 5 business days** | Offer clear choices and close the loop |

Do not email two minutes after an open notification; it can feel automated. If a client opens a proposal at 4:45 p.m. a consultant can write at 9:00 the next morning with one project-specific question.

For in-pipeline emails, [Gong reports](https://www.gong.io/files/gong-guide-7-laws-of-highly-effective-sales-emails.pdf) a **37% success rate** when the sender suggested a specific date and time, compared with 28% for other calls to action. Treat that as guidance, not a universal promise. “Could we review the two scope options Thursday at 2 p.m. Eastern?” is more answerable than “Would you like to chat?”

## How to Track Proposal Views and Read Client Viewed Proposal Signals

![Revdoku website analytics showing views, unique visitors, downloads, and recent activity](/assets/blog/follow-up-after-sending-proposal/chrome-revdoku-analytics-overview.webp)

A “**client viewed proposal**” alert helps when the visitor is reliably identified. It does not prove the person read every page, liked the offer, controls the budget, or plans to buy. Separate the observation from your interpretation.

Revdoku tracks proposal views, visitor activity, visited paths, clicks, and downloads. Access tied to a captured email can also identify the visitor. Built-in forms provide stronger signals through the visitor’s exact words. Use only what the evidence supports:

| Observed data | Reasonable interpretation | Do not claim |
|---------------|---------------------------|--------------|
| No recorded open | Delivery or access may need checking | The client ignored you |
| Identified visitor opened the link | That address was used to access the proposal | The person read or understood it |
| Repeat visits or several relevant paths | The material may be under active review | Approval is close |
| Pricing path viewed or pricing link clicked | Pricing information drew attention | Price is the objection |
| File downloaded | The file was obtained | The whole document was reviewed |
| Feedback submitted | The stated question or request is real | The wider team agrees |

Email security tools and link scanners can create activity. Before inferring, look for human patterns such as a later return, relevant paths, a download, or a reply.

Suppose an identified buyer returns twice, opens the pricing path, and downloads an appendix. Ask whether the pricing assumptions need clarification. It does not say, “I know budget is your concern.” Analytics should sharpen the question, not answer it.

## Proposal Follow-Up Email Templates: No View or No Response

Use the **no-view template** only when your setup shows no verified access. It should fix delivery, not push for a decision.

1. **No verified view after two business days**

**Subject:** Can you open the [project] proposal?

Hi Maya,

I sent the proposal for Acme’s onboarding redesign on Tuesday. Could you confirm that the link opens on your side? It covers the scope, fee, and a July 29 start option.

Here it is again: [proposal link]

If someone else owns the decision, I’m happy to send it to them directly.

Best,
Jordan

2. **No response after earlier follow-ups**

**Subject:** Close the loop on [project]?

Hi Maya,

I have not heard back on the onboarding proposal, so I want to make this easy. Should we move ahead, revisit it in [month], or close it for now?

A one-line reply is enough. If timing is the issue, I can hold the current scope until [date].

Best,
Jordan

The second **proposal follow-up email** offers real choices. Use it after one or two useful messages over 7 to 14 business days. Do not repeat the same nudge.

A typical no-view case is simple: the client’s security policy blocks an unfamiliar domain. An access-check email reveals the problem, the sender supplies an approved route, and the conversation resumes. No persuasion was needed.

## Proposal Email Templates for Recent and Repeat Engagement

After a recent identified **client viewed proposal** event, wait to avoid seeming intrusive. Connect the message to a proposal detail. Mention an identified visitor plainly; omit tracking if identity is uncertain.

1. **Recent identified view**

**Subject:** One question on the [project] proposal

Hi Andre,

I received a notice that the protected proposal link was opened today. I wanted to make the next step easy: does the phased launch in section 3 fit your target date?

If useful, I can walk through the scope in 15 minutes on Thursday at 2:00 p.m. Eastern.

Best,
Priya

2. **Repeat identified engagement**

**Subject:** Would a short scope review help?

Hi Andre,

I wanted to clarify one point that often comes up during review: the research phase is included in both options, while user testing is only in the expanded scope.

Would a 15-minute comparison help? I can do Thursday at 2:00 or Friday at 11:00 Eastern.

Best,
Priya

For repeat engagement, use only recorded activity. Do not invent time-on-page, printing, forwarding, stakeholder identity, or a “signature-ready” event.

Imagine the same gated address returns to the scope and schedule on two days. The follow-up explains the phased launch and offers two meeting times. That fairly addresses repeat interest. Claiming that legal or finance is reviewing the deal would be guesswork.

## Templates for Pricing Interest and Submitted Feedback

Treat pricing interest as meaningful only when analytics record a visit to a distinct pricing path or a trackable pricing-link click. Even then, you know what was accessed, not what the buyer thought. Ask what the real constraint is.

| Verified condition | Safe language | Language to avoid |
|--------------------|---------------|-------------------|
| Pricing path visited | “Would a breakdown of the two options help?” | “I see that the price worries you.” |
| Feedback form submitted | “Thanks for the note about the workshop.” | “Your team wants the workshop removed.” |

1. **Pricing-page interest**

**Subject:** Pricing options for [project]

Hi Lena,

I wanted to clarify the two proposal options. The core plan is [price] and covers [scope]; the expanded plan is [price] and adds [item]. Both include [shared deliverable].

Is your priority a lower upfront cost or a faster launch? I can adjust the scope at the same link.

Best,
Sam

2. **Feedback submission**

**Subject:** Re: your proposal feedback

Hi Lena,

Thanks for the note about removing the workshop. I’ll revise the scope and total by 3:00 p.m. tomorrow. The proposal link will stay the same.

One question before I update it: should I keep the written handoff guide in the revised option?

Best,
Sam

Revdoku’s [built-in feedback forms](https://revdoku.com/cases/add-a-feedback-form-without-a-backend/) keep the submission with the bucket and can notify the owner. A consultant can receive a request to remove a workshop, revise the PDF in the same bucket, and confirm it without a new URL. The follow-up addresses explicit feedback, not an inferred objection.

## Proposal Follow-Up Best Practices and Pitfalls

The best messages use the client’s words, make one point, and stop. Before sending, check the **proposal follow-up**:

| Element | Do | Avoid |
|---------|----|-------|
| Subject | Name the project or decision | “Following up again!!!” |
| Opening | Restore context in one sentence | A long recap of your company |
| Value | Clarify one term, option, or next step | An empty “thoughts?” |
| Call to action | Ask one answerable question | Three unrelated requests |
| Analytics | State only verified access or activity | Claims about intent or emotion |
| Cadence | Send two or three useful follow-ups, then pause | Daily nudges with no new value |

## Final Thoughts

To **follow up after sending a proposal**, replace guesswork with a useful next step. Check access when there is no view. Answer recent or repeat views with a relevant question, stating only what the data proves. Clarify pricing when a recorded path or click supports that topic. Answer submitted feedback directly. Then make pausing or closing the deal easy.

Revdoku supports this workflow without code. Add the proposal or folder, choose public, password-protected, or email-gated access, share one stable link, and track views through notifications and visitor analytics. Update the bucket when work changes so the client always has the latest version. The best follow-up is timely, specific, and easy to answer.

## Ask ChatGPT for the follow-up signal

After the link is opened, ChatGPT can summarize Revdoku analytics for the published site. That turns raw viewing activity into a clear follow-up signal.

![ChatGPT summarizes Revdoku analytics for a demo site](/assets/en/blog/follow-up-after-sending-proposal/chatgpt-revdoku-analytics-magic-stories.webp)

Start publishing for free

Connect this AI to Revdoku so it can store files, create, update, and publish websites for me. Read and follow https://revdoku.com/prompt.md. A Revdoku account is required. If I do not have one, send me https://app.revdoku.com/users/sign_up?utm_source=revdoku.com&utm_medium=ai-chat&utm_campaign=connect_ai_first and wait until I confirm signup is complete. For ChatGPT, Claude, or another cloud AI, connect https://app.revdoku.com/mcp and complete Revdoku OAuth. For a local agent, use Revdoku's browser device sign-in and complete the connection in Revdoku. Never ask me for a password or API key in chat, or for a verification code. When Revdoku tools are connected, verify the connection, tell me you’re ready, and ask what I want to publish.

Copy Prompt

or

Create Free Account

## Frequently asked questions

### How many times should I follow up after sending a proposal?

For most client work, two or three messages over 7 to 14 business days suffice: an access check or timely response, one useful clarification, and a close-the-loop email. A firm expiry date or new verified engagement can justify another message.

### Should I tell the client I can see proposal activity?

If so, be direct and calm: “I received an access notification for the protected link.” Do not imply that you watched them read. Email-gated identity is evidence, though forwarding or shared credentials can blur who was present.

### What about email rules?

In the United States, the [FTC says CAN-SPAM covers commercial email, including B2B messages](https://www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business). Use accurate headers and subjects, include the required sender details and opt-out method when the law applies, and honor opt-outs within **10 business days**. Relationship and transactional messages may differ, so seek legal advice for your program and target countries.

### When should I send the first follow-up after a proposal?

If there is no verified view, wait about two business days and check whether the client received and could access the proposal. If an identified client recently opened it, follow up later that day or the next business morning with one relevant question or clarification.

### What should I say if the client has not opened the proposal?

Treat the situation as a possible delivery or access problem rather than a rejection. Reshare the link, ask whether it opens correctly, and offer to send it to another decision-maker if appropriate.

### Should I email a client immediately after receiving a view notification?

Avoid responding within minutes, because the message may feel automated or intrusive. Wait for a natural interval, then connect your follow-up to a specific scope, schedule, or pricing question that could help the client decide.

### Does repeated proposal activity mean the client is ready to approve?

No. Repeat visits, downloads, or pricing-page activity suggest active review, but they do not reveal the client’s intent or decision status. Use these signals to ask a better question, not to claim that you know what the client thinks.

### Which proposal access option should I choose?

Use a public link for low-risk material and the least access friction, a password when entry must be restricted, or an email gate when visitor identification matters. Remember that a password alone does not establish who opened the proposal, while shared or forwarded credentials can make email-based identification imperfect.

### How should I handle proposal revisions after sending?

Update the proposal at the same stable link whenever possible so the client does not have to search for the latest attachment. Confirm what changed, state when the revision will be ready, and ask any necessary clarification before updating it.

### When should I stop following up?

For most proposals, two or three useful follow-ups over 7 to 14 business days are enough. If the client remains silent, send a final message offering clear choices to proceed, revisit later, or close the opportunity, then pause unless new engagement or a deadline justifies another contact.

---

[View the canonical page](https://revdoku.com/blog/follow-up-after-sending-proposal/) · [Browse llms.txt](https://revdoku.com/llms.txt)