Pricing/Implementation timeline

Implementation timeline

Know the path from plan choice to first source-backed report.

See the SIRJ implementation path from plan selection to account setup, first workspace, first source, dashboard readiness, reporting handoff, and expansion support.

Start Growth plan Compare plans

Buyer answers

Answer the after-signup questions before checkout.

A clean implementation path should explain where the buyer lands, what makes the first workspace real, and when rollout support needs to become more formal.

Implementation answer

What happens after a buyer chooses a SIRJ plan?

The selected plan can carry into signup, then the account is created with the first workspace route aimed at billing, integrations, or the dashboard based on the buyer's starting point. The first practical job is to create or confirm the client workspace that will hold source connections and reports.

The buyer does not have to wonder whether Start free trial leads to a contextless form, a blank dashboard, or a private handoff. The first route continues the buying context.

Review related path

Implementation answer

What should the first implementation milestone be?

The first milestone is a real client workspace with at least one source connected, required provider setup visible, and enough synced evidence to make dashboard readiness meaningful. That can be a core ad, call, CRM, job, invoice, or payment source depending on the first reporting proof.

Implementation is not considered real just because a login exists. The workspace needs a source path that can support a dashboard or report.

Review related path

Implementation answer

How does SIRJ show whether the dashboard is ready?

Dashboard readiness depends on workspace scope, connector setup, sync state, source health, and whether the dashboard can show supported metrics from the active client. Missing sources or incomplete setup stay visible instead of being hidden behind empty cards.

A buyer can see whether the dashboard is ready for reporting or still waiting on access, setup, sync, or source evidence.

Review related path

Implementation answer

When does implementation become Scale or Enterprise work?

Scale becomes useful when connector QA, portfolio reviews, lineage exports, templates, or reporting architecture review become recurring needs. Enterprise becomes the right path when SSO, procurement, custom retention, private connectors, or governed rollout must be approved before launch.

The buyer can start with the right public plan and move into deeper support only when the rollout itself requires it.

Review related path

Timeline

From selected plan to first reporting handoff.

The timeline makes the sequence explicit: choose the plan, create the account, scope the workspace, connect a source, confirm dashboard evidence, and move into reporting or rollout support.

Plan intent Account and workspace First source First dashboard evidence Reporting handoff Expansion or governance

Implementation steps

Each step has an owner and visible proof.

The implementation timeline should never depend on vague progress language. Each step names what happens and what the buyer can inspect.

Phase	Owner	What happens	Visible proof
Plan intent	Buyer and SIRJ account flow	The buyer starts from pricing, plan comparison, integrations, onboarding, or a solution page, and the selected plan or source context carries into signup when available.	Signup can show selected plan and source context before account creation, so the first workspace continues the choice the buyer already made.
Account and workspace	SIRJ account owner	The account owner creates the account, confirms business context, enters the protected workspace, and creates or confirms the first client workspace for source setup.	Workspace and client access pages explain account state, visible-client scope, invitations, role boundaries, and where the first useful workspace action appears.
First source	SIRJ user with source access	The team connects the first source and completes provider setup such as resource selection, webhook activation, permission review, or pipeline mapping when the source requires it.	Integration pages and connector health show auth method, imported records, setup requirements, sync cadence, stale data, and missing setup before reporting depends on the source.
First dashboard evidence	SIRJ product state	The first sync has to produce supported dashboard evidence such as spend, leads, calls, forms, jobs, invoices, payments, campaign rows, or recent activity for the active client.	Dashboard readiness, metric definitions, and data validation explain which cards can appear and which unsupported numbers stay out of client-facing reports.
Reporting handoff	Account team	Once the first dashboard has evidence, the account team can move into reports, weekly insights, white-label exports, and the next source needed to strengthen the revenue story.	Reports, sample report, weekly insights, and exports pages show how dashboard evidence becomes client-ready output without losing source context.
Expansion or governance	Buyer and SIRJ support path	The buyer adds Scale support for recurring QA and portfolio review, or moves into Enterprise when security review, procurement, private connectors, or custom retention decide the rollout.	Connector QA, reporting architecture review, custom connectors, and Enterprise rollout pages explain what deeper support covers before the buyer commits to it.

