A sales leaderboard on an office TV is a live number showing the team’s pipeline, attainment, or activity against a goal — refreshed when the source changes, not on a fixed timer. Most useful when it shows a team number, not individual ranking; the version that pits reps against each other publicly is the one that quietly poisons the team. The hard part isn’t the wiring — it’s the design constraint: a wall screen is glanced at, not studied. Browser dashboards can afford small type and dense tables; a screen twelve feet away at standing height can’t. That’s the gap this post fills, starting from a Google Sheet and a wifi-only screen.
Start with the data you already trust (not the data you wish you had)
The single most common failure isn’t a wrong widget choice. It’s putting numbers on a screen that nobody believes. The fix is principle: if the office manager wouldn’t quote the number in a one-on-one with the rep whose name is on it, it doesn’t go on the wall. Stale numbers are worse than no numbers — they look official and wrong.
The 10–50-person team almost always has one of three sources: a Google Sheet the office manager updates Monday morning, a CRM list view (HubSpot deal board, Pipedrive list, Salesforce Essentials report), or a Zapier-fed Sheet that mirrors the CRM every 15 minutes. The rule is the same for all of them.
If you haven’t picked a use case yet, the five office TV dashboard use cases is a faster read; this post focuses on the leaderboard pattern in depth.
What to actually put on the screen (and what to leave off)
Three widgets a sales leaderboard should have:
- Weekly pipeline coverage vs. target. Total open $ against quota. The standard proxy for whether the team is on pace; open pipeline should be several multiples of remaining quota.
- Deals-in-pipeline by stage. A horizontal bar per stage. Tells the team whether late-stage coverage is healthy or quarter-close is going to be a sprint.
- Closed-won this week plus a rolling 90-day attainment vs. target. The morning meeting reads the weekly number first; the rolling 90-day is the pacing number.
Leave off:
- Individual ranking by name. Especially when the team is under six reps. The bottom two of a five-person team get demotivated permanently; the top two disengage. The academic literature on gamification consistently names public leaderboards as the single game element most associated with negative outcomes for participants — see Hyrynsalmi et al. on gamification side-effects, or the Springer chapter How to Avoid the Dark Side of Gamification. The mechanism holds especially strongly in small leagues.
- Live deal values that flip-flop when stages change. A deal that moves from “qualified” to “proposal” today and back tomorrow creates a screen that lies twice a week.
- Raw cold-call activity counts on a public screen. Activity-only metrics misfire as a public ranking — they reward reps who game the count.
If you’ve decided on the leaderboard and now need to pick the software, the office TV dashboard buyer’s guide is the comparison and the seven questions to ask any vendor.
Refresh cadence — weekly on outcomes, daily on activity, never sub-hourly on either
Two cadences work for most small teams: refresh the outcome numbers weekly, or on demand when the source changes, and refresh the activity numbers daily. Sub-hourly refresh on either is a screen that moves faster than the team can react to — and a screen nobody trusts is worse than a screen nobody watches.
Daily activity counts require a live source (CRM list with API, or a Google Sheet connected through Zapier with a polling interval). Weekly outcomes tolerate a Monday-morning manual refresh, especially when the source is the office manager’s own Sheet.
A daily sales standup wants the activity number refreshed overnight, not every five minutes. A weekly leadership review wants the close-out number, refreshed at midnight Sunday.
For the broader cadence cluster across other wall-screen use cases, the digital signage use cases hub covers the menu-board, waiting-room, and meeting-room variants.
When a public leaderboard quietly poisons the team (and how to design around it)
Three failure modes an SMB operator will recognise. The literature cited above is the research anchor; the operational version is the one to design around.
Refresh that’s slower than the source. Spreadsheet says X, screen still says Y, team loses trust. The fix is mechanical — use a paid tier with fast refresh, or accept the lag. The worst version is a screen that lags by exactly one standup cycle. The team stops reading it.
One rep persistently at the bottom. If the team wants individual ranking, pair it with explicit conversation about what to do when this happens. If the team doesn’t have that conversation — and most don’t — drop individual ranking and show team-only numbers. The research is consistent: in a small league, ranking rewards luck as often as effort, and the bottom-of-league rep is rarely the worst salesperson on the team.
The screen becomes wallpaper. Six months in, nobody looks. The cure is rotation — swap the leaderboard for closed-won-this-week, or for activity counts, or for a meeting-room availability board for a week, then bring the leaderboard back. A wall screen is a finite attention resource.
The team dashboard best-practices post has the full decay-prevention checklist for the version of wallpaper that comes from six-month-old numbers nobody updated.
The 30-minute setup from a Google Sheet
Most teams already have the kit: a TV with HDMI (most offices have a meeting-room display nobody uses), a Fire Stick or Raspberry Pi if the wall TV is far from the router, the office wifi, a Google Sheet with one row per rep and a totals row, and a dotBlast subscription. dotBlast’s free tier covers one device; Starter covers the kitchen plus meeting-room screens.
The wiring is one widget — the iframe widget — pointed at a Google Sheet that’s been published to the web. That is dotBlast’s actual live-data path: the metric widget and the chart widget are typed-string widgets with no backend fetch. The iframe widget points at the Sheet’s published URL and refreshes on a plan-specific cadence.
One thing to think through before publishing a Sheet to the web: the URL is publicly accessible to anyone who has it. If your Sheet has rep names by row with deal values, you’ve made your team’s pipeline public at that URL. The standard mitigation is to publish a Sheet that contains only team totals, or use a private CRM view URL with the same caveat. This is the part most “sales dashboard on a TV” articles skip.
Six steps, under an hour:
- Get the source right. One Google Sheet, one row per rep. Use the Sheet the office manager already updates.
- Add a totals row for the team-aggregate numbers.
- Publish the Sheet to the web. File → Share → Publish to web. Pick the worksheet, “Web page” or “CSV”, copy the URL. Note what you’re publishing.
- Add the iframe widget to a new dashboard. Paste the published Sheet URL. Set the refresh interval to your decision cadence — daily for activity, weekly for outcomes. Your plan also sets a floor on how fast refresh can go (five minutes on Starter for an iframe), but the floor is a limit, not a target.
- Add a markdown widget with the team’s goal for the month (“$200K by Sep 30”).
- Link the screen with a permanent PIN, not a Quick Link.
If you’re still choosing between tools, the comparison page puts dotBlast next to Geckoboard, Klipfolio, Databox, and Grafana feature by feature.
Setup guide: how to put a dashboard on an office TV →
How dotBlast wires this specifically
Configuration example, not a sales pitch.
- The iframe widget pulls the Sheet’s published URL — that’s the live-data path. Refresh is clamped to the infra-heavy floor for this widget type, because the iframe pulls a real external URL on every refresh.
- Refresh intervals for the iframe widget by plan (current values live on the pricing page; this is the configuration example, not a price quote):
- Free: 60 minutes
- Starter: 5 minutes
- Pro: 60 seconds
- Business: 15 seconds
- PIN-pairing the wall TV uses a six-digit permanent PIN — the same screen reconnects automatically if the device reboots. Quick Links are for meeting-room share, not wall screens.
- Device allowances (live on pricing): 1 on Free, 3 on Starter, 10 on Pro, 25 on Business. One wall TV = one device.
The metric widget and chart widget don’t pull live data — they’re typed-string widgets with no backend fetch. If you want a number that updates when a CRM field changes, today’s path is the iframe widget + a published Sheet (or a published CRM list-view URL with the same caveat). A live Sheets or CRM data source behind the metric widget isn’t something dotBlast ships today. The iframe is the honest path, and it works.
The pre-launch checklist
Five checks before going live:
- Data source is current. Open the Sheet, open the CRM list view. Is the number one you’d quote in a one-on-one today?
- The metric is one a one-on-one would defend. If a rep asked “why is that on the wall,” the answer is one sentence.
- Refresh cadence matches the decision cadence. Daily on activity, weekly on outcomes. The plan floor caps how fast you can refresh; it is not a recommendation for how fast you should.
- The team has had one round of “what is this for.” Five minutes in the Monday standup.
- The dashboard has a named owner. Not an admin — an owner.
If any of those five is missing, fix it before the wall screen goes live. A wall screen that fails one of those five is a wall screen the team learns to ignore within a month.
If half the team is remote, the team dashboard best-practices post for remote and hybrid teams covers the laptop companion view — the wall screen only works if it works on a browser tab too.
Reading order for an SMB operator who landed here first: this post → the office TV dashboard buyer’s guide for the software → the setup walkthrough for the device.
Setup takes under an hour if you’ve got a TV and a Google Sheet ready.