Opening proof path
SIRJ is loading the workspace, connector, or public page with the same proof path intact: ad spend, lead, booked job, invoice, paid.
See how SIRJ turns connected sources into dashboard readiness, metric cards, source health, activity, Ask Data prompts, and next-source guidance.
Buyer answers
The dashboard page explains what the active workspace shows, how cards unlock, why missing data stays visible, and how the same context feeds Ask Data and reports.
The workspace shows the active client, date range, dashboard readiness, connected source health, Ask Data bar, available cards, and recent activity. Empty or partial stacks keep setup guidance visible instead of pretending a complete attribution board exists.
A buyer can tell whether the workspace is ready for revenue proof, which sources are present, and which next connection would unlock better answers.
Follow the workspace pathCards unlock from normalized event types and provider categories. Spend enables ad spend and campaign performance, revenue enables revenue cards, spend plus revenue unlocks ROAS, lead sources unlock lead tables, form sources unlock form conversion, and CRM sources unlock pipeline views.
The page makes the product rule visible: no source capability, no unsupported card. That restraint helps buyers trust the dashboard before a report or AI answer uses it.
Follow the workspace pathDashboard readiness summarizes connected providers, missing capabilities, attribution-path requirements, dashboard-complete status, and the next source gap so the account knows whether to connect ads, leads, revenue, or communication evidence.
Instead of burying setup work, the workspace shows why a metric is missing and which source would make the next client question answerable.
Follow the workspace pathAsk Data reads the current dashboard context before answering supported questions, while reports freeze dashboard cards, source rows, campaign performance, insights, and recommendations into client-ready exports or weekly delivery.
The dashboard is the shared source of truth for the workspace, assistant, weekly report, and export path rather than a disconnected visualization layer.
Follow the workspace pathDashboard surfaces
SIRJ makes the workspace state easy to read: which parts are ready, which parts are waiting on source data, and where the buyer can inspect the path behind each claim.
What users see
This table makes the product surface explicit: what the workspace shows, which source path supports it, and what an incomplete client stack can prove.
| Surface | User sees | Source path |
|---|---|---|
| Readiness summary | A data stack status, connected provider names, next requirements, attribution-path readiness, and setup state inside the workspace. | Dashboard readiness reads scoped connections, provider categories, inferred event types, missing capability requirements, and attribution-path requirements. |
| Metric cards | Ad spend, revenue, and ROAS cards when spend and revenue evidence exists for the active client and date range. | Dashboard config filters scoped events by date range, sums spend and revenue, then unlocks cards only when the required event types are present. |
| Source and campaign tables | Lead source, campaign performance, form conversion, ROAS by channel, and pipeline tables when the connected stack supports those rows. | Table cards are assembled from normalized events, provider categories, matching paths, grouped rows, and bounded date-range filters. |
| Recent activity | Recent spend, lead, deal, payment, communication, and anomaly rows with provider context and source descriptions. | Activity rows combine scoped events and notification records, then render through escaped HTML so user-facing text remains safe. |
| Ask Data prompts and next gap | Suggested revenue questions when the stack can answer them, or a next-source recommendation when a useful source is still missing. | Dashboard blueprint generation reads source categories and card eligibility before creating suggested prompts, card rationale, and next-gap guidance. |
AI-assisted build and human review
Dashboard generation saves the spreadsheet work without hiding judgment. The workspace keeps source gaps, unsupported cards, and review paths visible before a report or weekly update leaves the team.
SIRJ assembles the first dashboard from source categories, event types, tenant scope, date range, card eligibility, and next-source gaps instead of starting from a blank template.
The account team reviews which cards unlocked, which metrics stayed hidden, and which source gap needs attention before treating the workspace as client-ready.
Follow the review pathBefore a dashboard becomes a report, the workspace exposes source health, required fields, unsupported states, recent activity, metric definitions, and citation paths.
A human reviewer can verify whether spend, lead, revenue, pipeline, and recommendation claims have enough source support for the next client conversation.
Follow the review pathWhen the evidence holds, the same dashboard context feeds Ask Data, weekly insights, report snapshots, branded exports, and delivery records.
The account team decides what reaches the client, while SIRJ preserves the dashboard snapshot, source rows, and report history behind the final artifact.
Follow the review pathDashboard workflow
The dashboard loads quickly while its credibility comes from the sequence underneath: scope, capability, eligibility, rendering, and downstream answers.
| Step | What happens | User-visible proof |
|---|---|---|
| Scope the workspace | Dashboard generation starts from the active account and client, selected date range, connections, events, matches, and notifications that pass tenant scope checks. | The user sees one client's workspace, not blended records from other accounts or workspaces. |
| Infer available source capability | Connected providers are converted into categories and event types such as spend, lead, deal, payment, communication, form, CRM, ads, and accounting. | The readiness panel and card set explain what the current stack can support before the user reads a metric. |
| Unlock the eligible cards | The dashboard includes only cards whose requirements are met, then marks missing capability requirements for spend, leads, revenue, CRM, and communication evidence. | Users see available metric and table surfaces plus clear next requirements when the stack is partial. |
| Render metrics and activity | Metric cards, table rows, bar visuals, gauges, recent activity, source status, and onboarding steps render from the dashboard config and escaped display values. | The workspace gives the account a visual board while preserving empty states, provider context, and safe output escaping. |
| Feed answers and reports | The same dashboard context feeds Ask Data answers, cited rows, weekly insights, report snapshots, recommendations, and export workflows. | A buyer can move from dashboard to answer to report without losing the source-backed explanation for the number. |
Proof standards
Buyers do not need another glossy chart. They need a workspace that makes missing connectors, hidden scope problems, unsupported cards, and unsafe display values less likely to reach a client review.
Card generation and readiness checks require the relevant event types, provider categories, and attribution-path requirements before a surface appears as proof.
Dashboard readiness and runtime dataset construction assert account and client scope before connections, events, and derived records are used.
Readiness status, missing capabilities, next requirements, empty states, and next-gap guidance keep setup gaps visible to the user.
Dashboard HTML escapes rendered values while preserving tables, activity rows, Ask Data output, onboarding copy, and provider labels for the user.
FAQ
The FAQ is written for search and answer engines, but it also keeps the product promise precise: supported cards, scoped data, and visible setup gaps.
Yes. A partial dashboard can show what the current stack supports, while readiness status and next requirements explain which missing source would unlock better attribution proof.
Cards are hidden when the connected stack cannot support them yet. For example, ROAS needs spend plus revenue, while pipeline views need CRM or booking evidence.
Yes. The dashboard includes Ask Data, but answers stay tied to the active client, date range, available dashboard fields, and supported query types.
Report workflows freeze dashboard context into snapshots, source rows, campaign performance, insights, recommendations, branded exports, and weekly delivery records.
Ready when the numbers need to hold up
Use the live demo to inspect readiness, cards, source health, activity, and Ask Data from the same dashboard context.