Proposal management in a CRM: from draft to signed

The four stages of a proposal's life in the CRM

A proposal is not a single event. It is a sequence of stages, each with its own timing, risks, and required actions. Tracking these stages in the CRM makes the difference between a managed process and a best-guess one.

The follow-up window: timing that actually works

Most buying decisions happen faster than reps think, or much slower. The first 48 hours after a proposal is sent is the highest-engagement window. The prospect has read it recently, it is fresh in their mind, and a quick follow-up with something useful is welcome rather than intrusive.

After that, the window shifts. A follow-up at seven days is appropriate if there has been no response. By day fourteen, if there is still no signal, the situation has changed. It is no longer a follow-up; it is a re-engagement. The message needs to change accordingly: less 'checking in on the proposal,' more 'happy to revisit when the timing is better' or 'is there a question I can answer.'

The CRM makes this automatic when the tasks are created at the right moment. The moment you send the proposal, you create three tasks: 48 hours, seven days, fourteen days. If the deal advances before any of those tasks fire, you delete them. If it does not, the tasks remind you to act before the window closes.

Common proposal management mistakes

• Sending before the deal is qualified. A proposal sent to an unqualified prospect almost always stalls. The prospect gets something detailed and well-written and then feels vague pressure to respond to something they were not ready for. Qualify first: budget, authority, need, timing. The proposal should confirm a decision the prospect has already made internally, not start it.
• Moving the deal to proposal stage without logging the qualifying information. If the CRM shows a deal at proposal stage with no notes on the contact, no known stakeholders, and no close date, the stage means nothing. The proposal stage should be a gate, not just a label. Before moving a deal there, check that the record has the information you would need to write a good proposal and a persuasive follow-up.
• Not creating the follow-up task at the moment of sending. Following up feels optional the day you send the proposal. It feels urgent ten days later when you realize you have heard nothing. Create the follow-up task in the CRM before you close the email. Set the date for 48 hours out. Set a second task at seven days. You will not remember to do this later.
• Generic follow-up messages. 'Just checking in on the proposal' is not a follow-up. It is a reminder that you sent something. A follow-up adds something: a question, a relevant piece of information, a clarification the prospect might have been wondering about. Look at the last conversation notes in the CRM before you write the message. That is usually where the relevant hook is.
• Not logging the rejection reason. A rejection without a logged reason is a missed learning opportunity. If you know that three of your last five proposals stalled because of budget approval delays rather than interest, that tells you something about where to qualify harder. That data lives in the deal record, not in memory.

Tracking proposals alongside statements of work

For software agencies and consulting firms, proposals often evolve into statements of work before a deal closes. These are different documents with different purposes: the proposal makes the business case, the SOW defines the scope and terms. Both belong in the CRM.

The most useful approach is to log both as activities on the deal record, with dates. The proposal date tells you when the commercial conversation became serious. The SOW date tells you when the scope was agreed. The gap between them often reveals something about the deal: a long gap between proposal and SOW usually means there was internal debate on the buyer's side, which is worth knowing for forecasting.

If you use a dedicated tool like PandaDoc or DocuSign for SOW signing, the signing event is worth pushing back into the CRM as a note on the deal. That creates a clean record: proposal sent, SOW issued, SOW signed, project started. Whoever handles account management after the close starts from a full picture of how the deal came together.

How Lumenbase supports proposal tracking

• Deal record as the single source of truth. The deal record in Lumenbase holds the full timeline: the qualifying conversation, the proposal date, follow-up notes, stakeholder contacts, and rejection reason if it comes to that. When a deal reappears six months later, whoever picks it up starts from the full picture.
• Activity timeline on the company record. Proposal activity logs against the company, not just the deal. If the same company comes back with a different opportunity, the previous proposal history is visible on their company record even if the original deal is closed. That context shapes the next approach.
• Tasks linked to deal and contact. A follow-up task in Lumenbase links to the specific deal and contact. When the task is due, you open it and see the deal stage, the last note, and the contact history in one view. The follow-up message writes itself from that context.
• Stage-based pipeline view. Filter your pipeline by deal stage to see all proposals currently out. Sort by last activity date. That view tells you, in thirty seconds, which proposals are active and which are going cold. You do not need a separate spreadsheet to track this.

Who this is for

Software agencies, consulting firms, and professional services businesses that send custom proposals as part of their sales process. Particularly relevant for firms where proposals are long to write, deals are high-value, and a lost proposal represents a significant cost. If your pipeline regularly shows deals stuck at the proposal stage and you are not sure which ones are actively being reviewed and which have quietly died, this is the system that creates that visibility.

Frequently asked questions