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.
Integrations/CRM and pipeline integrations
Lead, opportunity, stage, owner, and follow-up data.
Data signals
Category pages make the library scannable by the job each connector performs, then point buyers to the exact connector pages for field-level proof.
Dashboard proof
This output only earns trust when the underlying connector records can be traced through normalized events, dashboard cards, and cited answers.
This output only earns trust when the underlying connector records can be traced through normalized events, dashboard cards, and cited answers.
This output only earns trust when the underlying connector records can be traced through normalized events, dashboard cards, and cited answers.
| Connector | Fields SIRJ uses | Dashboard output | Buyer question |
|---|---|---|---|
| Close CRM | Lead ID, Submitted at, Contact source | Lead stage velocity | How does lead records affect booked revenue? |
| Follow Up Boss | Lead ID, Submitted at, Contact source | Lead stage velocity | How does lead records affect booked revenue? |
| GoHighLevel | Contacts, Opportunities, Pipelines | Pipeline value by stage | Which leads have not been contacted? |
| HubSpot | Lead ID, Submitted at, Contact source | Lead stage velocity | How does lead records affect booked revenue? |
Connectors
Each connector page shows imported fields, dashboard examples, buyer questions, sample rows, and source-field lineage for that source.
Lead stage velocity
MVP ready · HourlyFollow Up BossLaunch trackLead stage velocity
Launch track · Hourly
Launch trackPipeline value by stage
Launch track · HourlyHubSpotLaunch trackLead stage velocity
Launch track · HourlyPipedriveRoadmapLead stage velocity
Roadmap · HourlyValidation workflow
| Step | What has to be true |
|---|---|
| 1 | Import lead, contact, opportunity, stage, and activity records from the CRM. |
| 2 | Normalize CRM activity into lead, deal, and communication events with tenant scope intact. |
| 3 | Match pipeline records back to the ad, call, form, or referral source that created demand. |
| 4 | Show uncontacted leads, stage leakage, pipeline value, and won revenue by source. |
Lineage route
Related categories
Connect paid search, paid social, Local Services, and other ad sources so campaign spend can be matched to calls, booked work, invoices, and collected revenue.
Call trackingBring call source, answered status, tracking number, duration, and recording context into the attribution path so phone leads are not treated as anonymous conversions.
FormsBring submissions, questions, answers, hidden source fields, and form metadata into the same path as CRM, calls, jobs, invoices, and payments.
Category-first integration planning
A connector is only persuasive when the buyer can see the downstream proof it unlocks. Use the category route to plan the stack before opening the first client workspace.