Built for RevOps and sales managers assembling dashboard libraries

Twelve working examples of sales dashboards you can clone, edit, and ship this week.

Most teams keep hearing that dashboards are important and keep opening the same two generic ones. This page walks through twelve concrete examples by audience (rep, first-line manager, VP, CRO, RevOps) with the exact panels, filters, and refresh windows that make each one earn its tile.

What this audience is actually dealing with

The pains that bring buyers here.

Sales dashboards fail in predictable ways. The one for the CRO reads like a weekly leaderboard. The one for the first-line manager reads like a status report. The one for the rep reads like a scoreboard that nobody looks at twice. The one for RevOps becomes a 24-tile grid where no single tile earns the pixel budget. Behind each failure sits the same mistake: the audience, the decision, and the refresh cadence were never named. A good dashboard answers one question for one role on a known cadence. The six pain points below are the symptoms we hear from mid-market and enterprise sales organizations before a dashboard rebuild. Each example in the sections further down is designed to retire one or more of these specific symptoms.

The 24-tile wall problem

A dashboard that answers everything answers nothing.

When a sales dashboard carries 24 tiles that each try to serve a different audience, the regional VP ends up ignoring 18 of them and the AE ignores all 24. Strkr tiles are role-tagged, which lets a single page render only the panels assigned to the viewing role so the AE sees eight tiles that matter to them and the VP sees eight different tiles on the same URL.

Dashboards that lag the data by a day

Monday standup opens a Friday snapshot.

Many CRM dashboards refresh overnight, which means a Monday 9am review opens numbers from Friday. For high-velocity teams running weekly cadence that lag kills every signal. Strkr tiles refresh on view or on configurable schedules (one minute, five minutes, fifteen minutes) and the surface shows the last-refreshed timestamp so the viewer always knows how fresh the number is.

Forecast dashboards without variance context

The number is 4.2 million. Compared to what?

A forecast tile that shows a single rolled-up number is a decoration. The useful version compares current forecast against commit, best case, pipeline coverage ratio, same-week-last-quarter, and a week-over-week delta. Strkr forecast tiles bundle these as linked panels so the manager reads context, not a single hero figure.

Rep dashboards nobody opens twice

A rep opens a dashboard once to prove it exists, then never again.

Rep adoption of dashboards fails when the panels show numbers the rep already feels (quota attainment, deals closed) rather than numbers that change their next action (list of deals with no activity in seven days, calls booked for the week ahead, follow-ups overdue). Strkr rep tiles are action-oriented and surface the next-action queue directly in the tile.

Pipeline tiles that show count only

The number of open deals tells you almost nothing.

A pipeline tile that reads 184 open opps is near-meaningless without stage distribution, aging, source mix, and expected close concentration. Strkr pipeline tiles ship with the small-multiple view that renders stage, aging, source, and close-date buckets as one grid so the viewer gets shape, not just count.

Cohort views that live only in a Looker tab

Retention and expansion patterns stuck in a separate tool.

Cohort retention, logo retention by segment, and expansion by vintage usually live in a BI tool and never make it back to the CRM dashboard. Strkr cohort tiles pull directly from Strkr data and render inside the sales dashboard so the AE and the account manager see the same cohort view the CS leadership team sees.

The first four examples: individual contributor dashboards

Dashboards for the person doing the selling.

An AE, an SDR, and an account manager each need a different first screen. The examples below describe the panels that actually drive a next action rather than reward the dashboard for existing.

Example 1 · AE daily board

Today, this week, this quarter in three horizontal bands.

The AE daily board stacks three bands. Top band: today's meetings, overdue follow-ups, deals with risk flags from Strkr AI. Middle band: this week's pipeline movement (deals advanced, deals slipped), activity volume versus a configurable floor. Bottom band: quarter attainment with coverage ratio and days remaining. Nothing else. The AE opens this once in the morning and once after lunch.

Example 2 · SDR activity dashboard

Outbound volume, response rate, and meetings held.

The SDR dashboard renders daily and weekly outbound counts (calls, personalized emails, LinkedIn touches), response rate per channel, meetings booked, meetings held versus booked, and quality score on booked meetings fed back from AE acceptance. A left rail shows the SDR's next ten accounts in the sequence with the step they are on.

