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/Setup guarantee
See what SIRJ means by the 30-day onboarding guarantee: guided first-workspace setup, source readiness, dashboard handoff, support boundaries, and what the guarantee does not promise.
Buyer answers
Buyers need to know what setup help includes, how progress is shown, which plans carry the offer, and which outcomes still depend on source data.
It covers the guided path to a usable first workspace: account creation, first client workspace, first source connection, provider setup requirements, first sync, dashboard readiness, and the reporting handoff that explains what is ready or still missing.
The buyer is not left alone with a blank dashboard. SIRJ has to keep the next setup action visible until the first workspace can show source-backed evidence.
Inspect the proof pathNo. The guarantee is a setup and clarity promise. It does not promise advertising performance, revenue lift, provider uptime, source completeness, client retention, or that every requested metric will be supported by the connected records.
The offer lowers setup risk without weakening the credibility of SIRJ's revenue claims. Proof still depends on connected source data.
Inspect the proof pathThe onboarding path shows whether the active client workspace exists, whether an integration is connected, whether provider setup is complete, whether a first sync has produced dashboard evidence, and which action is allowed next.
Progress is visible as workspace state, source readiness, setup requirements, and dashboard proof instead of a vague promise from support.
Inspect the proof pathStarter and Growth include the public 30-day onboarding guarantee. Scale and Enterprise use deeper support paths, including connector QA, architecture review, implementation planning, procurement support, or private connector scope when those needs are real.
The guarantee gives smaller teams enough confidence to start, while bigger teams still have a clear route to operational support without flattening every plan into the same offer.
Inspect the proof pathIncluded and excluded
Each setup stage explains what SIRJ helps move forward and what needs a different plan, provider permission, source record, or written agreement.
| Stage | Included | Outside the offer |
|---|---|---|
| Account and workspace | Account creation, selected-plan context, first client workspace, role-aware access, and a route back to the protected dashboard. | Changing ownership structure, SSO, custom retention, procurement terms, or multi-account migration outside the selected plan. |
| First source | Guidance for choosing the first integration, completing provider setup, seeing required resource selection, and understanding the first sync state. | Provider API outages, missing provider permissions, unavailable source records, or private connector commitments not scoped through Enterprise. |
| Dashboard readiness | Visibility into dashboard cards, empty states, missing source requirements, recent activity, source health, and first evidence needed for reporting. | A promise that every dashboard card will unlock from one source or that unsupported metrics will be shown as if they were complete. |
| Reporting handoff | A route from first dashboard evidence into report previews, weekly insight behavior, white-label output, and unsupported-state language. | Custom report design, client-specific consulting, guaranteed client acceptance, or custom destination work outside the plan or agreement. |
Setup path
The guarantee should move the buyer through account context, client workspace, first source, first dashboard evidence, and reporting rhythm without implying every possible source or result is available.
Workflow
| Step | What happens | User-visible proof |
|---|---|---|
| Preserve the buyer's starting point | Signup should remember whether the buyer came from pricing, an integration page, onboarding, or the default Growth path, then carry that context into the first workspace action. | Account setup explains selected plan and source intent before the buyer creates an account. |
| Create the first workspace | The first onboarding job is to create or confirm the active client workspace so source connections, dashboard state, reports, and weekly delivery stay scoped correctly. | Client workspaces explain visible-client scope, role boundaries, invitations, weekly recipients, and account-level ownership. |
| Connect and configure the first source | The guarantee path keeps the provider setup job visible: authentication, resource selection, webhook readiness, mapping requirements, or missing setup state. | Integration detail pages and connector health surfaces show setup requirements, imported records, sample rows, and stale-source behavior. |
| Confirm first dashboard evidence | Setup is not treated as complete just because a connector exists. The first workspace needs dashboard evidence such as spend, leads, calls, forms, jobs, invoices, payments, or recent activity. | Dashboard readiness and metric definition pages show which cards are supported and which numbers remain unsupported. |
| Move into reporting rhythm | Once the first workspace has evidence, the buyer can move into reports, weekly insight delivery, white-label exports, and the next source needed to make the revenue story stronger. | Reports, weekly insights, sample report, and exports pages explain the handoff from source-backed dashboard evidence to client-ready output. |
Offer boundaries
A strong setup offer does not require loose claims. These boundaries keep setup support, provider behavior, source evidence, and custom implementation separate.
The setup guarantee should not be confused with a promise that ad spend will improve, revenue will increase, or clients will retain after a report is delivered.
Disclosures and terms keep business outcomes separate from source-backed reporting setup, so buyers can evaluate the setup offer without mistaking it for a financial performance claim.
Review the boundarySome setup delays come from provider permissions, source APIs, missing records, resource access, or credentials that SIRJ cannot control directly.
Connector health and setup manifests show provider setup, stale-source, unauthorized, or missing-resource states rather than hiding them.
Review the boundaryA buyer may want a metric that the connected records cannot support yet; the guarantee should not turn that request into a fabricated chart.
Metric definitions, data validation, and Ask Data pages explain unsupported states and citation requirements.
Review the boundaryPrivate connectors, custom destinations, SSO, procurement review, and custom retention can change rollout scope and should not be buried inside a public self-serve setup promise.
Enterprise and custom connector pages route those requirements into scoped planning before production reporting depends on them.
Review the boundaryProof standards
Onboarding states carry the next allowed action and blocked reason so the buyer can see what is required before reporting output can be trusted.
Connector health and data validation keep missing setup and unsupported source states visible before reports or Ask Data answers use the evidence.
The setup guarantee page links to disclosures and terms, and names the outcomes that depend on source data, provider access, or a scoped agreement.
Pricing keeps the public guarantee on Starter and Growth, then routes Scale and Enterprise needs to QA, architecture review, implementation planning, or governed rollout.
FAQ
It is a setup clarity promise, not a blanket refund statement. Billing, cancellation, written offer terms, and plan-specific agreements are handled through the billing and disclosures paths shown during purchase.
No. Private connector work belongs in Enterprise planning because source purpose, authentication, available records, validation gates, support ownership, and rollout timing must be scoped before production reporting depends on it.
SIRJ shows that limitation clearly and routes the buyer to the next source, metric definition, data validation state, or unsupported-answer path instead of presenting an incomplete number as complete.
A guarantee claim is only useful when buyers can inspect the boundary. The page makes the setup promise, support path, and excluded outcomes visible before signup.
Ready when the numbers need to hold up
Choose Growth with a guided first-workspace path, or review onboarding to see how SIRJ moves from account setup to source-backed dashboard evidence.