What makes a sales dash different from a BI dashboard?
Three things make a sales dash useful where a BI dashboard typically fails. First, data freshness. A sales dash reads from the live CRM record data, not a nightly warehouse sync, so the dash and the CRM show the same number within minutes of a rep updating a deal. Second, next-step prompts. A sales dash tells the rep what to do today: deals missing a next step, follow-ups due, discovery incomplete at the current stage. Classic BI dashboards show aggregate state and leave the rep to figure out the action. Third, risk flags. A sales dash includes a weekly scan surfacing the deals in trouble on the same screen as the pipeline coverage. The combination means reps open the dash on Monday morning because it is useful, not because leadership mandates it. Classic BI dashboards get opened once a quarter for the all-hands review and sit idle the rest of the time.
How does the risk-flag scan work?
A weekly AI job scans every open deal against a set of risk signals: no next step scheduled in the last 7 days, no multi-threading (only one contact engaged), no champion tagged, cycle extending past segment baseline, discovery incomplete at the current stage, Mobilizer not identified. Deals matching 2 or more signals get flagged red; deals matching one get flagged yellow. The flags surface on the sales dash and in the Friday forecast card. Managers running the scan intervene in week 2 of the risk pattern instead of discovering the problem at quarter close. Customer deployments report catching 7-figure deal recovery opportunities 3 to 6 weeks ahead of close, which translates directly to attainment and forecast accuracy. The scan runs automatically; admins can tune the thresholds per segment.
Can we add custom metric cards without a BI engineer?
Yes. The custom-cards surface in the Strkr admin lets any admin add new metric cards without a BI engineer. Pick the metric (e.g., ACV by vertical, demo-to-close by rep, specific product attach, retention expansion rate), pick the segmentation (by rep, by segment, by vertical, by product line), pick the visualization (number, bar, trend line, heatmap), and the card lands on the dash. Admins can define per-role visibility (reps see their own metrics, managers see their team, CRO sees aggregate). The surface is deep enough to replace most BI dashboard use cases for operational metrics. Deep ad-hoc analysis (cohort retention, LTV modeling, custom attribution) still typically runs in a BI tool, but the day-to-day operational metrics live on the dash.
What happens when we have thousands of open deals across hundreds of reps?
The dash scales. Enterprise customer deployments with 500+ reps and 15,000+ open deals run the dash with per-role filtering: a rep sees their own pipeline, a manager sees their team, a director sees their segment, the CRO sees the aggregate. The risk-flag scan runs across the full deal set and surfaces team-level, segment-level, and aggregate flag counts. Admin-defined custom cards can slice by any segmentation the business cares about. Performance remains responsive because the dash reads from indexed live data rather than a nightly warehouse sync. The limits (how many cards per dash, how many open deals before performance degrades) are documented in the admin guide; the practical ceiling has not been hit by any customer deployment to date.
How does the dash integrate with existing BI tools like Tableau or Looker?
Three integration patterns. First, no integration: many customers find the Strkr dash sufficient for the operational cadence and retire the Tableau or Looker dashboards for sales operations. The retention of the BI tool for finance, marketing, or product analytics continues; the sales dash in Strkr is complete. Second, warehouse export: Strkr integrates with Snowflake, Redshift, and BigQuery via near-real-time CDC (change data capture) so BI tools can continue to pull the data for deep ad-hoc analysis. The warehouse data is minutes-fresh instead of hours-stale. Third, iframe embedding: Strkr dash cards can be embedded in a Looker or Tableau layout for teams that want to keep a single BI entry point while still getting the sales-specific primitives (next-step prompts, risk flags) that Strkr provides natively. Most customers end up on pattern one or pattern two; iframe embedding is the minority use case.
What are the limits of a sales dash?
Three real limits. First, the dash reports what is captured. If the pipeline hygiene is weak (missing stage transitions, dirty activity data, duplicate accounts), the dash numbers reflect the dirty inputs. Fix the hygiene first; the dash becomes useful. Second, the dash surfaces risk; the manager still has to coach. A risk flag on the dash tells the manager a deal is in trouble; the manager still has to run the intervention conversation. Teams that treat the dash as a substitute for 1:1 coaching see partial returns. Third, deep ad-hoc analysis still runs in a BI tool. Cohort retention, LTV modeling, custom attribution, and other analytical workloads live in Looker, Tableau, or dbt. The dash covers the operational cadence (daily, weekly, monthly); the BI tool covers the analytical cadence (quarterly deep-dives). Teams running both the dash and the BI tool get the right surface for the right job. Teams expecting the dash to replace all BI see partial returns.
