What is business dashboard software and how is it different from a general BI tool?
Business dashboard software is purpose-built for the specific question set a business runs on a weekly or monthly cadence: pipeline pacing, revenue pacing, customer health, campaign ROI, operational KPIs. The tool is designed to be used by the business owners of the data (executives, operators) rather than by a dedicated analytics team. A general BI tool like Tableau or Looker is more flexible but requires more technical expertise to configure and typically runs against a separate data warehouse. Strkr's business dashboard software runs natively on the CRM, respects the same permission model, and ships with role-based templates for the common functions. The difference is specificity: Strkr knows what questions revenue teams actually ask and ships the tiles to answer those questions, while a general BI tool is a canvas on which someone has to design each surface.
Can we have one dashboard that shows different data to different users based on their role?
Yes, and this is one of the specific advantages of a dashboard tool built inside the CRM rather than bolted on. The permission model enforces at the query layer, so a single shared dashboard shows one data set to a rep (their own records), a different data set to a manager (their team), and a different data set to the CRO (everything). The dashboard definition is one artifact. The data each user sees is scoped by their role, their team, their territory, their segment, or any other dimension the permission model considers. This eliminates the "I need my own version of the dashboard" proliferation and keeps the shared dashboard as the single source of truth for the organization while respecting data boundaries at the viewer level.
How does the Strkr AI assistant integrate with dashboards?
The assistant integrates in four specific ways. First, narrative tiles: a tile at the top of the dashboard carries a plain-English summary of the key numbers, direction, and risks, drafted by Strkr AI nightly. Second, anomaly detection: the assistant watches the dashboards and flags unusual movements with the signal driving the flag. Third, natural-language queries: a query bar on the dashboard accepts questions in natural language and the assistant interprets, pulls data, and returns the answer. Fourth, scheduled digests: a flow generates a weekly email summary of what the dashboards reveal. All four integrations respect the user's permission context, so the assistant never leaks data across role boundaries. The combined effect is that a dashboard shifts from a static display to an active conversation partner that highlights what the reader might miss.
What templates ship with Strkr's business dashboard software?
The template library covers the common functional dashboards for revenue teams. Executive summary dashboard (CEO/COO/CRO weekly briefing). Sales operations dashboard (pipeline, forecast, risk, activity, coverage). Marketing operations dashboard (pipeline contribution, campaign ROI, funnel conversion, channel attribution). Customer success dashboard (account health, renewals, expansion, tickets). Rep performance dashboard (individual rep activity, pipeline, win rate, quota attainment). Finance operations dashboard (ARR, billing, dunning, cash projection). Deal health dashboard (every open deal risk-sorted with reasons). Each template is a starting point the admin customizes for the specific tenant through the dashboard builder. Beyond the templates, the builder supports any custom dashboard the function needs.
How does scheduled delivery of dashboards work?
Any dashboard can schedule to a PDF, PNG, or scheduled email delivered to a distribution list on a configurable cadence (daily, weekly, monthly, quarterly). The delivery format carries the full tile layout, the current data at delivery time, and a link back to the live dashboard for drill-in. The distribution list can include internal users and external email addresses with permission scoping on which recipients see which data. For executives who prefer a predictable cadence, the Monday morning weekly digest to the ELT distribution has become a common pattern. The schedule configures once and runs automatically, with the data refreshing on each delivery. Behind the scenes, scheduled delivery is a Strkr flow with a dashboard-snapshot action, so admins can also customize the delivery flow (add a narrative, append team-specific comments, route different versions to different audiences) with the same flow builder they use for other automations.
What is the performance like for dashboards against large datasets?
The dashboard engine is designed for operational scale, which for most revenue teams means millions of records across the standard objects. The common dashboards load in under two seconds against a book of 50,000 open deals or a trailing twelve months of pipeline history. For heavier dashboards (many tiles, complex joins, long time ranges), a smart cache layer keeps load times fast while invalidating on record writes so the user sees fresh data within a few seconds of a change. For truly massive datasets (billions of activity records across years), the engine applies time-partition optimizations and index strategies to keep common operational queries fast while deep historical queries run slightly longer. For edge cases that require joining CRM data with external datasets at scale, the Strkr open API exposes the data for external BI tooling, but the vast majority of revenue-operations dashboarding is well-served by the native engine.
