Back to Blog
RevOpsSales PlanningB2B Sales

How to build a sales plan that survives Q1

Abhishek Singla Sep 08, 2026 12 min read

Every September I get the same kind of message. A founder or a CRO sends over a spreadsheet and asks me to "sanity check the plan for next year." I open it and find a tab with twelve columns, one per month, a row called New ARR, and a growth rate applied to last year's number. Sometimes there is a second tab with headcount. That is the plan.

Then in March the same person messages again, because Q1 came in at 61 percent of target and nobody can agree on why. Was it the quota? The hiring? The pipeline? Marketing? The plan does not answer the question, because the plan never contained an answer. It contained a number.

I have built or rebuilt this document for around thirty B2B companies now, mostly between 20 and 200 people. The ones whose plans hold up all do the same thing: they build the number from the bottom, not the top, and they write down the assumptions in a form that can be checked in six weeks rather than argued about in twelve months.

This is how I do it.

Why last year's number times 1.4 is not a plan

The top-down approach is not wrong because growth targets are wrong. Boards set growth targets, that is their job, and a company with no ambition in the number will hit exactly what it aimed at. The problem is that a top-down number carries no information about whether it is reachable, and no way of telling you early that it is not.

Consider what the number is actually made of. Revenue comes from a certain quantity of selling capacity, converting a certain quantity of pipeline, at a certain rate, over a certain cycle. If any one of those four inputs is off by 20 percent, the output is off, and you find out at the end of the cycle. For a company with a four month sales cycle, that means the mistake you make in December surfaces in April.

The benchmark data on this is grim and getting grimmer. Average B2B SaaS quota attainment has fallen to somewhere around 43 to 47 percent, against a pre-2022 baseline in the 55 to 65 percent range. That is not mostly a talent problem. It is a planning problem. Quotas got set from a revenue target divided by headcount, headcount got hired late, ramp took longer than the model assumed, and the number was mathematically unreachable by February.

The attainment gap
43%

Median B2B SaaS quota attainment in recent benchmarks, down from 55 to 65 percent before 2022. Most plans still assume 100 percent, which is how a 15 percent capacity shortfall turns into a 40 percent revenue miss.

Here is the part that stings. If your plan assumes every rep hits quota and the real world gives you 45 percent attainment, you have not missed by a bit. You have built a company cost structure against revenue that was never going to arrive.

Start with the four numbers, in this order

A sales plan is a chain of dependencies. Build it in the wrong order and you get a document that looks complete and is internally inconsistent. Build it in this order and the errors surface while you can still fix them.

Step 01
Segment
Decide which accounts you are actually selling to and what each one is worth.
Step 02
Capacity
Model selling months by rep, after ramp, attrition, and start dates.
Step 03
Pipeline
Work backwards from bookings to the number of opportunities each source must produce.
Step 04
Quota
Set the rep number last, from capacity and conversion, with attainment assumed below 100.

Most teams do this in reverse. They start with the revenue target, divide by planned reps to get a quota, and then reverse-engineer a pipeline number that makes the arithmetic work. That produces a coverage requirement that marketing has never delivered and nobody flagged.

Step one: segment before you do anything else

You cannot plan capacity without knowing what a deal costs to win, and that varies wildly by segment. A 12,000 euro SMB deal that closes in 21 days and a 180,000 euro mid-market deal that closes in 130 days are different businesses sharing an office.

Pull the last 18 months of closed won and closed lost from your CRM and cut it by company size, industry, and source. You are looking for four things per segment: average deal size, win rate, sales cycle in days, and the number of opportunities you actually created. If your CRM data quality is poor enough that you cannot get these cleanly, that is the first project of the planning season, not an excuse to skip the step.

What usually falls out of this exercise is uncomfortable. One client, a 70 person B2B software company in Berlin, found that their enterprise segment was 34 percent of bookings and 61 percent of AE hours, at a win rate of 11 percent. They had been planning to hire two more enterprise AEs. We moved that headcount to mid-market and their new ARR per rep went up 40 percent the following year without a single new logo in enterprise.

If you have never done this properly, my post on building a data-driven ideal customer profile covers the segmentation work in more depth.

Step two: capacity is measured in selling months, not headcount

This is where almost every plan I audit breaks. The spreadsheet has a headcount row: 8 AEs today, 14 by December. Then it multiplies 14 by the annual quota and calls that capacity.

That number is fiction. A rep who starts in September does not produce a year of selling. They produce roughly one productive month, if you are lucky and the cycle is short.

