Annual Sales Planning: 5 CRM Reports to Pull First

Here is a scenario that plays out in conference rooms every fall. Leadership is debating whether to set next year's revenue target at $3M or $4M. The CFO wants the higher number. The head of sales thinks it is achievable but wants to check the math. Someone asks whether the CRM can answer the question.

Silence. Then a slow scroll through the sales dashboard that nobody fully trusts.

Most companies use the CRM as a daily deal management tool and a board-meeting prop. They almost never use it as a planning database. The data to answer "is $4M achievable?" is sitting right there: win rates, deal sizes, cycle lengths, rep productivity, coverage ratios. But nobody has ever run the reports that would surface it.

Annual planning defaults to gut instinct and top-down math because nobody set up the CRM to answer planning questions. This guide covers what to fix and what to pull.

Why Annual Plans Fail by February

There is a predictable failure pattern for sales plans built without CRM analysis. The target gets set top-down: revenue goal divided by average deal size divided by assumed win rate. The assumptions are optimistic. The plan ships.

By February, the head of sales is looking at a pipeline that is already 30% under the coverage ratio they need, with reps who are already 25% behind their quarterly pacing. The plan was not wrong because the team underperformed. It was wrong because the inputs were wrong.

Specifically: the assumed win rate did not match the actual win rate in the CRM. The assumed average deal size included outlier deals that are not repeatable. The assumed sales cycle length did not account for how long enterprise deals actually take to close, which means Q1 pipeline was never going to close in Q1.

The fix is not a better spreadsheet. It is pulling the real numbers before the planning conversation starts.

The 5 CRM Reports to Pull Before Setting Targets

1. Win Rate by Pipeline Stage

This is the most important report most teams never look at. Not your overall win rate, but stage-to-stage conversion: what percentage of deals move from qualified to proposal, proposal to negotiation, negotiation to closed-won.

Overall B2B win rates vary by company size and deal type, but HubSpot's 2025 State of Sales survey puts average B2B win rates in the 21-28% range depending on segment and deal size. Your number may be higher or lower, but the stage breakdown matters more than the summary.

Why: a rep with a 40% close rate who only reaches negotiation on 15% of qualified deals is a very different problem than a rep with a 40% close rate who reaches negotiation on 50% of qualified deals. The first problem is discovery and qualification. The second problem is negotiation. You need the stage data to know which coaching or process investment to make.

In HubSpot, pull this from the Deals pipeline report with stage-to-stage conversion enabled. In Salesforce, the Opportunity Funnel report gives you the same breakdown. In Pipedrive, the conversion rate report under Pipeline gives it by stage.

For planning purposes: use the stage conversion data to build a credible pipeline coverage model. If your overall win rate from qualified to closed is 22%, you need roughly 4.5x the pipeline at the qualified stage to hit a given revenue target.

2. Average Deal Size by Segment and Lead Source

Your average deal size at the aggregate level is almost certainly pulled up by outliers. One $200K enterprise deal in a year of $30K average deals makes the plan look more exciting than reality.

Segment the average deal size by:

• Company size (SMB, mid-market, enterprise by headcount or revenue)
• Lead source (inbound vs outbound, referral, partner)
• Product or service line if you sell multiple things

This tells you where your real revenue comes from, which is often not where leadership assumes it does. A company doing $2M in annual revenue may find that 60% comes from a narrow band of mid-market, inbound deals that your sales process is tuned for, with the other 40% coming from expensive, time-consuming enterprise deals that produce a worse ROI than they look like.

Build next year's revenue model from the deal types that actually close, not the deal types you wish closed more.

3. Median Sales Cycle Length by Deal Type

This report determines whether your quarterly projections are physically achievable.

If your median sales cycle for enterprise deals is 127 days from qualified to closed, then a deal that enters the pipeline in October will not close until February on average. If your Q4 plan assumes $500K from enterprise deals sourced in October, you need to check when those deals were actually sourced to be sure the math works.

