Sales Goals: Setting Targets the Pipeline Can Actually Reach

Most sales goals are set by the wrong math. A finance team decides the company needs to grow 40 percent, divides that across the headcount it happens to have, and hands each rep a number. Nobody checks whether the pipeline exists to support it. Nobody checks whether the reps are ramped. The goal is published, the kickoff happens, and the miss is already baked in. It just takes three quarters to surface.

A sales goal is a revenue target the team commits to over a set period. A reachable sales goal is one the current pipeline and capacity can actually produce, broken down into the leading indicators that get you there, with an owner on each piece. The gap between those two sentences is where most plans fail. I have built revenue and forecast models for B2B SaaS companies for two decades, and the teams that miss almost always set a number that was never reachable, then spent the year blaming execution for a planning error.

Here is the claim I will defend for the rest of this guide: a goal you cannot trace back to pipeline and capacity is not ambitious, it is fictional, and the most expensive sales mistakes happen at the goal-setting whiteboard, not in the field.

The reachability test

Before any goal gets published, it has to pass one test. I call it the Reachability Test, and it is three questions asked in order. If the goal fails any one of them, it goes back to the whiteboard before it goes to the team.

One. Does the pipeline exist to support it? Take the goal, divide by your realistic win rate, and you get the pipeline you need under coverage. If the goal is 12M in new ARR and you close 20 percent of qualified pipeline, you need 60M in pipeline to support it. If you are sitting on 30M and your build rate is flat, the goal is not reachable from where you stand, no matter how motivated the team is. The number does not care about effort. Two. Does the capacity exist to close it? Pipeline does not close itself. Every deal needs a ramped rep with the room to work it. Count ramped capacity, not headcount, because a rep three weeks into a six-month ramp is a cost, not a closer. If the math needs 14 fully productive reps and you have 9 ramped plus 5 mid-ramp, the goal assumes output that will not exist until the back half of the year. Three. Does the timeline allow it? A goal is a number and a date. If your sales cycle is 100 days, deals you have not sourced yet cannot close inside this quarter. The pipeline you need for Q4 has to exist by the start of Q3. Most goals quietly assume deals will appear and close faster than the cycle physically permits.

A goal that clears all three is reachable. A goal that fails one is a forecast of disappointment with a deadline attached. The trouble is that most teams never run the test, because the goal arrived from above as a fixed input rather than a question to be answered. That is the habit I want to break.

Top-down meets bottom-up

The reason goals fail the reachability test is almost always a single missing step: the company built the goal in one direction only.

A top-down goal starts from what the business needs. The board wants 40 percent growth, so the number is the number, divided across the teams. A bottom-up goal starts from what the field can produce. Each segment and rep has a realistic output given pipeline and ramp, and you add it up. Both directions are correct. Both are also incomplete on their own.

Top-down alone gives you ambition with no reality check. The number reflects what investors expect, not what the pipeline can feed, so it sails past the reachability test untested. Bottom-up alone gives you reality with no stretch. Reps and managers, who own the number, will build a base they are confident they can beat, which sandbags the company into mediocrity. Neither number is the goal. The goal is where they reconcile.

	Top-down	Bottom-up
Starts from	What the business needs to grow	What the field can produce
Owned by	Finance, board, CEO	Sales managers, reps
Strength	Sets real ambition	Grounded in pipeline and capacity
Failure mode	Number the pipeline cannot feed	Sandbagged, beatable base
Answers	"What do we need?"	"What can we deliver?"

The reconciliation is the actual planning work, and it is where the honest conversation lives. When the top-down ask is 12M and the bottom-up build lands at 8M, you have not failed. You have found the real number to solve: a 4M gap, named out loud, with three months to decide how you close it. You close it by adding ramped capacity, lifting win rate on pipeline you already have, shortening the cycle, or, when none of those math out in time, by adjusting the goal before you commit to it rather than after you miss it. A gap you name in planning is a decision. The same gap discovered at quarter-end is a postmortem. This reconciliation is the core of real sales planning, and the bottom-up build leans directly on sales capacity planning to know what the field can actually carry.

The contrarian piece, the one that gets pushback in the room: when top-down and bottom-up will not meet, the answer is more often to fix the goal than to fix the team. A number the pipeline cannot feed does not become reachable because you demand it harder. It just relocates the failure from the plan, where you could still do something, to the field, where you cannot.

