Sales KPI Dashboard: A Free Google Sheets Template With Activity Benchmarks

Publish date: Nov 10, 2026
A sales KPI dashboard puts your team's activity, pipeline and outcome numbers on one screen, each against a target. This free Google Sheet does that with 10 KPIs, a weekday view and a rep view. One row per rep per day feeds it. Make a copy of the Sheet and the Dashboard tab fills itself.
The targets are not guesses. The Benchmarks tab carries Spona's dial benchmark for US IT services, built on 352,285 dials over a recent quarter. Of those dials, 16.6% reached the intended prospect and 8.7% became a conversation. The sheet is in English, and it downloads as an .xlsx file with its formulas intact.
Get thousands of leads in 4 minutes.
Stop stitching tools together.
Start with verified sales data, delivered in minutes.
No contracts · No setup · No onboarding
Sales KPI dashboard: 10 KPIs and their formulas
Ten KPIs cover a B2B sales team from the first dial to the quota. The table gives each one's formula, what it tells you and the example target the sheet ships with. The KPI definitions tab names the basis of every target, so you know what you are replacing.
| KPI | Formula | What it tells you | Example target in the sheet |
| Dials per rep per day | Dials / rep-days logged | Whether reps make enough attempts | 56 |
| Connect rate | Connects / dials | Number quality and timing | 16.6% |
| Conversation rate | Conversations / dials | Whether a reached prospect talks | 8.7% |
| Meeting rate | Meetings booked / conversations | How well the opener and the offer land | 4.8% |
| Opportunities created | Count of new opportunities | Whether meetings turn into pipeline | 0.29 per rep-day |
| Pipeline created | Sum of new opportunity value | New pipeline value in the period | 4,350 per rep-day |
| Pipeline coverage | Open pipeline / quota still to close | Whether the quarter can still close | 3.6x |
| Win rate | Deals won / (deals won + deals lost) | Share of decided deals you win | 28% |
| Average deal size | Revenue won / deals won | Value per won deal | 15,000 |
| Quota attainment | Revenue won / quota for the period | The result the rows above predict | 100% |
Geckoboard's rule for a sales dashboard is to include both input and output metrics. The first six rows are inputs a rep controls this week. The last four are outputs that follow weeks later, from pipeline the team built earlier.
The bases matter. SalesScreen writes win rate as won divided by won plus lost, and pipeline coverage as open pipeline over the remaining quota. Salesforce's conversion rate divides deals closed by leads in the pipeline instead. The two are not interchangeable, so the sheet spells out the base of every ratio.
The 3x coverage rule assumes you win about a third of what you work. SimpleKPI puts it plainly: at a 25% win rate you need about 4x. At 33% you need about 3x.
APQC's median is 28.0% of qualified leads closing as a sale, across 696 organizations. One divided by 0.28 gives the sheet's 3.6x target.
Dials per rep per day starts at 56 because The Bridge Group's SDR study puts phone-centric teams at 56 dials a day. The opportunity target comes from the same study: a median quota of 6 meetings a month converted into an opportunity. Spread over 21 working days, that is 0.29 per rep-day.
Opportunities created and Pipeline created count only deals that passed a qualification stage. Our guide to the B2B sales pipeline covers exit criteria for each stage, so a rep cannot inflate the count with first calls.
Sales dashboard template: five tabs in Google Sheets
The template has five tabs. You type in two of them, and the other three read from those.
| Tab | What you do there | What it computes |
| Instructions | Read six steps, type your reps, open the Spona links | Nothing; the Reps list feeds every Rep dropdown |
| Data entry | Log one row per rep per working day, up to row 200 | Weekday from the date, and In view for the Dashboard period and Rep |
| KPI definitions | Edit the yellow Target (edit) column | Pipeline created and Pipeline coverage targets from three other targets |
| Dashboard | Set the period, the rep and three quota and pipeline figures | Period totals, 10 KPI rows with a Status, a weekday table and a rep table |
| Benchmarks | Edit your number mix in the yellow cells | Spona rates by weekday and number type, and the expected rate for your mix |
Make a copy of the Sheet and set it up in six steps.
- Instructions: type your reps. Column H holds the Reps list from row 10, with Rep A to Rep C as examples. Every Rep dropdown reads this list, and so does the Dashboard filter. Row 9 holds All reps and stays. Google Sheets rejects an entry that is not on the list, so a misspelt name cannot split one rep's numbers in two.
- KPI definitions: set the targets. Column E, Target (edit), is yellow. Change the ten targets to yours; the Example target basis column says where each one came from. Row 13 holds the Watch band, set to 80%. A KPI under that share of its target shows Behind; between the band and the target it shows Watch.
- Data entry: one row per rep per day. Nine numbers per row: Dials, Connects, Conversations, Meetings booked, Opportunities created, Pipeline created, Deals won, Revenue won and Deals lost. Weekday fills from the Date, and In view (1 = counted) marks the rows that match the Dashboard period and Rep. Red cells catch Connects above Dials, Conversations above Connects and Revenue won with no Deals won. The money columns carry no currency, so type whatever you sell in. If your deals live in our CRM template, copy the won and lost counts from there. The 15 example rows are three reps over one week; clear them when yours start.
- Dashboard: set the period. Type Period start and Period end, then pick a Rep or All reps. Below them sit Quota for the period, Open pipeline closing this quarter and Quota still to close this quarter. Rep-days logged counts the Data entry rows in view, and every count target multiplies by it. Three reps over five days make 15 rep-days, so the Pipeline created target reads 65,250.
- Read the KPI table. Rows 15 to 24 show This period, Target, Status and Benchmark for each KPI. The totals come from SUMIFS, which adds every Data entry column where In view is 1. Each rate divides two of those totals. A rate stays blank until its base is above zero, so an empty week shows no false zeros.
- Read the weekday and rep tables. Rows 28 to 33 split the period by weekday against Spona's rates and print the Connect gap (points). A rate turns amber when it sits under Spona's. Rows 37 to 51 show each rep's Rep-days, Dials per day, both rates, Meetings booked, Pipeline created and Revenue won for the period.
With the example rows in place, six of the ten KPI rows show Watch. Three show On track and one shows Behind: Opportunities created, at 3 against a target of 4.4.
Friday shows a 15.2% connect rate on 145 dials. Rep B connects at 13.9% while Rep C reaches 18.0%. Those are the three conversations a Monday meeting would have.
The sheet is manual: nothing moves until a rep types the day's counts. Geckoboard's dashboards update continuously from a connected source, and that is the trade for a free sheet.
Dashboard benchmarks: dials, connects and conversations by weekday
Spona's call records give the activity rows a reference point. Over a recent three-month period, calls to US IT services companies produced 352,285 dials, split by weekday below.
| Weekday | Dials | Connects | Conversations | Connects per dial | Conversations per dial |
| Monday | 77,331 | 12,601 | 6,719 | 16.3% | 8.7% |
| Tuesday | 68,030 | 11,539 | 5,957 | 17.0% | 8.8% |
| Wednesday | 71,912 | 11,912 | 6,310 | 16.6% | 8.8% |
| Thursday | 64,735 | 10,831 | 5,683 | 16.7% | 8.8% |
| Friday | 70,277 | 11,628 | 6,114 | 16.5% | 8.7% |
| All weekdays | 352,285 | 58,511 | 30,783 | 16.6% | 8.7% |
The weekday barely matters. Tuesday's connect rate is the highest at 17.0% and Monday's the lowest at 16.3%. That is a spread of 0.67 points. The conversation rate moves by 0.09 points across the whole week.
A spread that small sits inside the noise of any one team's week. The sheet uses the weekday rows as a reference line, not as a reason to move calls to Tuesday. Hour of day is a separate question; our best time to cold call post covers it.
Across all weekdays, a connect took 6.0 dials and a conversation 11.4. About 52.6% of connects became conversations, and that share hardly changes by weekday either.
Two caveats travel with the table. The rows include calls placed outside office hours, so a team that calls only in office hours may run slightly above them. And the four number types each make up about a quarter of the dials. A list heavy in mobiles will run above these rows, and a switchboard-heavy list below them.
What counts as a connect and a conversation
Jesse Chan at Spona maps the two definitions to the sheet. A connect means the intended prospect was reached. A gatekeeper answer alone is not a connect. By the same rule, neither is voicemail or the wrong person.
A conversation means a substantive exchange about a need or a next step. A prospect who picks up and ends the call at once is a connect, not a conversation.
Both rates divide by all dial attempts, not answers. Measured on answered calls instead, a rate looks better and compares with nothing. Repeated attempts to one number count as separate dials. The Data entry tab uses the same three counts, so your rates sit on the same base as the benchmark.
The gatekeeper rule matters most for switchboard numbers, where a receptionist answers first. Our guide to getting past the gatekeeper covers the tactics. The dashboard only counts the result.
Number type moves the rates more than the weekday
The same 352,285 dials split four ways by number type. Unknown means Spona could not classify the number.
| Number type | Dials | Connects | Conversations | Connects per dial | Conversations per dial | Dials per conversation |
| Mobile | 87,939 | 22,888 | 11,777 | 26.0% | 13.4% | 7.5 |
| Direct dial | 87,233 | 17,738 | 9,273 | 20.3% | 10.6% | 9.4 |
| Switchboard | 87,064 | 11,179 | 6,205 | 12.8% | 7.1% | 14.0 |
| Unknown | 90,049 | 6,706 | 3,528 | 7.4% | 3.9% | 25.5 |
Mobiles connected at 26.0% of dials and switchboards at 12.8%. That is a gap of 2.0 times, and it dwarfs anything the weekday does. A conversation on an unknown number took 25.5 dials, against 7.5 on a mobile.
The gap is observational. It shows how each type performed in these records, not that swapping a switchboard number for a mobile multiplies your connects. Still, it is the first place to look when the Connect rate row turns amber.
The Benchmarks tab turns the table into a target for your own list. Type the share of your dials that goes to each type in the yellow cells. The Expected for your mix row blends the four rates.
Say 40% of your dials go to direct dials and another 40% to mobiles. Switchboards take 15% and unknown numbers 5%. The expected connect rate is 20.8% and the conversation rate 10.9%.
A switchboard-heavy list runs the other way. Put 60% of dials on switchboards and 20% on unknown numbers. Direct dials and mobiles get 10% each. The expected connect rate falls to 13.8%, and conversations to 7.5%.