Readiness checks

Know what must be true before reports use the workspace.

First reports become credible when workspace scope, source setup, synced dashboard evidence, and reporting handoff are all visible.

Check	Buyer sees	Review path
Workspace is scoped	The first client workspace is tied to the right account, active client, visible-client scope, invited roles, and reporting destinations.	Client workspace and account setup routes explain how SIRJ separates owner signup, invited user access, role-aware workspace actions, and client-visible reporting.
Source access is usable	Connector auth, required permissions, selected resources, provider-specific setup controls, webhook state, and sync cadence are visible before source data is treated as ready.	Integration setup manifests and connector health rows keep setup requirements visible for OAuth, API keys, account selection, forms, calls, CRM stages, jobs, invoices, and payments.
Dashboard evidence exists	Supported cards appear only when the active client has synced source evidence that can support spend, leads, revenue, ROAS, form, call, job, invoice, payment, or activity metrics.	Dashboard, metric definition, and data validation pages explain card eligibility, unsupported states, stale-source behavior, and metric calculation boundaries.
Report handoff is clear	The team knows how dashboard evidence moves into weekly insight delivery, sample report output, white-label exports, and client-facing proof without manual reconstruction.	Reports, weekly insights, sample report, and exports routes show the output path from dashboard evidence to client-ready artifacts.
Support depth matches the plan	Starter and Growth use the public setup path, Scale adds recurring QA and architecture review, and Enterprise handles governed rollout requirements.	Plan comparison, connector QA, reporting architecture review, and Enterprise pages explain when implementation stays self-serve, guided, operational, or governed.

Plan handoff

Implementation depth should match the plan.

Starter and Growth focus on first-workspace setup. Scale adds recurring operational review. Enterprise handles governed rollout.

Plan	Included path	Expand when
Starter	Guided first-workspace setup for up to 5 client workspaces, core integrations, dashboards, Ask Data, exports, and the public setup guarantee.	Move to Growth when reporting becomes weekly across more clients or the team needs every current SIRJ integration.
Growth	Default agency implementation path with every current integration, priority onboarding, weekly insights, custom metrics, connector health, and up to 20 active workspaces.	Move to Scale when connector readiness reviews, portfolio reporting, templates, or lineage exports become recurring operations.
Scale	Operational implementation support for larger portfolios: connector QA, reporting architecture review, advanced lineage exports, templates, and priority support.	Move to Enterprise when security review, SSO, procurement, custom retention, private connectors, or executive reporting have to be approved before rollout.
Enterprise	Governed rollout path for custom workspace volume, SSO, security review, procurement support, retention terms, private connectors, and executive reporting.	Use Enterprise from the start when governance is part of the buying requirement rather than a later upgrade trigger.

Rollout safeguards

Keep implementation promises tied to what the product can prove.

These safeguards keep setup support, source readiness, permissions, and governance separate enough for the buyer to trust the plan.

Review standardSetup support stays tied to source evidence

A buyer should not be promised a polished report before the first workspace has the source records needed to support it.

The onboarding and setup guarantee pages keep source access, setup requirements, first sync, dashboard readiness, and unsupported outcomes visible.

Review path

Review standardUnsupported sources are not treated as ready

A must-have source may need public integration support, private connector scope, or a different rollout plan before it can support revenue proof.

Integration, connector health, custom connector, and Enterprise routes separate supported connectors from private source planning and provider limitations.

Review path

Review standardPermissions stay role-aware

Client users, viewers, and account owners need different access paths so implementation does not accidentally expose broad agency data.

Account setup, client workspaces, security, and invitation flows keep workspace access scoped to account, client, role, and permitted reporting surfaces.

Review path

