Every CRM vendor ships a screenshot of a KPI dashboard. The ones below are patterns Strkr customers run in production every week, built on live records, drilled through to the deal or the account, and shared with executives who ask hard questions. Pick a shape, clone it, swap the filters for your segments, and ship it before standup.
A screenshot of a dashboard proves nothing. A dashboard that survives six months of use, that an executive opens on Monday without asking "which rep is this filtered to," that drills into the record that owns the number, and that updates in real time as the week unfolds, is the only example worth copying. These eight properties separate a decorative dashboard from one your team runs by.
Every number resolves against the live CRM record at the moment the dashboard loads. Change a deal's amount or stage and the tile moves on the next refresh. No overnight ETL, no stale snapshot, no explanation of why the number differs from what the rep sees in the pipeline view.
Every tile is a filter. Click the "$1.2M committed" and the list opens with the 14 deals that make up the number, in the pipeline grid, with the same owner and stage filters applied. No tab-shuffling, no copy-pasting a filter into a view, no explanation of which deals rolled up to the tile.
Dashboards refresh on every record write that touches the underlying filter. A rep moves a deal to Closed Won, the "Closed MTD" tile ticks up before the Slack notification lands. No scheduled job, no "last updated 4 hours ago" caveat on the executive report.
The same dashboard renders differently per viewer. Reps see their own numbers by default, managers see their team's roll-up, executives see the full org. The underlying filters inherit from the Strkr permission model. One dashboard, every seat, no duplicated copies to keep in sync.
A viewer applies ad-hoc filters (segment, product line, region, source) without touching the saved dashboard. Their filter choice persists for their session, so refreshing the page keeps the slice. Admin edits to the base dashboard do not disturb viewer filters.
Share a dashboard via URL to anyone in the tenant with the right permission scope. External sharing (board members, investors) goes through a signed read-only link with optional expiration. No PDF export tradition, no quarterly "please recreate the board deck slide" ritual.
Export the underlying rows to CSV, snapshot the tile as PNG for a slide, or schedule the dashboard as an email to a distribution list every Monday 7 AM. Every path is included in the seat price. No external BI license, no third-party reporting SKU, no credit meter.
Every dashboard reflows to a single-column mobile view with the tiles stacked in priority order. Drill-through works from the phone. The executive opens the dashboard on the way to the board meeting and the numbers are the same ones in the slide deck.
Every example dashboard below can be cloned to your tenant in one click. The clone is editable. Rename, retitle, re-filter, add or remove tiles. The clone keeps nothing hardcoded. If a tile does not fit your segment, delete it and ship a replacement in minutes.
The weekly sales leadership dashboard answers five questions: What did we close last week? What is on the glide path to close this quarter? Where is the pipeline leaking? Who is at risk of missing quota? What should the forecast call focus on? These seven examples cover the shapes Strkr sales leaders run across SMB, mid-market, and enterprise motions.
A tile per segment showing current pipeline divided by quarterly plan. Green above 3x, yellow between 2x and 3x, red below 2x. Drill into a cell and the segment's pipeline opens in the deal grid. One dashboard answers "do we have enough shots on goal" in six seconds.
Three tiles on a seven-day rolling window with a sparkline for the trailing twelve weeks. Executives see velocity, not just this week's number. Drill into a tile and the list of closed deals opens with owner, segment, and source visible.
A horizontal funnel showing count and value at each stage, time-in-stage averages, and historical stage-to-stage conversion. The widening or narrowing of each band tells leadership which stage is leaking. Drill into a band and the stuck deals open.
Four tiles reflecting rep and manager roll-ups. Clicking "committed" opens the deals the rep marked commit. Clicking "gap to quota" opens the open opportunities ranked by close date and amount. The weekly forecast call becomes a shared read-only screen rather than a slide the ops team re-renders.
A sorted list of open deals with the highest at-risk score, surfaced by Strkr AI from engagement decay, stage-time anomalies, and competitor mentions. The sales lead works top to bottom in Monday's pipeline review. Drill into a row and the deal timeline opens with the signals highlighted.
A stacked bar per rep showing activity volume across call, email, meeting, and demo. The manager spots the quiet rep and the over-indexing rep in the same glance. Drill into a bar and the rep's activity feed opens filtered to the week.
A bar chart of win reasons and loss reasons from the deal close workflow. Price, product fit, timing, competitor, and no-decision each get a count. Managers see which reasons are growing. Drill into a bar and the loss debrief notes open for review.
The SDR and marketing dashboards answer different questions than the sales leadership set. They focus on top-of-funnel volume, conversion into the sales process, speed to lead, source attribution, and campaign ROI. These six examples cover the shapes Strkr customers use to run demand gen weekly standups.
A ranked table of SDRs with each column tied to the real activity feed. Totals, averages, and quota-pacing all visible. The scoreboard updates in real time as reps clear their task queues. Drill into a row and the SDR's cadence output for the week opens.
A tile showing average speed-to-lead for inbound form fills on a seven-day window. Benchmarks against last quarter. Drill-through to the slowest 20 leads so the SDR lead can diagnose the lag. Teams running Strkr's inbound routing flow average under two minutes to first human touch.
A grouped bar chart showing lead-to-opportunity conversion over the trailing 90 days. Breakout by source (paid, organic, event, referral), by SDR, and by segment. The marketing lead and the SDR lead see the same chart and have a short conversation instead of a long debate.
A row per campaign with the full funnel from spend to closed revenue. Pipeline-generated and closed-won columns use the Strkr source attribution to tie dollars back to the campaign that opened the deal. Marketing teams renew spend based on the row, not the gut call.
A funnel showing MQL volume, SQL acceptance rate, and the handoff lag in hours. The three leak points (reject, timeout, re-route) each report their own count. Drill into any band and the leaking records open for review.
A table of content assets with first-touch, last-touch, and multi-touch deal counts. The marketing team sees which eBook, demo video, or pricing page actually appears in winning deal timelines. The content calendar reorders based on evidence.
The operations and customer success dashboards track the back half of the revenue motion: retention, expansion, support SLA, renewal risk, and the data-quality signals that keep the rest of the dashboards honest. These seven examples cover the shapes Strkr customers run in post-sale operations.
A cohort heatmap showing NRR for each monthly signup cohort over the trailing twelve months. Green cohorts expand, red cohorts contract. Drill into a cohort and the customers inside open for a CSM review. Board-level NRR becomes a working surface, not a quarterly PDF.
A list of accounts up for renewal in the next 90 days, ranked by Strkr AI risk score. Signals include engagement decay, open support tickets, usage drop, and payment-health flags. The CSM lead works the list top to bottom in weekly ops review.
A pipeline view scoped to expansion opportunities, grouped by CSM, with stage-weighted amount and close date. The CSM team runs forecasting on expansion the same way AEs forecast new logos. Drill into a stage and the deal grid opens.
Three tiles with trailing seven-day numbers for first-response time, resolution time, and SLA breach count. Drill into breach count and the breached tickets open for triage. Support leads brief the executive team off the same tile the agent sees.
A composite account health score across usage, support, billing, and engagement, rolled up by segment. Green, yellow, red bands show where the book of business is drifting. The health score weights are configurable per tenant so the dashboard reflects your actual definition of a healthy account.
Three tiles showing counts of records missing required fields, records not touched in 60 days, and probable duplicates flagged by Strkr AI. Drill-through surfaces the records themselves. RevOps triages data quality off the same dashboard every week.
A tile per billing state: failed-charge count, past-due AR, accounts in dunning, and recovered revenue month-to-date. The finance team and the CSM team review the same surface so a payment failure never becomes an account save surprise.
Lifting a dashboard example into your tenant is only useful if the underlying mechanics match. These six properties are what Strkr dashboards do differently from the generic BI templates you can find on a vendor blog.
Strkr dashboards do not require a Tableau, Looker, or Mode license. The engine is part of the CRM seat price. There is no secondary vendor relationship, no connector, no data warehouse to maintain, and no credit meter on query volume. Clone a dashboard, run it, share it.
Tiles reference the same objects, fields, and relationships the rest of the product uses. Custom fields are automatically available. Custom objects are first-class. There is no mapping layer, no "which column is amount" ambiguity, and no sync lag between the CRM and the dashboard.
A rep opening a leadership dashboard sees only the records their permission scope allows. Managers see their teams, executives see the org. The permission model is enforced at the data level, not the dashboard level, so a sharing mistake cannot leak records a viewer should not see.
Set a threshold on any tile (SLA breach above zero, coverage ratio below 2x, failed charges above $10K). When the threshold trips, the dashboard sends a Slack or email alert to the owner. The dashboard stops being a passive display and becomes a notification surface.
Dashboard tiles embed inline on account and contact detail pages. The CSM opens an account and the renewal risk, support SLA, and expansion pipeline tiles render inside the record. No tab-shuffling between the dashboard and the account the CSM is working.
Every tile addition, filter change, and permission edit on a dashboard is logged with actor and timestamp. A tile that reports a different number this quarter versus last quarter has a traceable edit history. RevOps investigates "why did the number change" with a query, not a group chat.
Start a trial, pick a dashboard shape that fits your motion, clone it to your tenant, swap the filters for your segments, and share it with your team before standup. No BI license required, no sync job, no credit meter.
Each example is a shape Strkr customers run in production weekly. The screenshots are rendered against anonymized tenant data from live installations. You can clone any of the shapes to your own tenant in one click, swap the filters for your segments, and ship your version before standup. The tiles reference the same objects and fields your CRM already has, which keeps the clone useful rather than aspirational.
No. The Strkr dashboard engine is included in the CRM seat price. There is no secondary vendor relationship, no connector to maintain, no data warehouse to stand up, and no credit meter on query volume. Clone a template, edit the tiles, and share the URL. External BI tools can still consume the data through the Strkr API if your team already runs on one, but they are not required for any of the examples below.
Three ways. First, the data is live rather than snapshot-based, so a tile moves within seconds of the underlying record changing. Second, drill-through opens the records that make up the number in the standard CRM grid, not a separate reports module with its own filters. Third, the engine is included rather than gated behind a reporting SKU or an Analytics tier upgrade, so there is no incremental cost per dashboard, per viewer, or per export.
Yes. The permission model is inherited from the CRM itself. A rep opening a leadership dashboard sees only the records their role scope allows, so their coverage ratio reflects their own pipeline. A manager sees the team roll-up. An executive sees the full org. One dashboard, three audiences, no duplicated copies to keep in sync.
Yes. Every tile accepts a threshold rule (SLA breach above zero, coverage ratio below two, failed charges above a dollar amount) with a corresponding Slack or email alert routed to the owner. The dashboard stops being a passive display and becomes a notification surface. Alert history is logged alongside the dashboard's edit log for audit review.
Yes. External sharing goes through a signed read-only link with optional expiration and optional password protection. The link renders the dashboard with the same drill-through and filter mechanics, scoped to the share's permission grant. No external user needs a seat in your tenant. The share is auditable: every open is logged with timestamp and viewer IP.
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.
