Feature · Dashboard Application

A dashboard application that is also where the work happens.

Most dashboard applications are destinations. The viewer leaves whatever work they were doing, opens a separate URL, consults the chart, and goes back. Strkr builds the dashboard application into the operating surface, so the viewer never leaves the record to see the number. The pipeline dashboard sits inside the CRM. The forecast dashboard sits on the forecast page. The account health dashboard sits on the account record. Dashboard-as-destination becomes dashboard-as-context, which is a different kind of useful.

Start free trial See pricing
What dashboard-as-context means in practice

The nine places a tile earns its keep on the record it describes.

A dashboard application that is a destination requires a trip. The viewer leaves the record, opens the dashboard, hunts for the right filter, finds the number, and returns. A dashboard application embedded on the record removes the trip. The number is in the viewer's eyeline the moment they open the surface. The sections below walk the nine places this pattern shows up in Strkr and the numbers each embedded dashboard carries.

Account record dashboard

Health, ARR, open deals, support tickets.

The account page carries a health score, ARR, open pipeline, trailing-12 revenue, open support tickets, and renewal date on an embedded tile band. The account owner opens the record and sees the operating picture of the account in the hero. No navigation to a separate dashboard required.

Deal record dashboard

Risk, next step, activity shape, forecast category.

The deal page carries the risk score with reasoning, the suggested next step, the activity-shape sparkline, the forecast category, and the stage-age indicator on an embedded tile. The rep updating the deal sees the model-called risk tier alongside their own gut call.

Rep home dashboard

My pipeline, my tasks, my week.

The rep home page carries personal pipeline coverage, open tasks, weekly activity goal progress, and the rep's own quota attainment. The rep opens the home page and sees the shape of their week in under 10 seconds, no filter configuration required.

Manager home dashboard

Team pipeline, slip queue, coaching candidates.

The manager home page carries the team pipeline, the slip queue sorted by risk-value, the coaching candidate list, and the aggregate attainment. The manager opens the home page and knows which three reps to check on first and which three deals to escalate.

VP home dashboard

Floor rollup, forecast delta, risk concentration.

The VP home page carries the floor-level forecast with committed and model-weighted numbers, the forecast delta week over week, the risk-concentration by segment, and the pipeline coverage by product line. The VP sees the operating picture of the floor at the altitude they operate at.

Pipeline page dashboard

Stage mix, aging, win rate on the kanban.

The pipeline page carries an embedded header with stage-mix distribution, aging indicators per stage, and win-rate trend. The viewer scrolling the kanban sees the aggregate shape at the top of the page without a trip to a separate dashboard.

Forecast page dashboard

Committed vs model, deal-level deltas.

The forecast page carries the committed, best-case, and model-weighted numbers at the top, with the deal-level delta list below. Each delta shows the rep-called category next to the model-called category. The forecast page is itself the dashboard; nothing is hidden on a different URL.

Lead queue dashboard

Response time, score mix, source distribution.

The lead queue page carries an embedded header with the current response-time average, the score tier distribution, and the source mix. The SDR working the queue sees where the queue is backing up before picking the next lead.

Campaign page dashboard

Opens, replies, conversions, cost per MQL.

A campaign page carries embedded performance tiles: email open rate, reply rate, SQL conversion rate, cost per MQL, cost per closed-won. The marketer running the campaign sees the operating numbers on the campaign surface, not on a separate attribution dashboard.

How the embedded dashboard is still a configurable application

The capabilities that keep the dashboard flexible when it is also contextual.

Embedding dashboards on the record is useful only if the embedded tiles are still configurable by the admin and savable by the viewer. A rigid embedded tile is worse than a destination dashboard because it cannot adapt to the viewer's need. Strkr builds the embedded surfaces as fully configurable dashboard applications. The sections below walk the capabilities that preserve the flexibility.

Admin configures per role

The rep sees different tiles than the manager.

Admins configure the embedded dashboard shape per role. The rep home carries personal tiles. The manager home carries team tiles. The VP home carries floor tiles. Each role sees the right altitude of information for the decisions they make. The configuration is a tenant-level setting, not a code change.

Viewer saves variants

Private views on top of the shared base.

A viewer can save a private variant of the embedded dashboard: hide a tile they do not care about, add a tile the admin did not configure, reorder the tiles to match their mental model. The private variant persists for the viewer without changing the shared base.

Filters hold across pages

A segment filter applied once, applied everywhere.

When the viewer filters by a segment on one dashboard, the filter persists across other dashboards in the same session. The EMEA mid-market view the viewer selected on the pipeline dashboard stays applied when they open the forecast dashboard. The cross-page continuity reduces re-filtering friction.

