What is a CRM dashboard?
A CRM dashboard is a visual summary of the key metrics a revenue team uses to run the business. It typically includes pipeline health (deal counts and amounts by stage), activity trend (calls, emails, meetings over time), quota attainment (closed-won against the quarter target), rep leaderboard (attainment by rep), and deal-risk flags (AI-graded commits). 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. Strkr's dashboard is role-shaped so each role gets the right default view without a configuration step.
What CRM dashboard examples work best for sales teams?
Three templates we see work across most mid-market sales teams. (1) The AE Home dashboard: today's meetings with AI prep briefs, open deals ranked by close date, stale commits (no activity in 10 days), unanswered inbound emails, and the forecast submit widget. (2) The Sales Manager dashboard: team roll-up (direct reports with commit, variance, slip count, AI risk count, accuracy score), top-10 commit deals across the team, red-flag list, team activity trend. (3) The Sales Leader dashboard: quarter attainment against plan, 8-week commit trend, segment breakdown, cycle-time trend, win-rate trend, top-5 largest deals with AI grade. Each ships as a default template in Strkr; users overlay their own preferences on top.
Can I customize the CRM dashboard?
Yes. Two layers of customization. First, admin-level: admins own the per-role default templates and can add, remove, reorder, or resize widgets for everyone in a role. Second, user-level: any user can overlay their own preferences (add widgets, hide widgets, save alternate views) without touching the role template. When admin updates the role template, the user's overlay persists. Admins can also author custom widgets from SQL for tenant-specific metrics that are not in the standard library, which show up alongside native widgets with the same drill-through and filter support.
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 one-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 (rep in a tunnel or on a plane can still see the morning snapshot). Scheduled email and Slack delivery means the dashboard also lands in the recipient's inbox and messaging tool without opening the app.
How is this different from using a BI tool like Tableau or Looker?
A BI tool is more flexible but requires a data pipeline from your CRM. Someone maintains the ETL, keeps the schema aligned, handles data drift, and configures the dashboards. For a growing revenue team the hidden cost of the pipeline (and the BI license) is often more than the dashboard delivers. Strkr's dashboard is native to the record layer, so no pipeline exists; the data is in-product, the widgets query it live or cached, and the role templates ship as defaults without a configuration project. Teams that still want BI for financial or cross-system analysis can keep it; the Strkr dashboard replaces the CRM-centric BI use case.
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 widget showing financial detail (ARR, LTV, CAC) is only visible to users with finance.view. A widget showing team-level activity is only visible to managers. The permission gate applies at the widget level, not just the record level, so a leader's dashboard and a rep's dashboard can share the same underlying template but render different content based on who is viewing. All access writes to the audit log.