Example 3 · Account manager renewal board

Health, usage, next renewal date per account.

The AM dashboard shows every account owned by the viewer with a health color, product usage trend over the last 90 days, days to renewal, open support tickets, QBR date, and expansion plays suggested by Strkr AI. The default sort is days-to-renewal ascending with health as a tiebreaker so the account approaching renewal with a yellow health flag floats to the top.

Example 4 · Deal-focused AE pipeline

One tile per open deal with stage, next step, next date.

An alternative AE view renders each open deal as a card in a vertical list ordered by expected close date. Each card shows stage, amount, decision maker, last activity date, next step owner, next step date, and risk flags. The AE scans the list in two minutes to find the deals missing a next step or with stale activity.

Example 5 · SDR weekly report

A Monday morning summary of last week.

Separate from the daily dashboard the SDR gets a weekly Monday morning report tile: last week's targets, actuals, response-rate deltas, top-performing sequence, worst-performing sequence, and the accounts that moved to AE. The purpose is pattern recognition over the preceding seven days rather than real-time status.

Example 6 · AE cohort perspective

How the current class of deals compares to historical cohorts.

An AE dashboard that benchmarks the current quarter against the same AE's last four quarters: deals opened at the same point in quarter, average deal size, close rate on deals from the same lead source, cycle time distribution. The purpose is self-benchmarking rather than ranking against peers.

The next three examples: first-line manager dashboards

Dashboards for the sales manager running a team.

A first-line sales manager has a different question than the AE: who on my team is on track, who is slipping, where should I spend coaching time this week. The three examples below are built for that question.

Example 7 · Team scorecard

Attainment, activity, pipeline coverage per rep.

The manager scorecard renders a row per rep with quota attainment, pipeline coverage ratio, this week's activity volume, deals advanced, deals slipped, and a composite health score. The default sort surfaces the rep with the lowest health first so the manager spends coaching cycles where they are most needed. Clicking a row opens the AE dashboard for that rep.

Example 8 · One-on-one prep

The deals and signals for this week's one-on-one.

Before a weekly one-on-one the manager opens a prep dashboard for the rep. The surface shows deals with stage changes, deals with activity gaps longer than seven days, deals with Strkr AI risk flags raised in the past week, deals that moved into or out of commit, and a free-form note area the manager fills in for the conversation.

Example 9 · Pipeline inspection

Deals in commit sorted by risk.

The pipeline inspection tile shows every deal the team has in commit and best-case stages with the Strkr AI risk score, days in stage, last activity date, decision-maker engagement signal, and procurement step status. The manager works down the list and flags the deals that need coaching rather than discussing the full forecast line-by-line.

Example 10 · Win-loss by rep

The pattern across the past 90 days.

A win-loss panel segmented by rep showing win rate on sourced versus marketing-provided deals, win rate by competitor replaced, loss reasons distribution, and cycle time variance by deal size. The manager uses the panel in quarterly reviews to coach on specific loss patterns rather than aggregate numbers.

The next three examples: VP and CRO dashboards

Dashboards for the executive layer that owns the number.

A VP of sales or CRO reads a different dashboard than a first-line manager. The question is portfolio-level: are we going to hit the quarter, where is the risk concentrated, and what is the leading indicator telling us.

Example 11 · CRO quarterly board

Commit, best, pipeline coverage, segment health.

The CRO board shows the current quarter's commit, best case, and pipeline coverage against plan rolled up by segment, by region, and by product. A delta column shows change-since-last-week on each line. A trend sparkline on each row shows the past six weeks. The purpose is identifying segment-level risk early, not inspecting individual deals.

Example 12 · Leading-indicator panel

Pipeline creation, qualified opps, SQL-to-opp conversion.

The leading-indicator panel surfaces pipeline creation rate, qualified-opportunity volume, SQL-to-opportunity conversion, and sales-accepted-lead volume versus the same period in prior quarters. Trailing indicators (wins, revenue) lag by a quarter, so the leading panel is what the CRO reviews in weekly ops cadence for early-warning signal.

Example 13 · Segment and territory health

Where attainment is concentrated and where it is thin.

A heatmap of attainment by segment and territory with cell shading reflecting percent-to-plan and a sidebar of territories flagged as at-risk based on Strkr AI's segment-health model. The CRO opens the panel ahead of QBR cycles to prioritize which segments get leadership attention next quarter.

