# LoopLedger search-to-pilot attribution map Connect referral management software for business networks traffic to live app proof, buyer evidence, pilot package interest, and launch details so the demo can be sold and improved from real intent data. North star metric: Accepted referrals with owner follow-up within 5 business days Instrumentation phase: Instrument landing CTA, demo launch, referral create, status change, follow-up reminder, sponsor export, and implementation-spec download before the first pilot. Canonical page: https://ideas-realized.com/demo-library/referral-network Live app: https://referral-network.ideas-realized.com ## Attribution Stages ### 1. Industry search entry Route: https://ideas-realized.com/industries/referral-management-software-for-business-networks Event: industry_page_viewed_referral_network Trigger: referral management software for business networks visitor lands on the indexable industry page. Owner: Growth lead Destination: Search console, analytics landing report, and CRM first-touch source Success signal: 6 qualified discovery requests per quarter Proof asset: Referral networks use software like this to centralize member directories, log warm introductions, attribute revenue, and keep thank-you follow-up visible to chapter leaders. Next action: Route engaged visitors into LoopLedger instead of a generic contact form. ### 2. Live app launch Route: https://referral-network.ideas-realized.com Event: demo_opened_referral_network Trigger: Buyer opens the referral network app preview from a landing or industry page. Owner: Growth lead Destination: Analytics event stream and CRM source field Success signal: Demo open rate by traffic source reaches 8 percent from the referral software cluster. Proof asset: 16/16 clickable flows in the demo app. Next action: Tag the session with demo slug, source page, buyer role, and selected workflow. ### 3. Workflow proof interaction Route: https://ideas-realized.com/demo-apps/referral-network Event: referral_status_advanced Trigger: User advances a referral from New to Accepted, Closed won, or Thanked. Owner: Product lead Destination: Product analytics funnel Success signal: At least 70 percent of sample referrals move beyond New during a sales demo. Proof asset: Logged-in member directory with category search and chapter context.; Referral capture flow with source, recipient, client, status, and value.; Follow-up task queue for stale handoffs, meeting-recognition prep, and CRM export readiness. Next action: Use the touched workflow as the first follow-up proof point. ### 4. Proof and ROI review Route: https://ideas-realized.com/roi-calculators/referral-network-roi-calculator Event: sponsor_report_exported Trigger: Leadership report or sponsor activity packet is downloaded. Owner: Client sponsor Destination: Audit ledger and sales proof dashboard Success signal: Sponsor-safe reporting is used in 3 of 5 qualified sales calls. Proof asset: /case-studies/referral-network-pilot-case-study plus ROI calculator and production evidence export. Next action: Attach ROI, case-study, and proof-pack links to the buyer follow-up. ### 5. Pilot package qualification Route: https://ideas-realized.com/pilot-packages/referral-network-pilot-package Event: pilot_package_viewed_referral_network Trigger: Buyer opens Referral network management software pilot package after live app or ROI review. Owner: Sales lead Destination: CRM opportunity score and deal desk queue Success signal: Buyer can approve one chapter, one admin owner, one sponsor report audience, and a six-week pilot without board procurement. Proof asset: $18k-$32k setup, $750-$2.5k/month recurring, 2 weeks tenant setup, 2 weeks workflow hardening, 2 weeks chapter pilot and report review.. Next action: Confirm One chapter admin, one sponsor/reporting owner, roster export access, and weekly launch review for the first 30 days. ### 6. Launch details handoff Route: https://ideas-realized.com/implementation-intake/referral-network-implementation-intake Event: implementation_spec_downloaded Trigger: Prospect exports the JSON or Markdown implementation spec. Owner: Sales lead Destination: CRM intent score Success signal: Spec download creates a follow-up task within one business day. Proof asset: The current demo already covers directory, logging, attribution, follow-up tasks, member onboarding, sponsor reports, sponsor fulfillment, billing renewals, leaderboard, thank-you workflows, and a manual CRM/sponsor/billing/chapter export package. A sellable pilot would need authentication, role permissions, real import/export jobs, notification delivery, and CRM/accounting integrations. Next action: Collect required assets, source-data owner, approval gates, and production-domain decision. ## CRM Fields - source_route - demo_slug - buyer_role - workflow_touched - proof_asset_opened - pilot_package_viewed - implementation_intake_started - next_sales_action ## Dashboards - Referral launch dashboard (Ideas Realized sales and product) - Demo opens by source - Spec downloads - Accepted referral actions - Sponsor report exports - Chapter operator dashboard (Chapter admin and sponsor lead) - New referrals - Stale follow-ups - Closed won value - Sponsor-safe activity report ## Privacy Guardrails - Private referral value: Deal value and private notes are excluded from sponsor analytics unless the buyer explicitly approves aggregate reporting. - Member contact data: Roster import analytics count exceptions and completion only; raw email and phone data are never sent to marketing analytics. - Demo-only signal: Seeded demo interactions are flagged separately from live tenant analytics before launch.