The unit you want is the productive selling month. For each rep, planned or existing, write down their start date, their ramp period, and their expected productivity curve during ramp. A typical B2B SaaS AE takes three to five months to reach full productivity, and I have written separately about how to measure and shorten rep ramp time. During ramp, assume something like 25 percent of full productivity in month one, 50 in month two, 75 in month three.

Then subtract two things people forget. Attrition, at whatever your real rate has been, applied as a probability that a given seat goes empty mid-year. And hiring slip, because your recruiting pipeline will not deliver on the dates in the plan. In my experience you should assume every planned hire lands four to six weeks later than the plan says. Not because your recruiter is bad, but because that is what the data says every year.

14
AEs on the org chart
104
productive selling months
64
months the plan assumed away

Those numbers are from a real plan I rebuilt in October last year. The original spreadsheet had 14 AEs and multiplied by 12 months, giving 168 selling months. After start dates, ramp curves, and one open backfill, the real figure was 104. The plan was 38 percent overstated before a single conversion assumption was applied.

The capacity model is the single highest-value hour you will spend on the plan. If you want the mechanics in detail, I go through them in the sales capacity planning guide.

Step three: pipeline math, run backwards

Now you have capacity and segment economics. Multiply them and you get an implied bookings capacity. Compare it to the target the board wants. If capacity is short, you have three levers: hire faster, raise win rate, or raise deal size. Pick one and write down what you are going to do about it. Do not close the gap by raising quota, which is the same as closing it with a wish.

Then take the bookings number and work backwards through the funnel per segment:

  • Bookings divided by average deal size gives closed won deals needed.
  • Divided by win rate gives opportunities needed.
  • Multiplied by your real coverage ratio gives pipeline value required.
  • Divided by the number of quarters, offset by the sales cycle, gives when that pipeline has to exist.

That last line is the one people skip and it is the one that matters. Pipeline for a Q2 close with a 100 day cycle has to be created in Q1. If your plan calls for a big Q2 and your Q1 pipeline generation target is flat, the plan is already broken and you can see it in October.

On coverage, please use your own historical number rather than the folk wisdom 3x. I have seen healthy businesses run at 2.2x and unhealthy ones need 6x. The ratio is an output of your win rate and stage hygiene, not a rule. I argue this out properly in the piece on the 3x pipeline coverage rule.

The plan that breaks in March
One revenue number, split evenly by quarter
Headcount counted as bodies, not selling months
Quota set by dividing target by reps
Coverage assumed at 3x because everyone says 3x
Pipeline targets start in the quarter of the close
Reviewed at the end of the year
The plan that holds
Bookings built up per segment from real deal economics
Capacity in productive months after ramp and slip
Quota set from capacity, at 80 to 90 percent attainment
Coverage taken from your own 18 month history
Pipeline creation targets offset by the sales cycle
Six assumptions checked monthly against actuals

Step four: quota comes last, and it is not the target

Quota is a compensation instrument, not a forecast. Those two things get conflated constantly and it causes real damage.

Build quota bottom up from capacity, then check it top down against the company number. The two will not match. The gap between the sum of quotas and the company target is your over-assignment, and you want it there deliberately, usually somewhere between 10 and 20 percent. Most quota models should assume 80 to 90 percent average attainment across the team, not 100.

Set it so that a genuinely good rep in a normal territory can clear it and earn well. If your top quartile is at 130 percent and your median is at 45, the quota is not motivating anyone, it is just a number reps have learned to ignore. My longer treatment of this is in the quota setting and capacity model post, and the pay side sits in sales compensation plan design.

Territory assignment follows quota, not the other way round. If two reps carry the same number and one has the named accounts with existing usage, you have created a fairness problem that will show up as attrition in Q3. The territory planning guide covers how to balance them.

The part everyone skips: write down what would prove you wrong

A plan is a set of predictions. Predictions that cannot be checked are opinions.

So at the bottom of the document, list the six to eight assumptions the whole thing rests on. Not thirty. Six to eight, with the specific number you assumed and the number that would mean you are wrong. Something like:

  • Mid-market win rate holds at 24 percent. Below 19 percent, the pipeline target is wrong.
  • Two AE hires land by 1 February. Later than 1 March, cut Q2 bookings by 340,000.
  • Outbound produces 45 percent of new opportunities. Below 35, marketing spend has to move.
  • Average cycle stays under 95 days. Above 115, Q4 revenue moves to next year.