Example 14 · Churn and expansion band

The post-sale number that affects top-line growth.

A band on the executive dashboard dedicated to NRR, GRR, logo-retention curve, and expansion motion contribution. For a growth-stage company this band is often as important as new business and often lives on a separate tool. On the Strkr CRO dashboard it sits inline so the full growth picture reads in one scroll.

The last two examples: RevOps and SKO-ready narrative dashboards

Dashboards for the operator and the presentation.

RevOps teams build dashboards for themselves (operational monitoring, data health, pipeline sanity) and for formal presentations (SKO, board decks, QBR narrative). The final two examples cover each shape.

Example 15 · RevOps data-health dashboard

Where the CRM data is drifting or incomplete.

The RevOps data-health board shows record completeness scores by object (contact, account, opportunity), fields with high null rates, records flagged as duplicates by Strkr AI, deals with missing close dates, and the queue of records failing validation rules. The operator spends an hour a week working the queue so the dashboards further up the stack stay trustworthy.

Example 16 · SKO narrative dashboard

The dashboard shaped for a 90-minute presentation.

An SKO or kickoff dashboard is shaped for a different audience. The tiles are larger, the font sizes bigger, the number of panels fewer. It walks a presenter through last year's results, the plan for the new year, segment-level targets, and the leading-indicator baseline. The presenter clicks through sections rather than scrolling. The Strkr dashboard builder supports this presentation mode as a toggle on any dashboard.

Example 17 · Pipeline hygiene board

Stale deals, missing next steps, missing contacts.

Separate from data health, pipeline hygiene renders the hygiene gaps blocking forecast reliability: deals with no activity in 14 days, deals in the forecast without a stated next step, deals with no identified economic buyer, deals with close dates in the past that have not been updated. RevOps and first-line managers both open this view in weekly cadence.

Panel-level patterns across every example

The reusable panels that compose into dashboards.

Every example above is built from a smaller set of reusable panels. Strkr ships the panel library so a dashboard author composes panels rather than building each tile from scratch. The twelve most-used panels appear below.

Pipeline coverage ratio

Pipeline divided by remaining gap to plan.

The coverage-ratio panel renders a single number with a target floor (typically 3.0x for mid-market, 4.0x for enterprise) and a trend sparkline. A red state fires when the ratio drops below the floor. The panel appears on manager, VP, and CRO dashboards. It is derived rather than configured so every team using Strkr sees the same shape.

Weighted forecast

Pipeline weighted by stage close-rate history.

The weighted-forecast panel multiplies open-pipeline amount by historical close-rate per stage per segment per rep, then rolls up. A toggle switches between fixed-stage weighting and dynamic Strkr AI weighting that incorporates recent cycle data. The two views sit side by side so the operator sees both.

Activity volume floor

Calls, emails, meetings versus a configurable minimum.

The activity-floor panel renders rep-level activity (calls, emails, meetings held) against a floor the manager sets per segment. Red state fires when a rep sits below floor for two consecutive weeks. The panel appears on both AE and manager dashboards, with the manager version aggregated across the team.

Deals-at-risk flag list

The Strkr AI risk model surfaces specific deals.

The deals-at-risk panel renders deals the Strkr AI risk model flagged in the last seven days with the signal (stale activity, missing procurement step, decision-maker disengaged, competitor mentioned in notes). The manager opens the panel in one-on-one prep rather than scrolling through the full pipeline.

Stage conversion funnel

Volume at each stage with conversion to next.

The funnel panel renders a horizontal bar per stage with volume count and conversion percentage to the next stage. A segment filter lets the viewer compare funnel shape by segment or source. The panel is the fastest way to find a stage where deals are getting stuck.

Cohort retention curve

Logo and dollar retention by vintage.

The cohort panel renders retention curves by acquisition quarter with both logo retention and net dollar retention plotted. A hover reveals specific cohort size and expansion contribution. The panel appears on AM, VP, and CRO dashboards and uses Strkr's unified data model so sales and CS see the same curve.

Lead source attribution

Pipeline and revenue by source.

