What is dashboard software?
Dashboard software is a visualization layer that displays key metrics as charts, tiles, and tables for a specific audience. The best dashboards answer the one question a role wakes up with: a rep sees what to do today, a manager sees the team's week, a leader sees the quarter against plan. Dashboard software typically includes a widget library (chart types), a composition surface (drag and drop), filter controls, and delivery options (email, Slack, PDF, mobile). Strkr's dashboard surface is native to the data layer, so no ETL pipeline is required; the widgets query live or cached directly against production records.
What are examples of good dashboards?
Three widely useful templates. (1) The sales rep home: today's meetings with AI prep briefs, open deals ranked by close date, stale commits (no activity in 10 days), unanswered inbound emails, forecast submit widget. (2) The sales leader strategic: quarter attainment, 8-week commit trend, segment breakdown, cycle-time trend, win-rate trend, top-5 largest deals with AI grade. (3) The CSM portfolio: account health scores, at-risk accounts, renewal pipeline next 90 days, usage trend, support ticket volume, QBR schedule. Each role gets a different default; Strkr ships them as role-keyed templates with per-user overlay for customization.
Can I create custom dashboard widgets?
Yes. Two layers. Users can add, remove, reorder, resize, and save alternate views without a configuration step (user-level overlay on top of the role template). Admins can author new widget types from parameterized SQL for tenant-specific metrics (a unique conversion metric, a split-cohort analysis, a vendor-side KPI). Custom widgets ship with the same drill-through, filter support, and permission layer as native ones. For teams running custom widgets at scale, the admin surface supports version history and A/B comparisons before promoting a new default.
Does the dashboard work on mobile?
Yes. The dashboard surface is mobile-responsive by design. Widgets reflow from a four-column desktop grid to a two-column tablet grid to a single-column phone grid, with every widget rendering readable at every width. Charts render as mobile-friendly SVG. The native mobile apps cache the latest fetched state for offline viewing. Scheduled email and Slack delivery means the dashboard also lands in the recipient's inbox and messaging tool without opening the app. The dashboard is a tool for the field user, not just the HQ desk.
How is this different from a BI tool like Tableau?
A BI tool is more flexible but requires a data pipeline from your source systems. Someone maintains the ETL, keeps the schema aligned, handles data drift. For a growing revenue team the hidden cost of the pipeline (plus the BI license) is often more than the dashboard itself delivers. Strkr's dashboard is native to the record layer, so no pipeline exists; the data is in-product, widgets query it live, and role templates ship as defaults. Teams that still want BI for financial or cross-system analysis can keep it; the Strkr dashboard replaces the CRM-centric BI use case cleanly.
Does the dashboard respect permissions?
Yes. Dashboards and widgets both respect the user's permission layer. A rep sees widgets scoped to their territory, team, and record access. A finance-tagged widget (ARR, LTV, CAC) is only visible to users with finance.view. A team-level activity widget is only visible to managers. The gate applies at the widget level, not just the record level, so a leader's view and a rep's view can share an underlying template but render different content based on who is viewing. All access writes to the audit log for compliance review.
How many dashboards does a typical team run?
The pattern we see across tenants: 4 to 6 dashboards get real daily use, another 8 to 12 get weekly review, and the rest decay. Strkr surfaces usage stats so admins can retire the ones that stopped getting opened six weeks ago. A 50-rep team typically runs 5 role-templates (SDR, AE, manager, leader, CSM), 3 team-level operational dashboards (Monday rollup, risk digest, forecast delivery), and 2 to 4 team-specific custom dashboards. More than 15 total starts creating confusion about "which dashboard is the real one," which is a sign to consolidate.
Can we deliver dashboards to Slack or email on a schedule?
Yes. Scheduled delivery runs on cron syntax or human-friendly schedule shorthand ("every weekday at 8am," "every Friday at 4pm"). The delivery can go to a Slack channel, a DM thread, a shared email alias, or an individual user. The content renders as inline images with a link to the live view for drill-through. The pattern we see most often: Monday 8:30am rollup to the sales channel, daily 7am risk digest to the manager, Friday 4pm forecast snapshot to the CFO. The schedule is as important as the dashboard itself because it drives the cadence of attention.
What happens if the underlying data changes format or a field gets renamed?
Strkr tracks widget-to-field dependencies. When a field gets renamed or deprecated, dashboards referencing it get a migration prompt rather than a silent break. For custom SQL widgets authored by an admin, the version history shows which fields each query touches, so the admin can patch before the deprecation lands. The alternative, discovering 20 dashboards broke overnight because a column got renamed, is a well-known BI-tool failure mode we have avoided by design.
