The scene
You hit send. The work isn’t really finished.
The proposal is in the client’s inbox. It lays out the scope, timing and terms you have just clarified on a call. From the other side comes a “thanks, I’ll take a look and let you know”.
It’s a normal thing to say, not a refusal. But if the next step isn’t decided now, in a few days that proposal becomes one more indistinct line in your Sent folder. To pick it up again you’ll have to remember what really mattered, which doubt was left and when it made sense to write back.
Before you close
Three details protect the next contact.
You don’t need to build a complex pipeline. You only need to leave the job enough context to be reopened without starting from scratch.
The method
Follow-up timing comes from the conversation, not from a formula.
If the client has to talk it over with a partner, the next move can be to offer clarification after that meeting. If a technical detail is missing, it can be sending it before the decision stalls. If you agreed on an answer by a certain date, the reminder should keep that promise.
This avoids two extremes: writing too early with an empty message, or waiting until the proposal goes cold. The follow-up stays professional because it continues the conversation instead of reopening it from the start.
With Avanlio
Document, client and next step stay on the same thread.
Avanlio is built so that a proposal doesn’t live apart from the relationship that produced it. You can keep the client, the job, the document and the thing to do next close together. Assist can prepare a follow-up suggestion from the sources you choose, but it sends nothing and changes nothing in your work without a clear confirmation.
The benefit isn’t automating the relationship. It’s reaching the right moment already knowing what happened and which move might help.
If you want to start even earlier, also read how to turn a call into a readable next step. Or see how Avanlio works for freelancers and consultants.
Questions
Short answers.
What is worth setting as soon as you send a proposal?
What you sent (the right version, tied to the client and the job), what still needs to become clear, and when and why to get back in touch.
When should you follow up on a proposal?
When it makes sense given the conversation: after the meeting with a partner, before it stalls over a technical detail, or on the agreed reply date.
Do you need a complex pipeline for this?
No. Just leave the job enough context to be reopened without starting from scratch.