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.
Pricing/Reporting architecture review
See what SIRJ Scale reviews across client workspaces, source coverage, connector health, dashboard templates, report outputs, lineage exports, and weekly delivery.
Buyer answers
Growing agencies need to know what the review covers, why it belongs in Scale, and where data boundaries still apply.
It reviews the client workspace portfolio, connected sources, connector health, dashboard template coverage, report outputs, weekly delivery path, and lineage export needs behind the current reporting motion.
Scale buyers can see whether the reporting system is repeatable across clients instead of relying on a fresh manual fix for every review cycle.
Follow the review pathScale is for agencies where the reporting problem has become portfolio infrastructure: more client workspaces, more source combinations, more template reuse, and more pressure to keep evidence consistent across recurring reviews.
The review makes the plan difference concrete. Scale is not just a larger workspace limit; it adds a recurring check on the operating system behind client reporting.
Follow the review pathNo. The review does not alter source records or loosen validation. It checks whether the current setup, templates, reports, and exports can use supported data clearly, and it names the gaps that need another source, plan path, or implementation step.
The buyer gets operating clarity without weakening the evidence standard behind revenue claims.
Follow the review pathThe review keeps source health, dashboard templates, report sections, weekly delivery, white-label output, and lineage exports aligned so a client can ask where a number came from and receive the same answer across every surface.
The agency has a cleaner path from dashboard evidence to client-ready proof, which makes recurring reporting easier to defend.
Follow the review pathReview surfaces
The review is useful because it follows the same surfaces a client reporting workflow depends on every week.
| Surface | Buyer sees | Review path |
|---|---|---|
| Client workspace portfolio | Whether workspace volume, visible-client rollups, access, branding, and weekly recipients can be managed consistently across the client base. | Review client workspace structure, roles, invitations, brand settings, recipient configuration, and account-level ownership before reporting gets copied one client at a time. |
| Source coverage and connector readiness | Which sources are connected, which records each source can support, which connectors need setup, and which data paths are stale or incomplete. | Compare the current source stack against the required reporting claims, then check connector health, setup requirements, sync cadence, and validation states. |
| Dashboard templates and card support | Which starting boards fit the agency's client mix, which cards have enough evidence, and which template gaps require another source or clearer metric boundary. | Match workspace needs to templates, card unlock rules, metric definitions, source requirements, and the live dashboard states each client should see. |
| Reports, weekly delivery, and exports | Whether recurring reports, weekly insights, white-label output, PDF exports, and report history carry the same source-backed explanation. | Check report snapshots, weekly recipient behavior, export status, attention items, recommendations, and client-ready proof sections for consistency. |
| Lineage exports and validation boundaries | Which claims can be supported by source records, which validation states are blocking confidence, and which evidence may need an export for review. | Review data lineage, validation gates, export paths, missing-data language, and disclosure boundaries before unsupported claims reach a client review. |
Review path
The Scale review moves through client portfolio shape, source coverage, template fit, report output, and the boundary between Scale support and Enterprise rollout.
Workflow
| Step | What happens | User-visible proof |
|---|---|---|
| Map the current reporting motion | Start with how the agency reviews performance today: client workspace count, report cadence, source stack, weekly recipient list, template reuse, review meetings, and recurring questions from clients. | The review starts from the actual client reporting motion instead of a static checklist, so the recommended plan path matches how the agency operates. |
| Review source coverage and health | The review checks whether each reporting claim has the required ad, call, form, CRM, job, invoice, payment, or private-source evidence, then names connectors that are missing setup, stale, or unsupported. | Connector health and integration pages show setup state, imported records, sync behavior, and source readiness before reports depend on the data. |
| Align templates to plan needs | The review compares the agency's recurring boards against available dashboard templates, metric definitions, source requirements, and cards that should stay hidden until enough evidence exists. | Dashboard template pages explain starting boards, required sources, card eligibility, and the reporting surfaces each template can support. |
| Check report and export evidence | The review follows dashboard evidence into report snapshots, weekly insights, branded exports, attention items, recommendations, delivery status, and export history so each output can defend the same claims. | Reports, weekly insights, sample report, white-label reporting, and export pages show the client-facing output and the proof path behind it. |
| Decide what belongs in Scale or Enterprise | The review separates Scale operating needs from Enterprise needs such as SSO, custom retention, procurement review, private connector planning, executive rollout, or custom destination scope. | Pricing, Enterprise, custom connector, billing, and disclosure pages keep workspace limits, support paths, and governed rollout requirements visible before the buyer commits. |
Operating drift
Scale should help a growing agency keep reports consistent as clients, sources, templates, and weekly review needs multiply.
A client portfolio gets harder to manage when every workspace has a different setup, reporting rhythm, brand treatment, and recipient path.
The review checks workspace structure, access, branding, recipients, and dashboard reuse so reporting can scale without rebuilding the same foundation repeatedly.
Inspect the related surfaceA client review becomes fragile when the report depends on a source that is stale, unauthorized, missing setup, or unable to support the requested metric.
Connector health and validation checks keep stale data, setup gaps, and unsupported metrics visible before reports or answers use them.
Inspect the related surfaceAgencies lose reporting leverage when every client board becomes a custom layout that cannot be reused, compared, or explained consistently.
The review aligns recurring client needs to template families, metric definitions, source requirements, and reusable reporting surfaces.
Inspect the related surfaceDashboards, PDFs, weekly emails, and white-label reports can create competing versions of the truth when they stop sharing the same source context.
The review traces output from dashboard snapshot to reports, weekly insights, exports, and lineage evidence so each surface explains the same supported facts.
Inspect the related surfaceProof standards
The review starts from client workspace structure, role-aware access, invitations, ownership, and the agency overview before inspecting report output.
Connector health, setup requirements, sync cadence, imported records, and validation states are reviewed before a source is treated as ready for reporting.
The review ties templates to card unlock rules, metric definitions, required sources, missing-data language, and reporting handoff.
The review follows report snapshots, attention items, recommendations, delivery records, export states, and lineage paths before the workflow is treated as portfolio-ready.
FAQ
Yes. Scale includes a quarterly review focused on client workspace volume, source readiness, dashboard templates, reporting output, lineage exports, and the recurring workflow behind portfolio reporting.
No. The review is an operating check on the reporting system already supported by the plan. Custom connectors, custom retention, SSO, procurement terms, or custom destinations belong in Enterprise planning.
It can identify when a private source is blocking the reporting motion, but scoping authentication, records, support ownership, validation gates, and rollout for a private connector belongs in Enterprise.
No. It improves reporting clarity and repeatability, but client retention, ad performance, provider behavior, source completeness, and business outcomes remain outside the guarantee.
Ready when the numbers need to hold up
Talk through workspace volume, source coverage, template fit, report output, weekly delivery, lineage exports, and whether Enterprise rollout is already the cleaner path.