Proposal management in a CRM: from draft to signed
Most proposals get sent and then forgotten. Here's how to track proposals inside your CRM so the follow-up is consistent, the timing is right, and nothing disappears into a black hole.
By Sebastian StreiffertPublished Jun 2, 2026Updated Jun 2, 20266 min read
Most proposals get sent and then forgotten. The follow-up gets pushed, the deal goes quiet, and by the time someone checks the prospect has moved on or chosen someone else. Here is how to track proposals inside your CRM so the follow-up is consistent and nothing disappears into a black hole.
The proposal black hole
Most proposals die not with a rejection but with silence. The proposal goes out, the rep waits, a week passes, and the follow-up starts to feel awkward. A CRM fixes this by treating a proposal as a tracked event with a defined lifecycle: proposal date logged, follow-up tasks created at sending, deal record holding the context that makes follow-ups specific rather than generic.
The four stages of a proposal's life in the CRM
- Draft — Qualifying criteria confirmed: budget range, decision-maker, timeline, business problem.
- Sent — Log the exact date. Create the follow-up task the same moment you send.
- Under review — Prospect has acknowledged receipt. Keep light-touch contact.
- Decision pending — Objections identified, remaining stakeholders mapped, final conversation context logged.
The follow-up window
Create three tasks at the moment of sending. Delete unused ones if the deal advances first.
- 48 hours after sending — First follow-up, with something useful (a question, a clarification, a relevant note).
- Seven days — Second follow-up if no response.
- Fourteen days — Situation has changed from follow-up to re-engagement. Adjust tone.
Common proposal management mistakes
- Sending before the deal is qualified on budget, authority, need, and timing.
- Moving deals to proposal stage without logging the qualifying information.
- Not creating follow-up tasks at the moment of sending.
- Generic follow-up messages: "just checking in."
- Not logging the rejection reason when a proposal is declined.
Tracking proposals alongside statements of work
Log both the proposal date and the SOW date as activities on the deal record. The gap between them often reveals internal debate on the buyer's side, useful for forecasting. If you use a signing tool, push the signing event back into the CRM as a note.
Who this is for
Software agencies, consulting firms, and professional services businesses that send custom proposals as part of their sales process. Particularly useful where proposals are long to write, deals are high-value, and a pipeline full of stuck proposals is a forecasting problem.
Frequently asked questions
Should proposals live in a dedicated tool or in the CRM?
Both if you use a dedicated tool. The proposal tool handles formatting and e-signing; the CRM holds relationship context, deal status, and follow-up history. Ideally the proposal tool logs sent/viewed events back into the CRM automatically.
How soon should I follow up after sending a proposal?
Within 48 hours, with something useful. Not "just checking in." A specific question, a clarification, or a relevant note.
How do I track which proposals are at risk of going cold?
Filter your CRM pipeline by last activity date on deals at the proposal stage. Anything with no activity in fourteen or more days and no confirmed response needs attention.
Is it worth sending a proposal if the deal is not qualified?
Usually not. A proposal sent to an unqualified prospect almost always stalls.
What should I track in the CRM after a proposal is rejected?
The rejection reason. Budget not approved, went with competitor, timing not right, decided not to proceed — these are all different situations that call for different re-engagement approaches later.
Was this article helpful?