Drill-through within context

A tile opens the right scoped list.

Tapping a tile opens the record list that drove the number, filtered to the current scope. From the account page, a tapped tile opens the deals on that account. From the pipeline page, a tapped tile opens the deals in that stage. The context carries through to the detail view.

Share a view

A view URL carries the full scope.

A viewer sharing a dashboard view does so by URL. The URL carries the dashboard, the filters, the saved variant, and the scope. The recipient (with permission) sees the same view the sender saw. Sharing a dashboard becomes a one-click action, not an explanation.

Permission-respected

Shared views mask what the recipient cannot see.

When a view is shared with a user whose permission scope excludes some of the records in the view, the view masks those records rather than failing. The recipient sees what their permission allows. The share is secure by default.

Export anywhere

Any tile exports to CSV or PDF.

Any tile, embedded or standalone, exports to CSV (for the underlying data) or PDF (for the rendered tile). The export runs under the viewer's permission scope. The viewer can take a slice of the dashboard into a board deck or a finance analysis without a reporting-tool trip.

Embed into external apps

A Slack, a Notion, an email.

A dashboard tile can embed into a Slack message, a Notion page, or an email with a signed URL. The embed respects the viewer's permission on each render. Teams running weekly status in Slack can embed the live pipeline tile rather than paste yesterday's screenshot.

Admin audit

The admin sees who viewed what.

The admin console shows every dashboard load with the viewer, the scope applied, and the timestamp. A security review on dashboard access runs on real logs, not reconstructed guesses. A dashboard that is sensitive (comp, forecast, exec attainment) carries explicit access-review requirements with audit coverage.

What the dashboard application does that spreadsheets never will

The structural advantages of a native application over a stitched sheet.

Teams moving from a spreadsheet or a Google Looker Studio dashboard to a native dashboard application unlock capabilities that are structurally unavailable in the sheet-based pattern. The sections below walk the unlocks that justify the migration.

Live state

The dashboard loads current data, every time.

A sheet runs on the last-pasted CSV. A sheet-based dashboard shows yesterday's numbers on Monday morning. A native application reads live data on every load. The viewer sees the current pipeline, not a snapshot of the past. Decisions off a native dashboard are based on current state.

Role scope

The same URL renders viewer-specific.

A sheet-based dashboard requires a copy-and-maintain pattern per role. A native application applies the viewer's permission scope at render time. One canonical dashboard, many viewer-specific renders, zero maintenance overhead per role addition.

Drill-through

Tap a tile, see the records.

A sheet-based dashboard shows an aggregate. The viewer wondering about the underlying records has to open a different sheet. A native application lets the viewer tap the tile and see the records. The aggregate and the underlying list are two clicks apart on the same surface.

Audit coverage

Every number traces back to a record change.

A sheet-based dashboard has no audit linkage to the source of truth. The viewer has to trust the pivot. A native application links every tile to the record changes that drove the number. A comp dispute is a two-second drill rather than a two-hour reconciliation.

Mobile parity

The phone render is the real render.

A sheet-based dashboard on a phone is a wall of frozen panes. A native application renders the same tiles natively on mobile with touch targets, drill-through, and native filters. The viewer on the road sees the same operating picture as the viewer at a desk.

Alerts and anomalies

A sheet does not watch itself.

A sheet never notifies the viewer when a number moves. A native application watches tiles and pushes alerts when thresholds breach. The manager wakes up to a push alert rather than discovering a problem at the Monday standup. The lag between problem and detection shrinks from days to minutes.

Share and embed

The dashboard travels with context.

A sheet shares as a link, an image, or a copy that drifts from the original. A native application shares with the full context: scope, filters, saved variant, permission check on the recipient. The embed in Slack or an email renders live and secure.

Scheduled digests

The dashboard pushes to the inbox.

A sheet never pushes. The viewer has to remember to open it. A native application schedules PDF or inline-email digests at any cadence. The weekly rollup lands in the inbox before the Monday standup, every week, without a human remembering.

AI commentary

The dashboard explains itself.

A sheet shows the number. A native application writes the explanation underneath. Strkr AI tells the viewer why pipeline coverage dropped, which deals drove it, and which coaching conversations would move it. The explanation is the compounding advantage of a native application over a static sheet.

The patterns Strkr customers run on the embedded dashboard

Three operating cadences the application supports natively.

The embedded dashboard application earns its keep in specific operating cadences. The three patterns below are the ones Strkr customers run on the embedded surfaces every week. Each demonstrates where the context-on-record pattern saves a measurable number of minutes per cycle.

Account check-in

The CSM opens the account, sees the health picture.

