A proposal usually follows a good conversation. The buyer has shared a problem, your team has explained a plan, and someone has put the scope in writing. Then the document goes out and the week fills up. That is where follow-up often becomes vague.
Write down what the buyer cared about before you send.
The proposal is a summary of the work. The follow-up should use the reason the buyer wanted the work in the first place. It might be a launch date, a team bottleneck, a cost they want to control, or a result they need before the next planning cycle.
Keep that detail in the account record. It gives the person following up a real reason to write. It also means the next email can sound like it came from someone who was in the meeting.
Set the next step while the call is still fresh.
You do not need to force a decision on the call. You do need to agree on what happens after the proposal arrives. Ask when the buyer expects to review it, who else needs to see it, and what question would block the deal. That gives the follow-up a useful date and a useful topic.
A proposal has more value when the team knows what the buyer is doing after they receive it.
Follow up with the context, not the attachment.
“Checking in” gives the buyer very little to respond to. A better message refers to the decision they were trying to make. It can ask whether the proposed timeline still works or whether the internal review raised a specific question.
Keep the message short. The buyer already has the proposal. Your job is to make the next conversation easier to start.
Update the record when something changes.
When the buyer replies, the account owner needs the full picture. Put the reply in the CRM, share the key point with the team, and add the next meeting if one is scheduled. This is basic sales work, but it often slips when the person who sent the proposal is handling several accounts at once.
I would treat the days after a proposal as active account work. The proposal set the conversation up. The follow-up decides whether it keeps going.