Proposal Follow-Up Emails
When To Use
Ten days since you sent it. You have written "just wanted to check in" three times and deleted it three times. The client is not ignoring you so much as lacking a reason to answer today. Run this to give them one: a message that hands over something useful, then another, then a graceful exit.
When Not To Use
If the call was today and no proposal has gone out, send the Discovery Recap Email. If the client said yes and the quiet came afterwards, the steps are stuck and not the conversation; use Mutual Action Plan.
Inputs
- The proposal, the date it went out, and the thread
- Your call record, especially the questions the client left open
- Real material you could share: an answer you now have, a true example from past work, a smaller first phase
If you have none of this beyond the proposal, I start from it and mark each follow-up as a first draft waiting for one useful thing from you. With the Gmail connector I read the thread; I write here and you send.
Approach
The rule is a practitioner convention, described generically: a message must have a reason to exist that is useful to the reader. "Any news?" puts the work on the client and teaches them your emails can wait. A message that answers the question they asked on the call gets opened. The failure it prevents is the fourth "bumping this up", after which the client is too embarrassed to reply at all.
Workflow
- Ask, in one go: when did the proposal go out, and what was said about timing? Which questions did the client leave open? What real material do you have to share?
- Look through the thread and notes for useful reasons, in this order: an answer to a question they asked, a true example from your own work that matches their situation, a smaller scope or first phase they could accept. One reason per message; a second strong one waits for the next.
- Draft the first. The subject names their topic, never "following up". The useful thing is in the first line, told in a few sentences, and the message closes with one easy question. No summary of the proposal.
- Draft the second the same way on a different reason. If it offers a smaller first phase, describe it in their words and leave any fee as [your price].
- Draft the close-the-loop note: brief and warm, says you will take it that the timing is wrong, leaves the door open, with no guilt and no deadline you do not mean.
- Check each draft against the list of things to avoid: "just checking in", "bumping this", "circling back", invented urgency, invented scarcity. The spacing is yours to choose; I schedule nothing and send nothing.
Output Format
# Follow-Up Drafts
Proposal sent: [date] · Timing the client mentioned: [their words]
## First follow-up (to send around [your date])
Subject: [their topic]
[Draft: lead with the useful thing, close on one easy question]
Useful reason: [open question answered / real example / smaller first phase]
## Second follow-up (to send around [your date])
Subject: [their topic]
[Draft]
Useful reason: [a different one]
## Close-the-loop note (to send around [your date])
[A brief draft that keeps the door open]
## Decision
[You] decide whether each draft goes, and on which day, starting by [date]; you send every one yourself.
Done When
- Each follow-up carries one useful thing taken from your notes or material
- None opens with a phrase from the avoid list, and none invents urgency
- The closing note is short and leaves the door open
- Dates stay as placeholders until you set them
Quality Bar
- The first line gives; any asking comes last
- Examples are real work you supplied, never made up to fill a slot
- A figure, fee or result is yours or stays a [placeholder]
- No automation, no mass sending, no scheduled sequence
- Drafts only, built from your material with nothing invented; you choose the dates and send every message.
Next
Run firm-client-decision-brief (Client Decision Brief) to give your contact a fair page to argue from inside.
About the makers
This pack is made by 90n (90n.ai): AI-native ways of working and tools for Product, Marketing and HR teams, built by ex-McKinsey founders. We map where time and money leak, redesign the work around AI and stay until your people run it themselves, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).
1---2name: firm-proposal-follow-up3description: Drafts two proposal follow-up emails that each bring one useful thing (an answer to an open question, a real example, a smaller first phase), then a short close-the-loop note, as drafts only, with the dates and the sending left to you. Use for "run firm-proposal-follow-up", "follow up on my proposal", "no reply to the proposal", "my proposal went quiet", "how do I follow up without nagging", "anything but just checking in", "write a close the loop email", part of the Claude for Consultants · Team in Claude Pack by 90n.4metadata:5 source: https://skillmd.com/skills/polar-bear-org/firm-proposal-follow-up6---78# Proposal Follow-Up Emails910## When To Use11Ten days since you sent it. You have written "just wanted to check in" three times and deleted it three times. The client is not ignoring you so much as lacking a reason to answer today. Run this to give them one: a message that hands over something useful, then another, then a graceful exit.1213## When Not To Use14If the call was today and no proposal has gone out, send the Discovery Recap Email. If the client said yes and the quiet came afterwards, the steps are stuck and not the conversation; use Mutual Action Plan.1516## Inputs17- The proposal, the date it went out, and the thread18- Your call record, especially the questions the client left open19- Real material you could share: an answer you now have, a true example from past work, a smaller first phase20If you have none of this beyond the proposal, I start from it and mark each follow-up as a first draft waiting for one useful thing from you. With the Gmail connector I read the thread; I write here and you send.2122## Approach23The rule is a practitioner convention, described generically: a message must have a reason to exist that is useful to the reader. "Any news?" puts the work on the client and teaches them your emails can wait. A message that answers the question they asked on the call gets opened. The failure it prevents is the fourth "bumping this up", after which the client is too embarrassed to reply at all.2425## Workflow261. Ask, in one go: when did the proposal go out, and what was said about timing? Which questions did the client leave open? What real material do you have to share?272. Look through the thread and notes for useful reasons, in this order: an answer to a question they asked, a true example from your own work that matches their situation, a smaller scope or first phase they could accept. One reason per message; a second strong one waits for the next.283. Draft the first. The subject names their topic, never "following up". The useful thing is in the first line, told in a few sentences, and the message closes with one easy question. No summary of the proposal.294. Draft the second the same way on a different reason. If it offers a smaller first phase, describe it in their words and leave any fee as [your price].305. Draft the close-the-loop note: brief and warm, says you will take it that the timing is wrong, leaves the door open, with no guilt and no deadline you do not mean.316. Check each draft against the list of things to avoid: "just checking in", "bumping this", "circling back", invented urgency, invented scarcity. The spacing is yours to choose; I schedule nothing and send nothing.3233## Output Format34```markdown35# Follow-Up Drafts36Proposal sent: [date] · Timing the client mentioned: [their words]37## First follow-up (to send around [your date])38Subject: [their topic]39[Draft: lead with the useful thing, close on one easy question]40Useful reason: [open question answered / real example / smaller first phase]41## Second follow-up (to send around [your date])42Subject: [their topic]43[Draft]44Useful reason: [a different one]45## Close-the-loop note (to send around [your date])46[A brief draft that keeps the door open]47## Decision48[You] decide whether each draft goes, and on which day, starting by [date]; you send every one yourself.49```5051## Done When52- Each follow-up carries one useful thing taken from your notes or material53- None opens with a phrase from the avoid list, and none invents urgency54- The closing note is short and leaves the door open55- Dates stay as placeholders until you set them5657## Quality Bar58- The first line gives; any asking comes last59- Examples are real work you supplied, never made up to fill a slot60- A figure, fee or result is yours or stays a [placeholder]61- No automation, no mass sending, no scheduled sequence62- Drafts only, built from your material with nothing invented; you choose the dates and send every message.6364## Next65Run firm-client-decision-brief (Client Decision Brief) to give your contact a fair page to argue from inside.6667## About the makers6869This pack is made by 90n ([90n.ai](https://90n.ai)): AI-native ways of working and tools for Product, Marketing and HR teams, built by ex-McKinsey founders. We map where time and money leak, redesign the work around AI and stay until your people run it themselves, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).