Review standardGovernance is handled before rollout when needed

Some teams cannot connect client revenue data until SSO, procurement, retention, security review, or private connector scope is settled.

Enterprise rollout keeps those requirements separate from public-plan checkout so governed buyers can approve the implementation path before launch.

Review path

FAQ

Implementation questions before signup.

How long does SIRJ implementation take?

Timing depends on source access, provider setup, and whether the first source can produce dashboard evidence. Starter and Growth focus on a guided first-workspace path; Scale and Enterprise add deeper review when rollout complexity requires it.

Can setup start before every source is connected?

Yes. The first workspace can begin with the source that supports the first useful proof, while unsupported cards and missing sources remain visible until the required data is connected.

Who owns the first source connection?

The buyer or account team needs provider access and permissions. SIRJ makes the setup requirements, resource selection, and sync state visible so the next action is clear.

When should a buyer use Enterprise instead of a public plan?

Use Enterprise when implementation depends on SSO, procurement, custom retention, private connector work, security review, or executive reporting approval before client revenue data can be connected.

Start with the path visible

Choose the plan, then make the first workspace real.

Start Growth when weekly reporting is already a real workflow, or compare plans when workspace volume, source readiness, and governance still need a decision.

Start Growth plan Compare plans

What happens after a buyer chooses a SIRJ plan?

The buyer does not have to wonder whether Start free trial leads to a contextless form, a blank dashboard, or a private handoff. The first route continues the buying context.

Review related path

What should the first implementation milestone be?

Implementation is not considered real just because a login exists. The workspace needs a source path that can support a dashboard or report.

Review related path

How does SIRJ show whether the dashboard is ready?

A buyer can see whether the dashboard is ready for reporting or still waiting on access, setup, sync, or source evidence.

Review related path

When does implementation become Scale or Enterprise work?

The buyer can start with the right public plan and move into deeper support only when the rollout itself requires it.

Review related path

Phase

Owner

What happens

Visible proof

Plan intent

Buyer and SIRJ account flow

The buyer starts from pricing, plan comparison, integrations, onboarding, or a solution page, and the selected plan or source context carries into signup when available.

Signup can show selected plan and source context before account creation, so the first workspace continues the choice the buyer already made.

Account and workspace

SIRJ account owner

The account owner creates the account, confirms business context, enters the protected workspace, and creates or confirms the first client workspace for source setup.

Workspace and client access pages explain account state, visible-client scope, invitations, role boundaries, and where the first useful workspace action appears.

First source

SIRJ user with source access

The team connects the first source and completes provider setup such as resource selection, webhook activation, permission review, or pipeline mapping when the source requires it.

Integration pages and connector health show auth method, imported records, setup requirements, sync cadence, stale data, and missing setup before reporting depends on the source.

First dashboard evidence

SIRJ product state

The first sync has to produce supported dashboard evidence such as spend, leads, calls, forms, jobs, invoices, payments, campaign rows, or recent activity for the active client.

Dashboard readiness, metric definitions, and data validation explain which cards can appear and which unsupported numbers stay out of client-facing reports.

Reporting handoff

Account team

Once the first dashboard has evidence, the account team can move into reports, weekly insights, white-label exports, and the next source needed to strengthen the revenue story.

Reports, sample report, weekly insights, and exports pages show how dashboard evidence becomes client-ready output without losing source context.

Expansion or governance

Buyer and SIRJ support path

The buyer adds Scale support for recurring QA and portfolio review, or moves into Enterprise when security review, procurement, private connectors, or custom retention decide the rollout.

Connector QA, reporting architecture review, custom connectors, and Enterprise rollout pages explain what deeper support covers before the buyer commits to it.

Check

Buyer sees

Review path

Workspace is scoped

The first client workspace is tied to the right account, active client, visible-client scope, invited roles, and reporting destinations.

Client workspace and account setup routes explain how SIRJ separates owner signup, invited user access, role-aware workspace actions, and client-visible reporting.