A worked example: closing the gap at Quillmark

Numbers below are illustrative, not a benchmark, chosen to show how reconciliation behaves when the two directions disagree.

Quillmark is a mid-market B2B SaaS company heading into planning. The board wants 15M in new ARR next year, up from 10M, a clean 50 percent stretch. That is the top-down ask, and it is fixed before anyone in sales sees it.

Now the bottom-up build. Quillmark closes 20 percent of qualified pipeline, so 15M in new ARR needs 75M in pipeline across the year. The current build rate produces about 55M. Right there, on question one of the reachability test, is a 20M pipeline hole. On capacity, the plan assumes 16 productive reps. Quillmark has 11 ramped and is hiring 6 more, but on a five-month ramp those 6 contribute almost nothing until the second half, so realistic ramped capacity for the year is closer to 13. The bottom-up number, built honestly, lands at 10.5M, not 15M.

The instinct in the room is to publish 15M anyway and "hold the team accountable." That is the move I will argue against every time, because it converts a known planning gap into a guaranteed field miss. The 4.5M difference is not a motivation problem. It is a pipeline-and-capacity problem wearing a motivation costume.

So Quillmark solves the gap instead of denying it. Pulling the 4.5M apart shows three levers. Lift win rate from 20 to 23 percent, concentrated in the segment where deals are already strongest, and the same 55M pipeline produces meaningfully more, because that revenue comes from pipeline already paid for. Pull ramp forward by starting the 6 hires a quarter earlier and tightening onboarding, and more of that capacity lands inside the year. Add a focused pipeline program to close part of the 20M sourcing hole. Stack those and the reachable number climbs to roughly 13M. The honest recommendation to the board is 13M committed with a path to 15M if the pipeline program overdelivers, not 15M asserted on hope. One number is a plan. The other is a press release that comes due in twelve months.

The discipline that makes this work is testing the goal against a live model, not a spreadsheet built once at kickoff and never refreshed. The moment win rate moves or a hire slips, the reachable number moves with it, and you want to see that in week two, not at the QBR.

Break the goal into leading indicators

A reachable goal is still useless if it lives only as a year-end revenue figure. Revenue is a lagging outcome. A rep cannot do anything about 13M in new ARR on a Tuesday in March. The goal only changes behavior once you decompose it into the inputs that produce it, each one a number someone can move this week.

Work backward down the chain. Start at the revenue goal. Divide by win rate to get the qualified pipeline required. Divide pipeline by your stage conversion rates to get the opportunities, the meetings, and the qualified leads that feed it. Now the annual number has become a weekly coverage target, a stage-conversion target, and an activity-quality target, each owned by a specific person at a specific cadence. The goal stops being a wish on a slide and becomes a set of dials the team can actually turn.

This is the bridge from goal to execution, and it is the step most plans skip. They publish the revenue target, then wonder why nothing changes on the ground. Nothing changes because nobody can act on a lagging number. The leading indicators are the goal, expressed in the only language the field can work with. Decide which indicators to track using the discipline in sales KPIs, and pressure-test the conversion math with a pipeline velocity calculator so you know the chain actually produces the number before you commit the team to it.

One warning on the decomposition. Break the goal down by segment before you break it down by rep, because win rate, cycle, and deal size differ across SMB, commercial, and enterprise. A blended assumption applied evenly across reps quietly rebuilds the exact unreachability you just engineered out, by handing an enterprise number to a rep whose pipeline is all mid-market. Segment first, then distribute.

Set the number you can trace

If you take one thing from this, make it the discipline of tracing every goal back to its source before you publish it. A sales goal is not a statement of how much you want. It is a claim about what your pipeline and capacity can produce on a timeline, and a claim like that can be checked. Run the Reachability Test. Reconcile top-down ambition with bottom-up reality and name the gap out loud. Decompose the number into the leading indicators the field can actually move. Do that and the goal stops being a number you hope the team hits and becomes a plan you can defend line by line.

The teams that skip this are why 87 percent of enterprises missed revenue targets in 2025 (Clari Labs, 2026). The miss is rarely a field failure. It is a goal that was unreachable at the whiteboard, set against pipeline that never existed, on a timeline the cycle never permitted. That is also why ORM ties every target back to a live forecast, so the day the reachable number drifts from the committed one, the gap shows up while you still have a quarter to close it.