Then put those in a dashboard and review them monthly. Not the revenue number, which everyone stares at anyway. The assumptions. Because revenue tells you what already happened and the assumptions tell you what is about to.

This is the difference between a plan and a spreadsheet. The spreadsheet gets opened in January and again in December. The plan gets checked in week six, when you discover outbound is producing 28 percent instead of 45, and you still have ten months to do something about it.

I usually set this up as a small set of CRM reports and a monthly automated digest, which is the sort of thing n8n or a scheduled HubSpot report handles fine. It does not need to be sophisticated. It needs to exist and land in someone's inbox on the first Monday of every month. If you want the reporting layer done properly, our CRM and RevOps work is mostly this: making the numbers in the plan visible in the system where the work happens.

What to do with it once it is written

The plan is not a document, it is a series of commitments, and it has to reach the people making them.

Reps need their number, their territory, and their comp plan in writing before 1 January. Not the second week of February, which is when most companies actually manage it, having burned six weeks of selling time on uncertainty. The sales kickoff is the natural forum, but the numbers should be delivered before it, individually, not discovered on a slide.

Marketing needs the pipeline creation targets by segment and by month, offset by cycle length. Finance needs the hiring dates so cost lands in the right quarter. The board needs the assumption list, because that is what makes your board reporting a conversation about the business rather than a defence of a variance.

And the whole thing should be in the CRM, not only in a spreadsheet. Quotas, territories, targets by month. If the plan lives somewhere that never touches the system where deals are worked, nobody will notice it drifting until it has drifted a lot.

Planning season and no capacity model?

Book a free 30 minute session. We will look at your last 18 months of CRM data and tell you whether next year's number is reachable, before you commit to it.

Book a planning review →

The uncomfortable summary

Most sales plans fail because they were never tested. They were negotiated. Somebody wanted a number, somebody else agreed to it, and the arithmetic was fitted around the agreement afterwards.

The fix is not complicated and it is not a tool. Segment your business from your own data. Count selling months instead of people. Work the funnel backwards with your own conversion rates. Set quota last. Write down the six things that would prove you wrong and check them every month.

That takes about two weeks of real work in September or October. It is the cheapest insurance you can buy against a March where nobody can explain the miss.

FAQ

What is the difference between a sales plan and a sales strategy?

Strategy is which markets you sell to and why you win in them. The plan is the operational document that converts that into numbers: segments, capacity, quota, territories, pipeline targets, and the timing of all of it. Strategy changes rarely. The plan gets rebuilt every year and adjusted every quarter. If your plan does not have numbers in it that could be wrong, it is a strategy document wearing the wrong label.

When should we start annual sales planning?

For a January fiscal year, start in early September and aim to have the plan agreed by mid-November. That gives you six weeks for the data work and modelling, four weeks for the negotiation with finance and the board, and the whole of December to communicate quotas and territories so reps start on 2 January knowing their number. Teams that start in November end up delivering comp plans in February, and those lost weeks come straight out of Q1.

How accurate should the plan be?

Aim to be within 10 percent at the quarter level, not the month. Monthly precision in a business with a 90 day sales cycle is mostly noise. What matters is whether the shape is right: whether Q1 pipeline supports Q2 bookings, and whether the capacity curve matches the revenue curve. If you are consistently more than 20 percent out at quarter level, the problem is usually the conversion assumptions rather than the target. Our forecasting models piece goes into how to tighten this.

What do we do if the board target is higher than our capacity model?

Say so, in writing, with the gap quantified and the three options attached: more headcount earlier, a change in segment mix, or a lower number. Then let the board choose. The worst outcome is accepting the target silently and absorbing the gap as quota inflation, because that guarantees low attainment, high attrition, and a miss you cannot explain. I have never seen a board punish a leader for showing the arithmetic. I have seen several punish one for the March surprise.

Should the sales plan include existing customers?

Yes, and separately. Expansion and renewal revenue have different conversion rates, different cycle lengths, and usually a different owner. Model them as their own segment with their own capacity, whether that sits with AEs, account managers, or customer success. Mixing new business and expansion into one number is how companies discover in Q3 that all the growth came from one large renewal and new logo acquisition has been flat for three quarters.

Want a second pair of eyes on next year's plan? Get in touch and we will go through your numbers with you. You can also see how we approach go-to-market and AI automation work.

Second opinion

Wrestling with something like this in your own stack?

Describe the whole problem to us, in total privacy. Within 7 days you get our second opinion in writing: what is actually going on, how we would tackle it, and what we would avoid. We take on a limited number of questions each month.

Ask privately