How to Build Your Company's Sales Scorecard: From Annual Goal to Your Team's Weekly Activity
A sales scorecard is the table that converts your annual revenue goal into measurable weekly activity per person. You build it by reverse-engineering: divide the goal by your average deal size to get the number of deals you need, then run your conversion rates backward through the funnel until you land on numbers each rep can actually control week to week.
Let me use a concrete example throughout. Take a B2B SaaS company with a 600,000 dollar new-revenue goal and a 12,000 dollar average contract value. That is 50 deals a year, which, run backward through the funnel, becomes 150 proposals, 300 discovery meetings, and 3,750 leads over the year, or roughly 78 leads and 16 qualified leads (MQLs) per week for the team to hit. Revenue is the output. Activity is the only input you can manage today.
The approach here comes from the revenue-architecture method I use with clients: revenue is the result of a measurable process, and if you know your stage-to-stage conversion rates, you can calculate exactly how much top-of-funnel activity produces how much bottom-of-funnel revenue.
What is a sales scorecard, and why do you build it backward?
A sales scorecard is a table of numeric targets by funnel stage, by person, and by week: deals closed, proposals sent, meetings held, qualified leads generated. It is not a CRM report that analyzes the past. It is an activity contract pointed at next week.
The logic is simple. Revenue is a lagging indicator, and the only thing your team directly controls today is this week's activity. Once you know the conversion rates between stages, you can calculate precisely how much input activity produces what output revenue, and then hold people accountable to the input, not just the outcome.
The difference between a scorecard and a dashboard matters. A dashboard shows what happened. A scorecard tells you what has to happen this week and who owns it. A company that manages only on revenue is always running two or three months behind reality, because by the time the number is bad, the activity that caused it is long gone.
How do you reverse-engineer your annual goal in 6 steps?
With the right data, the full calculation takes under an hour.
First, define your new-revenue goal. Separate net-new from renewals and expansion. If your goal is net of churn, add the churn back into the number you have to generate.
Second, divide by your average contract value, the ACV. This gives you the number of deals you need for the year.
Third, apply your proposal-to-close rate. If you close 1 of every 3 proposals, multiply your deal count by three.
Fourth, apply your meeting-to-proposal rate. What share of discovery meetings turn into a proposal?
Fifth, apply your qualified-lead-to-meeting rate. This tells you how many MQLs, hand-raises, or PQLs marketing has to produce.
Sixth, divide by working weeks and split by role. Use 46 to 48 weeks, backing out PTO, holidays, and the December slowdown, then assign every number to a specific person.
Pull the conversion rates from your CRM over the last six to 12 months. No history yet? Use conservative assumptions and recalibrate at 90 days. An imperfect scorecard beats a team with no activity targets at all.
What does the full worked example look like?
Take a B2B SaaS company selling logistics software to mid-market accounts. The average contract value is 12,000 dollars a year. The team is two account executives (AEs), two SDRs, and one marketer. The goal is 600,000 dollars in net-new revenue.
The historical rates are 33% proposal-to-close, 50% meeting-to-proposal, 40% MQL-to-meeting, and 20% lead-to-MQL.
Running the goal backward through those rates produces the scorecard. New revenue is 600,000 dollars for the year, or 12,500 dollars a week. At a 33% proposal-to-close rate, that is 50 deals closed for the year, roughly one a week. At a 50% meeting-to-proposal rate, that is 150 proposals sent, around three a week. At a 40% MQL-to-meeting rate, that is 300 discovery meetings, about six a week. At a 20% lead-to-MQL rate, that is 750 qualified leads (MQLs), roughly 16 a week. And that traces back to 3,750 total leads for the year, about 78 a week.
Split by person, each AE runs three discovery meetings a week, sends one to two proposals, and closes about two deals a month. Each SDR books three qualified meetings a week, working roughly eight MQLs to get there. Marketing delivers 16 MQLs a week out of about 78 leads.
Closing 600,000 dollars a year at a 12,000 dollar deal size does not take heroics. It takes two reps running three quality meetings a week, every week, without exception.
How many leads do you need each week to hit your goal?
The general formula is the revenue goal divided by average deal size, then divided by the product of your close rate, your meeting-to-proposal rate, your MQL-to-meeting rate, and your lead-to-MQL rate.
In the example that is 50 deals divided by the product of 0.33, 0.50, 0.40, and 0.20, which works out to 3,750 leads a year, about 78 a week. Because the rates compound, a small improvement at any single stage meaningfully cuts the number of leads you need at the top.
There are two adjustments founders and RevOps leaders routinely forget. The first is pipeline coverage. You need roughly three times your goal in live, qualified pipeline, so to close 12,500 dollars a week, keep about 150,000 dollars in active qualified opportunities at any given time. The second is sales-cycle lag. With 60 to 90 day cycles, the leads you generate today become next quarter's revenue, so January's leads fund April, and October's leads cannot save the current year.
This is exactly why you manage the scorecard weekly. A deficit in lead generation compounds, and you cannot make it up in December. The free Sales Machine Scorecard at blueprint.switchon.dev/en runs the full reverse-engineering in minutes, using your CRM rates if you have them, or starter benchmarks if you do not.
How do you split targets by person and keep the scorecard alive?
Split targets against each role's real capacity. An AE in SMB or mid-market can sustain five to eight discovery meetings a week before quality drops, and an SDR books two to four qualified meetings a week. If your scorecard demands more than that, the problem is not discipline, it is headcount or conversion rates, and no amount of pep talks fixes it.
Install a ritual: 30 minutes every Monday, three questions. Did we hit last week's activity across meetings, proposals, and MQLs? Do our actual conversion rates still match the assumed ones? And what do we adjust this week?
Pair it with a marketing-to-sales SLA. Marketing commits to its 16 MQLs a week, and sales commits to contacting every qualified lead in under 24 hours.
Three mistakes kill a scorecard. Measuring only outcomes, like revenue and closes, with no activity targets. Borrowing someone else's benchmarks permanently instead of recalibrating quarterly with your own data. And leaving it in a spreadsheet nobody opens.
A scorecard only works inside a complete system: a defined ICP, mapped pains, and clear funnel stages. The free Blueprint generator and Pain Matrix at blueprint.switchon.dev/en build that foundation first, so the numbers in your scorecard actually map to real buyers and real problems.
FAQ
What conversion rates should I use if I have no CRM history?
Start with conservative B2B SaaS assumptions: 25 to 35% proposal-to-close, 40 to 50% meeting-to-proposal, and 30 to 40% qualified-lead-to-meeting. Treat them as hypotheses, not truths. At 90 days, replace them with real CRM data and recalculate the whole scorecard. A scorecard with imperfect rates is far better than a team with no activity targets at all.
What's the difference between a lead, an MQL, a hand-raise, and a PQL?
A lead is a contact that fits your ICP. An MQL has shown interest, like downloading a resource or attending a webinar. A hand-raise has explicitly asked to talk to sales, requesting a demo or a quote. A PQL is already using your product and has crossed a usage threshold that predicts a purchase. Hand-raises and PQLs typically convert two to five times better than a cold MQL, so your scorecard should separate them and prioritize them in your contact SLA.
How often should I recalculate the sales scorecard?
Three cadences. Weekly, a 30-minute activity review with no exceptions. Quarterly, recalibrate conversion rates with real CRM data. Annually, or whenever something structural changes like average deal size, ICP, team size, or sales motion, rebuild the scorecard from scratch.
What do I do if the team hits its activity but the revenue doesn't show up?
You have a conversion problem, not a volume problem. The scorecard's whole advantage is that it pinpoints exactly where the math breaks. Lots of meetings but few proposals means your discovery or lead quality is off, so check your ICP. Lots of proposals but few closes means your value proposition or negotiation is the issue. Fix the broken stage before you ask anyone for more activity.
How many leads do I need if my deal size is higher and my cycle is longer?
The logic is identical, only the numbers change. The same 600,000 dollar goal but a 60,000 dollar deal size means 10 deals a year, not 50, so fewer leads, but every meeting is worth six times as much. For higher-priced deals, add intermediate deal milestones to the scorecard, like multiple contacts in the account, a validated business case, and a proposal presented to the sponsor, because weekly closes are too rare to manage against on their own.
Is the scorecard just for sales, or for marketing too?
It is for the whole revenue engine. Marketing needs a weekly qualified-lead target, the 16 MQLs a week in the example, and sales needs a contact SLA against those leads. If marketing does not appear on the scorecard with a number of its own, you have guaranteed the monthly argument about bad leads versus sales not calling them.
Want us to build it with you?
15 minutes, no pitch deck. We look at your loop and tell you exactly where the revenue is leaking.