The source-attribution panel splits pipeline creation and closed revenue by lead source (marketing-sourced, SDR-sourced, AE-sourced, partner-sourced, inbound-sourced) with win-rate per source. The panel feeds both sales and marketing planning cycles.

Rep ramp curve

New-hire productivity versus benchmark.

The ramp panel renders a line per new-hire rep showing attainment by month-in-seat compared against the historical ramp benchmark. Managers use the panel to identify reps who are off the curve early and need additional enablement intervention.

Deal age distribution

Where deals are aging past healthy windows.

The age-distribution panel renders a histogram of deals by days in stage with a configurable healthy-window overlay. Deals outside the window get flagged. The panel sits on manager and VP dashboards for pipeline inspection.

Forecast delta from last week

How the forecast moved this week.

The delta panel decomposes week-over-week forecast change into deals added, deals removed, deals that moved amount, and deals that moved stage. The manager reads the panel in weekly forecast call rather than asking each rep to narrate the delta.

Open-task queue

The next-action list surfaced as a tile.

The open-task panel renders every task assigned to the viewer sorted by due date with the related record one click away. The panel is the dashboard's link from passive reading to active work.

Compensation estimator

Projected commission based on current pipeline and forecast.

The comp-estimator panel runs the current forecast through the rep's comp plan and projects quarter-end commission payout at the commit, best, and pipeline-weighted scenarios. The panel is motivational on AE dashboards and useful on manager dashboards for retention conversations.

Head-to-head

Strkr dashboards versus the common CRM dashboard builders.

Teams usually compare Strkr's dashboard surface against Salesforce reports and dashboards, HubSpot reports, and standalone BI tools (Looker, Tableau, Mode) that connect to the CRM through a warehouse. The comparison below focuses on the capabilities that make the dashboard examples above practical to ship.

Feature Strkr Salesforce Reports and Dashboards (standard)
Role-tagged tiles on one dashboard Native role-filter per tile Separate dashboards per role
Refresh cadence Per-tile from one minute to daily Dashboard-level with 15-minute floor
Cohort retention panel Built-in External BI tool typical
Deals-at-risk flag Strkr AI risk score native Einstein add-on SKU
Presentation mode Toggle on any dashboard Export to Quip or screenshot typical
Pipeline inspection panel Ships with the inspection view Separate feature SKU
Compensation estimator Native panel on AE boards External Spiff, CaptivateIQ, or build
Data-health board Ships with record-completeness tile Build using report types
Panel library 20-plus reusable panels Report-type templates
Price Included on every seat Reports included, Einstein and CRM Analytics separate
How teams use Strkr

How RevOps teams build dashboard libraries on Strkr.

Deployment snapshots from active tenants. Each one names the team size, which dashboards they stood up, and the friction the surface eliminated.

SaaS, 60-person sales team

Nine role-tagged dashboards replaced 23 inherited Salesforce dashboards.

A B2B SaaS company with 60 sellers consolidated 23 inherited Salesforce dashboards into nine Strkr dashboards tagged by role. The AE board, the manager board, the VP board, and the CRO board live on four URLs with role-aware tiles. Monthly dashboard-maintenance effort dropped from 14 hours a month in RevOps to 3 hours a month. The sellers report they open the dashboard three to four times a day rather than once a week.

Fintech, 22 enterprise AEs

Pipeline inspection and forecast-delta tiles cut weekly forecast call by 40 minutes.

A 22-AE fintech selling to banks used the pipeline-inspection and forecast-delta panels to run the weekly forecast call. Before Strkr the call ran 90 minutes with each AE narrating the delta on their deals. After Strkr the manager reads the delta from the panel and spends the time on three or four deals that need coaching. Average call length dropped to 50 minutes.

Agency, 11-rep team

The SDR weekly report tile became the Monday standup agenda.

An 11-rep agency sales team adopted the SDR weekly-report tile as the Monday standup agenda. The team opens the tile on the shared screen, walks the targets-actuals columns, and spends the remaining time on specific accounts that moved to AE. The standup moved from 45 minutes of status to 20 minutes of coaching.

Industrial equipment, 34 outside reps

Activity-floor panel surfaced the three reps blocking regional attainment.

A 34-rep outside sales team at an industrial-equipment distributor added the activity-floor panel to the manager dashboard. The surface identified three reps consistently under floor who were quietly driving regional under-attainment. Targeted coaching plus a route-planning intervention from Strkr field-sales features recovered two of the three within a quarter.