Source access is usable

Connector auth, required permissions, selected resources, provider-specific setup controls, webhook state, and sync cadence are visible before source data is treated as ready.

Integration setup manifests and connector health rows keep setup requirements visible for OAuth, API keys, account selection, forms, calls, CRM stages, jobs, invoices, and payments.

Dashboard evidence exists

Supported cards appear only when the active client has synced source evidence that can support spend, leads, revenue, ROAS, form, call, job, invoice, payment, or activity metrics.

Dashboard, metric definition, and data validation pages explain card eligibility, unsupported states, stale-source behavior, and metric calculation boundaries.

Report handoff is clear

The team knows how dashboard evidence moves into weekly insight delivery, sample report output, white-label exports, and client-facing proof without manual reconstruction.

Reports, weekly insights, sample report, and exports routes show the output path from dashboard evidence to client-ready artifacts.

Support depth matches the plan

Starter and Growth use the public setup path, Scale adds recurring QA and architecture review, and Enterprise handles governed rollout requirements.

Plan comparison, connector QA, reporting architecture review, and Enterprise pages explain when implementation stays self-serve, guided, operational, or governed.

Plan

Included path

Expand when

Starter

Guided first-workspace setup for up to 5 client workspaces, core integrations, dashboards, Ask Data, exports, and the public setup guarantee.

Move to Growth when reporting becomes weekly across more clients or the team needs every current SIRJ integration.

Growth

Default agency implementation path with every current integration, priority onboarding, weekly insights, custom metrics, connector health, and up to 20 active workspaces.

Move to Scale when connector readiness reviews, portfolio reporting, templates, or lineage exports become recurring operations.

Scale

Operational implementation support for larger portfolios: connector QA, reporting architecture review, advanced lineage exports, templates, and priority support.

Move to Enterprise when security review, SSO, procurement, custom retention, private connectors, or executive reporting have to be approved before rollout.

Enterprise

Governed rollout path for custom workspace volume, SSO, security review, procurement support, retention terms, private connectors, and executive reporting.

Use Enterprise from the start when governance is part of the buying requirement rather than a later upgrade trigger.

Know the path from plan choice to first source-backed report.

Answer the after-signup questions before checkout.

What happens after a buyer chooses a SIRJ plan?

What should the first implementation milestone be?

How does SIRJ show whether the dashboard is ready?

When does implementation become Scale or Enterprise work?

From selected plan to first reporting handoff.

Each step has an owner and visible proof.

Know what must be true before reports use the workspace.

Implementation depth should match the plan.

Keep implementation promises tied to what the product can prove.

A buyer should not be promised a polished report before the first workspace has the source records needed to support it.

A must-have source may need public integration support, private connector scope, or a different rollout plan before it can support revenue proof.

Client users, viewers, and account owners need different access paths so implementation does not accidentally expose broad agency data.

Some teams cannot connect client revenue data until SSO, procurement, retention, security review, or private connector scope is settled.

Implementation questions before signup.

Choose the plan, then make the first workspace real.

Preparing the source route.

Know the path from plan choice to first source-backed report.

Answer the after-signup questions before checkout.

What happens after a buyer chooses a SIRJ plan?

What should the first implementation milestone be?

How does SIRJ show whether the dashboard is ready?

When does implementation become Scale or Enterprise work?

From selected plan to first reporting handoff.

Each step has an owner and visible proof.

Know what must be true before reports use the workspace.

Implementation depth should match the plan.

Keep implementation promises tied to what the product can prove.

A buyer should not be promised a polished report before the first workspace has the source records needed to support it.

A must-have source may need public integration support, private connector scope, or a different rollout plan before it can support revenue proof.

Client users, viewers, and account owners need different access paths so implementation does not accidentally expose broad agency data.

Some teams cannot connect client revenue data until SSO, procurement, retention, security review, or private connector scope is settled.

Implementation questions before signup.

Choose the plan, then make the first workspace real.