Proposal rate

A consultancy takes five days on average to send a proposal. During that time, 20% of prospects go dark. They create three proposal templates for common scenarios. Average time to proposal drops to two days and proposal rate increases from 70% to 85%.

A software company sells to a single contact. When that contact goes on holiday or changes role, deals die. They start engaging two to three stakeholders per deal. Proposal rate increases from 65% to 80%.

‍

Calculate proposal rate:

Proposal rate = (Proposals sent / Qualified opportunities) × 100

Track this weekly. Break it down by:

• Deal size (do larger deals stall more?)
• Sales rep (is follow-up consistent?)
• Time in stage (how long before deals get a proposal?)

To improve proposal rate:

• Set clear next steps at the end of every call
• Create proposal templates for fast turnaround
• Follow up within 24 hours of qualification
• Multi-thread into multiple stakeholders
• Track deal velocity and flag stalled opportunities

Proposal rate impacts forecasting accuracy. If you count qualified opportunities as pipeline but only 60% receive proposals, your pipeline is overstated by 40%.

This metric also reveals process problems. A drop in proposal rate usually signals one of these issues:

• Sales cycle is too long
• Follow-up is inconsistent
• Competitors are faster
• Proposals are too hard to create
• Wrong stakeholders are being engaged

Improving proposal rate means more deals reaching the decision stage. Combined with a healthy win rate, this translates directly to revenue.

Proposal rate measures how many of your qualified opportunities actually get a proposal in front of them. You divide proposals sent by qualified opportunities, then multiply by 100. A proposal rate of 80% means that for every 10 qualified deals, eight got a proposal.

This metric sits between qualification and the close. In theory, a deal you've qualified should earn a proposal. So if the rate is low, something is quietly breaking down in that gap, and that's usually where money leaks.

Say you're running your pipeline in Pipedrive. You set a 'Qualified' stage and a 'Proposal Sent' stage, then watch the count drop between them. If 30 deals hit Qualified but only 12 reach Proposal Sent, your proposal rate is 40%, and that's a flashing light, not a footnote.

The usual culprits: prospects go dark after discovery, your champion loses momentum, a competitor gets there first, or your process drags and interest cools. A slow proposal step is often the real villain. Say you build proposals in PandaDoc from a template instead of writing each one from scratch, the turnaround shrinks from days to hours, and fewer deals die waiting.

Proposal rate exposes process friction. A healthy pipeline pushes qualified deals to proposal fast. A leaky one loses them on the way.

A B2B company has no visibility into how long deals sit in each stage. They implement stage duration alerts. Deals over 14 days in the qualified stage get flagged for follow-up. Proposal rate increases from 60% to 75%.