Outside studies measure differently, so compare with care. Gong analyzed more than 300 million cold calls. The average rep connects with 5.4% of prospects, and the top quartile with 13.3%.
Gong and Spona both divide by dials. Gong counts calls a prospect answered, while Spona counts calls that reached the intended prospect. Neither number is wrong, but they are not the same measure.
How many dials does each meeting take?
Work the funnel backwards from the meeting. The estimates below use Spona's rates for connects and conversations, and an outside rate for meetings, because Spona's records stop at the conversation. Label them estimates on your own dashboard until your meeting count replaces them.
Cognism's cold calling study counted 254 meetings from 5,265 conversations. Cognism calls that a 4.82% success rate. It does not define a conversation, so the two datasets may not count the same thing.
Spona's conversation rate turns 1,000 dials into about 87 conversations. At Cognism's meeting rate, those become about 4 meetings. One meeting costs about 237 dials on the benchmark mix.

The mix changes the bill. On the direct-and-mobile list from the Benchmarks tab, a meeting takes about 191 dials. On the switchboard-heavy list it takes about 278.
The Bridge Group's phone-centric SDRs average 56 dials and 4.6 quality conversations a day. That works out at 8.2 conversations per 100 dials. Spona's 8.7% sits close to it, though The Bridge Group leaves quality conversation undefined.
Five conversations a day take about 57 dials on the benchmark mix. The Dials per rep per day row tells you whether the team is making them. The Conversation rate row tells you whether the dials land.
A meeting is worth what the deal behind it is worth. Our lead value calculator turns customer lifetime value and the lead-to-customer rate into a value per lead. That number tells you whether 237 dials per meeting is cheap or dear for your team.
Reading the dashboard in a weekly sales meeting
HubSpot's dashboard template suggests a 30-minute weekly review. Thirty minutes is enough if the meeting reads the KPI table top-down and stops at the first Behind.
Read the ten rows in order. The activity rows say what happened this week, and the pipeline rows say what it will produce. The outcome rows say what happened to the pipeline the team built weeks ago. A bad week there is old news, not this week's.
Geckoboard warns that some metrics are too noisy to be useful over short periods. Win rate on five decided deals is one of them. So is any connect rate on one rep-day.
Before you act on a rate, count the dials under it. A connect rate is a proportion, and its margin of error shrinks with the square root of the sample. Penn State's STAT 200 course gives the 95% margin formula: 1.96 times the square root of p(1 - p) divided by n.
Take the benchmark connect rate of 16.6%. One rep's week of 280 dials carries a margin of about 4.4 points either way. At 500 dials it shrinks to 3.3 points. A five-rep week of 1,400 dials brings it down to 1.9 points.