B2B marketplace, 7-person RevOps team

Data-health board unlocked trust in the executive forecast.

A B2B marketplace company with 7-person RevOps shipped the data-health board as the first dashboard the ops team opens each morning. Record completeness went from 68 percent to 94 percent over 90 days. Executive trust in the forecast number recovered, which the CRO cited specifically in a board update as the biggest ops improvement that quarter.

Ship a sales dashboard library in a week, not a quarter.

Open a free Strkr trial and clone the dashboard examples above into your tenant. Start with the AE daily board, the manager scorecard, and the CRO quarterly board; add RevOps and SKO shapes as the organization matures. The panel library grows every release.

Common questions

What buyers in this bucket ask most.

What panels should an AE dashboard start with?

The strongest AE dashboard starts with four panels: today's meetings and overdue follow-ups, this week's pipeline movement with deals advanced and deals slipped, deals-at-risk flagged by Strkr AI, and quarter-to-date attainment with a coverage ratio. These four panels cover the AE's daily, weekly, and quarterly views without becoming a 20-tile wall. Add a compensation estimator and an open-task queue if the AE wants a motivational surface and an action-oriented surface on the same page. Avoid starting with vanity tiles (number of calls made in the last 90 days) that do not change the AE's next action.

How often should sales dashboards refresh?

Refresh cadence depends on the panel. Activity tiles (calls made, meetings held) should refresh every one to five minutes so the rep sees the number move during the day. Pipeline tiles (deals in stage, forecast rollup) should refresh every five to fifteen minutes because they drive weekly cadence more than hourly. Cohort retention and win-loss panels can refresh daily or weekly since those are reviewed in longer cycles. On Strkr each tile carries its own refresh cadence so the whole dashboard does not share a single refresh floor.

How many dashboards should a sales organization maintain?

The answer depends on team size but the general shape is one dashboard per role rather than many dashboards per role. A 60-person sales team typically needs an AE board, an SDR board, an AM board, a manager board, a VP board, a CRO board, a RevOps data-health board, and a specialized SKO or kickoff narrative board. That is roughly eight dashboards for the organization rather than 23. The failure mode is maintaining dashboards per rep or per segment, which multiplies maintenance effort without improving decisions. Strkr role-tagged tiles let one URL render differently per viewer so the dashboard count stays low even when the organization is large.

Can I build these dashboard examples in Salesforce?

Most of the panels can be built in Salesforce reports and dashboards or in CRM Analytics with configuration effort. Specific panels that are harder to build native: deals-at-risk based on an AI risk score (requires Einstein for Sales or similar add-on), cohort retention curve (typically lives in an external BI tool connected to a warehouse), compensation estimator (typically external Spiff or CaptivateIQ), and the presentation-mode toggle for SKO narrative. The practical difference is time to assemble and ongoing maintenance; Strkr ships the panel library so composition is minutes rather than weeks. Salesforce can get there with investment, and for teams already running a mature Salesforce dashboard practice there is no reason to migrate purely for dashboards.

Do I need a BI tool like Looker or Tableau if I use Strkr dashboards?

For most mid-market sales organizations, no. The Strkr panel library plus the role-tagged tile model covers the full sales analytics surface described on this page. BI tools stay valuable for cross-functional analytics that span sales, product, finance, and support where a warehouse is already the source of truth. For sales-only analytics the warehouse-to-BI roundtrip adds latency and maintenance for marginal gain. Teams with mature BI practices often connect Strkr data to their warehouse through the Strkr open API and run cross-functional dashboards in Looker while running operational sales dashboards directly in Strkr.

How do I prevent dashboard sprawl?

Four practices keep dashboard sprawl in check: name an owner per dashboard, retire dashboards that have fewer than ten unique viewers per week, require a stated audience and a stated decision on every dashboard before it ships, and audit the dashboard list quarterly. Strkr's dashboard-usage telemetry shows unique viewers and view counts per dashboard so the retire-the-unused step is a report rather than a judgment call. The role-tagged tile model also helps because one dashboard serves multiple audiences, which reduces the pressure to proliferate.

Try it free. Bring your team next week.

No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.