How to design an SDR outbound dashboard

Start from the SDR manager's week, not from the metric catalog. The manager has three decision loops: a morning floor-walk that asks who is behind on activity today, a weekly one-on-one that asks who is converting touches to meetings and who is not, and a monthly performance review that asks who is sourcing enough qualified pipeline to hit team quota. Each loop needs a different depth of view on the same source of truth. Write the three loops down with the exact question each one answers in under thirty seconds. Every tile on the dashboard has to earn its place against one of those loops. Everything else is dashboard clutter that trains the manager to stop opening the page.

• List the three SDR manager decision loops: morning floor, weekly one-on-one, monthly review
• Write the one question each loop must answer in under thirty seconds
• Map every candidate metric to at least one loop or cut it from the design
• Capture the output in a one-page brief the SDR manager and RevOps both sign before build

The SDR scorecard is three layers deep. Activity sits at the base: dials, connects, emails sent, email replies, LinkedIn messages, LinkedIn accepts, and sequence completion rate. Meetings sit in the middle: meetings set, meetings held, no-show rate, and meeting-to-SQL rate. Pipeline sits on top: SQLs created, sourced pipeline dollars, average deal size on sourced opportunities, and SQL-to-opportunity conversion. Pick two or three tiles from each layer. Too much activity data trains SDRs to grind for volume. Too much pipeline data makes activity invisible and the manager cannot coach the leading edge. The ratio is the point: activity is coached daily, meetings weekly, pipeline monthly, and the dashboard mirrors that cadence top to bottom.

• Pick two or three activity tiles the manager can coach the same afternoon
• Pick two or three meeting-stage tiles the manager can coach inside the week
• Pick two or three pipeline tiles that reconcile cleanly to the AE forecast downstream
• Document the exact definition, source event, and refresh rule for every tile
• Confirm meeting set and SQL definitions match what the AE org counts, not just what SDRs claim

The SDR manager scans the dashboard in under a minute between calls, so every visual has to pay off at a glance. Use a big-number tile with a trend sparkline for team totals like meetings set this week and sourced pipeline this month. Use horizontal bars ranked descending by rep for anything the manager coaches at the individual level, so the lowest performer sits at the bottom and the eye lands there first. Use a funnel visual for dial to connect to meeting set to meeting held to SQL, because the stages are inherently ordered and a drop in any one segment is a specific coaching conversation. Avoid pie charts, dual-axis lines, and anything that encodes rank in color alone. Keep red, yellow, and green reserved for threshold status, not for brand decoration.

• Use big-number plus sparkline for team-level activity and pipeline tiles
• Rank per-rep bars descending so the manager sees who to coach first without clicking
• Build an SDR funnel visual that shows dial to connect to meeting to SQL in one view
• Reserve color for threshold status: on-pace, behind, and critical only

A number without a cue is wallpaper. Under every tile, write the coaching move the manager runs when that metric drifts. If dials per rep drop two days in a row, run a block-time audit. If connect rate drops but dial volume holds, run a list-quality review on the sequence those SDRs are working. If meetings set hold but meeting-to-SQL conversion collapses, run a discovery-call review with the AE pod. If sourced pipeline slips but SQL volume holds, review deal-size qualification criteria with the SDR. Ship the cues as a small text panel beside each tile so the dashboard teaches managers how to use it. New hires onboard faster, veterans stop improvising, and the scorecard becomes a coaching system instead of a scoreboard.

• Write the coaching move for every tile: what the manager does when the number drifts
• Attach cues directly to the dashboard, not to a side document that no one re-opens
• Define thresholds that move a rep from on-pace to behind to critical for each tile
• Make the dashboard the explicit agenda source for weekly SDR one-on-ones

The same page should serve the whole-team floor-walk and the one-rep coaching conversation without a rebuild. Standard filters are time period, team or pod, SDR, sequence, segment, and target-account list. Set smart defaults so the manager lands on their own pod week-to-date and the SDR lands on their own book today. Make every bar and tile clickable. A click on a rep's meeting-set bar should open the list of meetings set this week, each one linked to the account and the sequence that produced it. A click on a sequence's connect rate should open the step-by-step send and reply data for that sequence. Drill-downs are the difference between a dashboard that gets read and a dashboard that gets worked.

• Define the filter set once and bind it to every tile and table on the page
• Set role-aware defaults so manager, team lead, and SDR each land on the right slice
• Make filters sticky across sessions so repeat views open without extra clicks
• Wire click-through from any tile to the underlying list of touches, meetings, or accounts

SDR activity is a same-day coaching surface, so the activity layer needs near-real-time refresh. Dials, emails, and LinkedIn touches should land on the dashboard within minutes, not overnight, so the manager can act before the floor goes home. Meetings-set and SQL counts can refresh hourly without hurting coaching. Sourced pipeline reconciles nightly against the AE funnel so the SDR and AE orgs cannot disagree on what the SDR actually produced. Build a nightly check that compares SDR-reported sourced pipeline against AE-held opportunities with SDR source stamps, and flag any gap beyond a tight tolerance. If the two numbers disagree on day one of the quarter, the dashboard loses the room for the rest of it.

• Refresh activity tiles near-real-time so same-day coaching has current data
• Refresh meeting and SQL tiles hourly, which is plenty for weekly one-on-ones
• Reconcile sourced pipeline nightly against the AE opportunity table and alert on drift
• Show a visible last-refreshed timestamp on every tile so staleness is never a guess

Alerts turn the dashboard from pull to push. Set a short list of threshold alerts the SDR manager cannot afford to miss: an SDR two days behind on activity target, team meeting-set pace falling below the band required to feed AE pipeline, a sequence whose connect rate drops below the lower bound of its own trend, and a sudden rise in no-shows on booked meetings. Route each alert to a single named owner, never to a shared channel where it gets ignored. Keep volume low: three to five sharp alerts a week clear the signal; thirty every day teach the manager to mute them. Pair every alert with the recommended next action and a deep link into the drill-down view so the manager works it in one click.

• Pick three to five metrics worth alerting on, not every tile on the page
• Set thresholds tight enough to catch drift early but loose enough to avoid false alarms
• Route each alert to a single named owner with a recommended next action inline
• Deep-link every alert into the drill-down so the manager can act in one click

An SDR dashboard is a living artifact because an SDR team is the most adaptive seat in the GTM org. Every quarter, run a short retro: which metrics predicted sourced pipeline, which drifted off the AE funnel, and which got gamed. If dial volume climbed and connect rate fell, the dials tile is being gamed and needs tighter definitions or a different measure. If meetings held but meeting-to-SQL conversion dropped, the meeting-set bar is too low. Drop or redefine any tile that stopped predicting outcomes. Hold the core formula stable so trend lines stay comparable across quarters, but tune thresholds, cues, and visuals aggressively. Keep a changelog with the date, the change, and the reason so six months later the team knows which tweak moved which number.

• Run a quarter-end retro on which tiles predicted sourced pipeline and which did not
• Drop or redefine any tile that was noisy or gamed and sharpen the ones that stayed
• Refresh thresholds against the current team shape and the AE pod sitting downstream
• Keep the core formula stable so quarter-over-quarter SDR trend lines stay comparable