Seasonality compounds this. Q4 often delivers a disproportionate share of annual revenue for B2B companies, since many buyers have budget to spend before year end. But the deals that close in Q4 were typically sourced in Q2 or Q3. Planning as if Q4 prospecting fills Q4 quota produces systematic misses.

Pull sales cycle data by deal type and segment from your CRM. In HubSpot, this is available under Reports as the "Time in pipeline stage" report. In Salesforce, the Opportunity History report gives you the date each deal entered each stage. Calculate median, not mean, to avoid distortion from outlier deals that stalled for two years.

For capacity planning: back-calculate when pipeline needs to be built based on when revenue is needed. If you need Q2 revenue, your reps need to be sourcing it in Q4 of the prior year.

4. Rep-Level Quota Attainment History

A plan that assumes all reps hit 100% of quota will be wrong. The question is by how much.

Historical attainment data tells you the distribution. You may find that your top three reps consistently hit 120-130% of quota while the bottom two consistently hit 60-70%. The aggregate looks fine, but the individual variance matters for capacity planning and for understanding what a realistic top-line target actually implies at the rep level.

For new hires and ramping reps, factor in ramp time. A new AE in a mid-market B2B environment typically takes three to five months to reach full productivity. A plan that assumes a January hire contributes full quota from day one will overshoot.

Pull this data from your CRM's quota reporting. In HubSpot, quota tracking lives in the Sales Dashboard under the Forecast module. In Salesforce, the Forecasting module tracks attainment against quota by rep. If you have not been tracking quota formally, use closed-won deal volume by rep as a proxy for what each rep realistically delivers.

5. Historical Pipeline Coverage Ratio

The standard rule is that you need 3x pipeline coverage to hit your revenue target, because a 33% overall win rate means roughly two out of three deals will not close. But your actual required coverage is 1 divided by your actual win rate, not a generic multiplier.

If your win rate is 20%, you need 5x coverage. If it is 35%, you need roughly 3x. The ratio is specific to your pipeline and your team. You can use the pipeline coverage calculator to run these numbers against your actual figures.

The planning question is whether you built sufficient coverage historically. Look back at the start of each quarter for the past two to three years and compare how much pipeline was in the CRM at that point to what actually closed by quarter end. This tells you:

• Whether your team was consistently underpiplined, overpipelined, or accurately covered
• Whether the coverage ratio you need is consistent across quarters or varies by season
• Whether certain deal types produce better coverage efficiency than others

This report is available in most CRMs through a historical pipeline snapshot, though it requires having kept historical data (CRM data that was deleted or overwritten cannot be reconstructed). If the data exists, it is one of the most valuable inputs for setting quarterly coverage targets next year.

How to Use These Reports in the Planning Conversation

Pulling the reports is step one. The planning conversation needs a structured way to use them.

A practical sequence:

Start with win rate and deal size to set a unit economics baseline. If your historical win rate is 23% and your median deal size in your primary segment is $42K, you have a repeatable unit of production to plan around. A rep who generates 150 qualified deals per year and converts at 23% closes roughly 34 deals at $42K each, or about $1.4M. That is a credible baseline, not a hope.

Use sales cycle data to validate quarterly pacing. Take the baseline and back it into a quarterly pipeline build schedule. If your median cycle is 90 days from qualified to closed, a deal sourced in January will close in April at the earliest. Your Q1 revenue comes from deals already in pipeline from Q4 of the prior year. Build the sourcing calendar around this reality, not the other way.

Stress-test the plan against coverage history. If your historical coverage at quarter-start has averaged 2.8x and your win rate requires 4.3x, you have a structural problem that no amount of sales management will solve without changing the top-of-funnel volume. Identify the gap explicitly before the plan finalizes, not in the March QBR.