That is why the hint under the weekday table reads: Gaps under 3 points on fewer than 500 dials are usually chance, not a trend. Spona labels its own hourly cells under 500 dials as small samples. The weekday spread of 0.67 points is smaller than a single rep's weekly noise.
When a row shows Behind, the fix depends on the row.
| Row that shows Behind | Where to look first | Why |
| Dials per rep per day | The calendar, not the rep | Selling time is the constraint |
| Connect rate | The number mix on the Benchmarks tab | Mobiles connect at 2.0 times the switchboard rate |
| Conversation rate | The first sentences of the script | The prospect was reached and still did not talk |
| Meeting rate | The offer at the end of the call | The conversation happened and still did not book |
| Pipeline coverage | New opportunities this week | A quarter cannot be fixed in its last month |
| Win rate | A quarter's worth of decided deals, not a week's | Too few deals make the rate noise |
Low dials are usually a time problem before an effort problem. Salesforce's State of Sales survey of 4,050 sales professionals found that the average seller spends 40% of their time selling. In the same survey, 48% say they lack the bandwidth for adequate cold outreach. Look at what fills the rest of the week before you raise the target.
A low conversation rate with a healthy connect rate points at the opener, not the list. The prospect picked up and still did not talk. Our cold call scripts post covers the first sentences that earn the next thirty seconds.
Coverage under target means the quarter needs pipeline now, not in its last month. Ebsta's benchmarks combine pipeline data with a survey of 2,000 CROs. They found 78% of sellers missed quota, up from 69% the year before. The coverage row flags a short quarter while there is still time to act.
Where Spona helps a low connect rate, and where it cannot
Spona is not a dashboard tool. It does not read this sheet, report on your CRM or roll numbers up a team. If you want a screen that refreshes itself from Salesforce or HubSpot, Geckoboard and Coupler do that, and this sheet does not.
Where Spona helps is one row: Connect rate. In Spona's records, mobiles connected at 26.0% and switchboards at 12.8%. A list with more of the first and less of the second is what Spona builds. You describe your ideal customer in a chat, and Spona returns a verified, scored lead list.
A Standard Search with email and mobile costs 35 to 55 credits a lead. In dollars, that is $0.28 to $0.55. Every search starts with a free sample of leads, and the price per lead shows at checkout. If your list already exists, Data Enrichment adds direct dials and mobiles to your own rows, and Spona has a HubSpot integration.
The limits are plain. Spona's benchmark covers US IT services, so a UK team calling finance directors should use the mix calculator as a shape, not a target. Spona has no dialer yet; one is coming soon, so the dials still happen in whatever you call from today.
And a better list works through the connect rate only. The share of connects that become conversations, the meeting rate and the win rate belong to the rep. No data vendor sells those.
Get thousands of leads in 4 minutes.
Stop stitching tools together.
Start with verified sales data, delivered in minutes.
No contracts · No setup · No onboarding
Sales KPI dashboard FAQ
What are the 5 key performance indicators in sales?
For a B2B team, the five that matter are dials per rep per day, connect rate, meeting rate, pipeline coverage and win rate. Together they cover effort, list quality, the call itself, the quarter and the outcome. If you can watch only three, take connect rate, pipeline coverage and win rate: one input, one forecast, one result.
What are some KPI dashboards?
Geckoboard's gallery shows ten sales dashboard examples, eight of them by type: leaderboard, pipeline, rep, activity, manager, account manager, opportunities and product. This template is an activity and rep dashboard with a pipeline block, because those are the rows a weekly meeting can change. A leaderboard is the same Data entry rows, sorted by rep.
What should a sales dashboard include?
Both inputs and outputs, with a target beside each. Stephen Few's definition still holds: a dashboard is the most important information needed to meet objectives, consolidated on one screen and monitored at a glance. The ten rows in the first table are a full sales KPI dashboard for a weekly team meeting. A rep's own view adds the weekday and rep tables.
What is the 5 second rule for dashboards?
Sisense's design rule says a dashboard should give the viewer the relevant information in about 5 seconds. The top insight goes at the top, with five to nine visualizations at most. The Status column on the Dashboard tab does the same job: its colour says On track, Watch or Behind before you read a number.
Does the template work in Excel?
Yes. In Google Sheets, use File, Download, Microsoft Excel, and the file downloads as .xlsx with its formulas. They use only standard functions such as SUMIFS, COUNTIFS, SUMPRODUCT and WEEKDAY, which Excel has. The dropdowns and colour rules should carry over too. The Weekday column uses CHOOSE on WEEKDAY, so it prints English day names in any locale.
How many dials should a rep make a day?
The Bridge Group's phone-centric SDR teams average 56 dials a day. Across all SDRs in its study, the median is 112 daily activities, 44 of them by phone.
At Spona's connect rate, 56 dials produce about 9 connects. About 5 of those become conversations. Set the target from the conversations you need, not from the dials. Five conversations a day on a switchboard-heavy list take closer to 67 dials.
Share this article
GET FREE LEADS





