Pipeline math and rep pacing for MSP sales teams

Start with the revenue target and work backward through your own stage-to-stage conversion rates. The result is the deals, opportunities, meetings, conversations, and calls your team needs. Then measure each rep against the days they have worked so far this week. I run my team this way at Five Nines Technology Group. This is the method.

How do you work backward from a revenue target to the activity a rep needs?

Divide the target by your average deal size, then divide each stage by the conversion rate of the stage before it. Each division gives the volume the previous stage must produce.

The chain looks like this: target, deals, opportunities, held meetings, conversations, calls. Here is an example with hypothetical round numbers. They are made up for teaching. Replace every one with your own.

Spread 6,000 calls over 13 weeks and you get about 460 a week for the team. If four reps share the work, that is about 115 calls each per week.

Now you can test the target. If 115 calls a week is more than a rep can physically dial, the target is too high for the team you have. You find that out in planning, before the quarter starts.

I built a live Sales Funnel Calculator that does this math from documented conversion rates, so coverage and activity targets come from a model. If you are sizing a BDR seat, the business case for a BDR uses the same inputs.

How do you build a conversion-rate baseline you can trust?

Define each stage in writing, pull history from your CRM, and keep one shared set of rates that the whole team uses.

1. Define the stages. Write one sentence for each: what counts as a conversation, a held meeting, or an opportunity. Three stages is enough to start. If two reps read a stage differently, your rates mean nothing.
2. Pull history from the CRM. Count how many records entered each stage and how many moved to the next one. Use records that have had time to resolve. A deal opened last week has not had its chance to close.
3. Use enough history to smooth out noise. Take at least a few quarters if your deals are slow, so one big win or one bad month does not set the rate. Check how many records sit behind each rate. A rate built on a handful of deals is a guess.
4. Keep it maintained. Refresh the rates on a schedule, such as every quarter, and note the date. Rates drift as your market and your team change.
5. Share one baseline. Everyone works from the same numbers. When the AE team and the BDR team use different rates, every planning meeting turns into an argument about the inputs.

If the CRM data is messy, fix the stage definitions first. The rates will follow.

What pipeline coverage should you carry?

Carry the inverse of your close rate. In the example above, 25% of opportunities close, so you need 4x coverage: $1.2M of open pipeline to hit $300,000.

The check: 48 opportunities at $25,000 each is $1.2M, and a quarter of them close for $300,000.

You will often hear 3x quoted as a rule of thumb. It only works if one in three opportunities closes. If your close rate is 20%, you need 5x. If it is 50%, you need 2x. Your own rate is a better source than any round number, because it already reflects your deal size and your sales cycle.

Two adjustments make the number more honest:

• Count only pipeline that can close inside the period. Opportunities with a close date next year do not cover this quarter.
• Compute the rate by stage if you can. A deal in late evaluation closes more often than one that was opened yesterday, so late-stage pipeline needs less coverage.

What is day-prorated pacing, and why is it fairer?

Day-prorated pacing measures a rep against the target for the days that have passed. On Tuesday evening, a rep with a 100-call weekly target is on pace at 40 calls.

A flat weekly target makes every rep look behind on Monday and Tuesday. Reps learn to ignore the red numbers. Prorating fixes the signal, so red means something.

The formula is: weekly target x (working days elapsed / working days available this week).

Handle the edge cases in the same formula:

• Holidays. A four-day week has four days available. The weekly target shrinks to four-fifths, and each day carries a quarter of it.
• PTO. Count only the days the rep was scheduled to work. A rep out Monday has four days available. After two worked days, the pace target is half the weekly target.
• Partial weeks. For a new hire or a mid-week start, count from the start date.

My Sales Command dashboard shows AE and BDR scorecards with this pacing built in. Each rep sees how they stand against the days that have passed.

What is weighted scoring?

Weighted scoring gives more credit to actions that sit closer to revenue. A closed deal counts for more than a call.

Raw activity counts reward volume. A rep with 150 low-quality dials outscores a rep with 80 dials and three good meetings. Weights fix that.

You can derive the weights from the funnel above. Using the hypothetical rates, a conversation takes 10 calls to produce, a held meeting takes 50, an opportunity takes 125, and a deal takes 500. Set the points to match:

Round them for readability and review them when you refresh the baseline. Sales Command uses weighted period scoring, and the same idea applies on a spreadsheet.

What should a dashboard do when the data fails?

It should show an error. A broken query must never appear as a zero.

A zero looks like a fact. If the CRM connection drops and a rep's meetings show as 0, a manager may coach on a problem that does not exist. Or a leader may quote the number to a board. After that happens once, nobody trusts the dashboard again, and people go back to asking for spreadsheets.

I hardened Sales Command so a failure produces an error banner. That includes retry logic and query batching, so a brief API hiccup recovers on its own. When it cannot recover, the page says so. Build the same rule into whatever you use: a number is either correct, or it is labeled as unavailable.

What belongs in the board view and what belongs in the rep view?

The rep view shows what a rep can change today. The board view shows whether the plan is on track.

Rep view: - Activity against the day-prorated pace - Weighted score for the week - Their own meetings, opportunities, and open deals - Which of their targets they have not touched

Board view: - Attainment by week and by month - Pipeline coverage against the target, computed from your baseline close rate - Performance against your stated sales standards - Stalled deals, listed by name - A format the board already reads, with a one-click PDF

I built both. Sales Command includes individual rep pages, a leadership-only insights view, a standards page benchmarked against the sales model, a weekly tracker in the board's own format, and PDF exports. Monday-morning alerts flag stalled deals and untouched targets before they cost a quarter.

Keep coaching detail out of the board view. A board needs the trend and the exceptions.

Your first step this week: write the stage definitions on one page and pull the last few quarters of stage counts from your CRM.

About the author. Steven Bartz is Director of Sales at Five Nines Technology Group, a managed IT partner in Lincoln, Nebraska. He sets his team's targets from a maintained conversion-rate baseline and paces reps against the days they have worked.