Set rep quotas from attainment history, not from division. Dividing the total target by headcount produces quotas that ignore individual variance. Use historical attainment to weight quotas, give ramping reps realistic targets for their first two quarters, and build in a meaningful overperformance incentive for your top performers.

The Data Quality Problem

There is a catch that almost every planning team runs into: the CRM data is only as good as the process that produced it.

If deals were left in active stages rather than being closed-lost when they went dark, your win rate looks inflated. If deal amounts were entered as estimates and never updated to reflect the actual contract value, your average deal size is wrong. If sales cycle length was calculated from deal creation date rather than from qualified date, it includes the time deals sat in prospect stages before anyone worked them.

Before running the planning reports, do a quick data audit. Look at:

• Open deals with no logged activity in 90 or more days (likely zombie deals that should be closed-lost)
• Deals with amount fields that were never updated from the initial estimate
• Deals where the stage has not changed in 60 or more days without a clear reason

A CRM data hygiene audit before planning season is not optional if you want numbers you can defend. Every zombie deal inflating your win rate is a future planning error.

When the Data Tells You Something Uncomfortable

Sometimes the CRM data will tell you that the leadership target is not achievable with the current team and current pipeline coverage. That is useful information, not a problem to suppress.

The right use of that finding is to surface it early, in August or September when there is still time to adjust the target, add headcount, or shift the mix toward faster-closing deal types. Surfacing it in December, after the plan has been approved by the board, creates a year of painful conversations.

The win rate data, the sales cycle data, and the coverage history together make an honest case for what the team can realistically deliver. If leadership wants a target above what the data supports, they need to also commit to the investments: new headcount, additional top-of-funnel spend, a process change that genuinely improves conversion.

For a detailed look at how sales pipeline analysis connects to quarterly forecasting, the sales pipeline gap analysis framework covers how to identify and close the spread between what you need and what you have.

Building the Habit

Annual planning with CRM data is not a one-year project. The value compounds because each year's plan is validated against actuals, which improves the assumptions for the next cycle.

The teams that are best at this treat planning data the same way they treat pipeline data: something to inspect, challenge, and maintain on an ongoing basis, not something to pull in a panic in October and hope is clean enough to be useful.

That means a clean CRM is not a RevOps nicety. It is the foundation of any plan worth defending.

Frequently Asked Questions

When should you start pulling CRM data for annual sales planning?

Most RevOps teams begin extracting historical CRM data in August or September to give leadership enough time to review, model scenarios, and finalize targets before the fiscal year begins. Waiting until November leaves too little runway to fix data gaps or renegotiate unrealistic quotas before they go live.

What CRM reports matter most for annual sales planning?

The five most actionable reports are win rate by pipeline stage, average deal size by segment or lead source, median sales cycle length by deal type, rep-level quota attainment, and historical pipeline coverage ratios. Together they tell you what your team actually produces, not what leadership hopes it will produce.

How do you set sales quotas using historical CRM data?

Build bottom-up. Take each rep's closed-won volume from the prior year, adjust for known changes (territory shift, product expansion, ramp time), and back into the pipeline coverage you will need to generate given your measured win rate. A rep who closed $500K last year at a 22% win rate needed roughly $2.3M in pipeline to get there. That ratio does not change much year over year unless your process does.

What is the difference between top-down and bottom-up quota setting?

Top-down quota setting starts from a revenue target set by leadership or investors and divides it among reps and territories. Bottom-up starts from what each rep historically produces and builds a realistic aggregate. CRM data makes bottom-up credible: you are arguing from attainment history, not optimism. The two approaches usually meet in the middle during negotiation.

How do stale CRM records distort annual planning?

If your CRM win rate is calculated from a pipeline full of zombie deals that were never formally closed-lost, your rate will look better than reality. If average deal size includes outlier enterprise deals that do not recur, your plan will be built on an unrepeatable number. Cleaning pipeline data before the planning cycle starts is not busywork. It is the difference between a plan you can defend and one that falls apart by February.