A CSM opening an account record sees the health score, the ARR, the trailing revenue, the open support tickets, and the renewal date on the embedded header. The pre-call pattern that used to take 15 minutes of hunting through tabs becomes a 90-second glance. The CSM walks into the call informed.

Deal coaching

The manager opens the deal, sees the risk picture.

A manager opening a deal in a 1:1 sees the risk score with reasoning, the activity-shape sparkline, the suggested next step, and the forecast category on the embedded header. The coaching conversation starts at the altitude of the data, not with "catch me up on this deal."

Forecast call

The VP opens the forecast page, runs the call.

The forecast call opens on the forecast page with the committed, best-case, and model-weighted numbers embedded at the top. The deal-level deltas are below. The call runs on the surface itself, not through a parallel dashboard tab. The VP sees the shape of the quarter and the deals driving the delta on one page.

A dashboard application that puts the right tile on the record you are already looking at.

Open a free trial, enable the embedded dashboard surfaces, and watch the account, deal, pipeline, forecast, lead queue, and campaign pages all carry their own live tiles. Role-scoped, drill-through, mobile-parity, share-ready. The seat price is the full price for the capability. No credit meter, no viewer-based pricing.

Start free trial See app dashboard
Common questions

What buyers ask about this feature.

What is the difference between a dashboard application and a dashboard embedded on a record?

A traditional dashboard application is a destination: the viewer leaves the current work, opens a separate URL, consults the chart, and comes back. Strkr builds the dashboard application as both a destination (for the full exploratory view) and an embedded surface (for the record-contextual view). The embedded view carries the tiles that are relevant to the record the viewer is on. An account record carries account-specific tiles. A deal record carries deal-specific tiles. The pattern eliminates the context switch between the work and the data, which is the main source of friction in a destination-only dashboard.

Can we configure what tiles show on each embedded surface?

Yes. Admins configure the embedded dashboard shape per role and per record type. The account record embedded dashboard carries different tiles for a rep than for a CS manager than for an exec. The deal record embedded dashboard carries different tiles for an AE than for a sales manager. Viewers can save private variants on top of the shared base to hide tiles they do not care about or add tiles the admin did not configure. The configuration is a tenant-level setting; the private variants persist per viewer without changing the shared base.

Does the dashboard application integrate with Looker, Tableau, or Power BI?

Yes. Strkr integrates with Looker, Tableau, and Power BI for the use cases that genuinely need a warehouse-backed analytics tool: cross-system exploratory analysis, executive QBR decks, finance deep dives. The native dashboard application covers the operational cadences (Monday standup, mid-quarter forecast, Friday review, account check-ins); the analytics tools cover the exploratory cadences. The two coexist cleanly rather than competing. Strkr can push data to a warehouse for the analytics stack and read the warehouse back for cross-system tiles when needed.

How does the mobile experience work for the embedded dashboards?

The embedded dashboards reflow natively on mobile. Tiles stack to a single column with the ordering reflecting importance. Touch targets are thumb-sized. Drill-through, filters, and share actions all work with native touch interactions. The embedded account dashboard renders on the mobile account page. The embedded deal dashboard renders on the mobile deal page. A rep on the road opening an account between meetings sees the same tiles they would see at a desk, with the mobile UX that native apps require. Dark mode and offline-tolerance both apply.

Can we embed Strkr dashboards into Slack or an external tool?

Yes. Any tile or dashboard can embed into Slack, Notion, an email, or an iframe-friendly external tool with a signed URL. The embed renders live and respects the viewer's permission on each load. Teams running weekly status in Slack can embed the live pipeline tile rather than paste yesterday's screenshot. Teams running an internal portal in Notion can embed the forecast tile on their RevOps page. The embed is a one-click action from the dashboard menu, and the signed URL expires on a configurable schedule for security.

Is the dashboard application included on every tier?

The embedded dashboard application ships on every paid Strkr tier. The default embedded surfaces (account record, deal record, rep home, manager home, pipeline, forecast, lead queue, campaign page) are included out of the box. Admin configuration of per-role tile sets, private viewer variants, cross-page filter persistence, and share-with-signed-URL embedding are included on Pro and above. Scheduled digests on embedded surfaces, Strkr AI commentary on embedded tiles, and multi-provider warehouse integration are included on Scale and Enterprise. There is no separate dashboard SKU, no per-view charge, and no viewer-based pricing. The seat price listed on the pricing page is the full price.

Related features

Pair this with...

App Dashboard Dashboard Apps CRM Dashboard Business Dashboard Software KPI Dashboard Sales Dashboard Dashboard Software

Try it free. Bring your team next week.

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.

Start free trial See pricing