# LoopLedger pilot proposal A client-ready proposal for turning the Referral Network demo into a scoped, rebrandable referral network management software pilot with clear launch owners, commercial terms, acceptance criteria, and follow-on SEO/AEO expansion. Recommended offer: Referral network management software pilot package Investment summary: $18k-$32k setup, $750-$2.5k/month recurring, $750-$2.5k/month hosting, support, report iteration, and workflow tuning. Target launch window: Weeks 8-12; 2 weeks tenant setup, 2 weeks workflow hardening, 2 weeks chapter pilot and report review. ## Executive Narrative A rebrandable referral operating system for member networks that need visible introductions, follow-up accountability, and sponsor-grade attribution. The paid pilot keeps scope tight: prove more visible referrals, clearer sponsor value, and fewer relationship handoffs lost after meetings. while deferring custom integrations, advanced automation, and unsupported workflow expansion until the buyer validates adoption. Buyer outcome: More visible referrals, clearer sponsor value, and fewer relationship handoffs lost after meetings. Proof points: - Active member adoption: 70% of imported pilot members log in or update profile details.. Evidence: Member onboarding table and profile completion status. - Referral hygiene: 80% of open referrals have next action, acknowledgement, or closed outcome.. Evidence: Stale handoff task queue. - Leadership report readiness: One exported referral summary for the next board or sponsor meeting.. Evidence: Implementation export and reporting proof asset. - Recovered warm introductions: Recover 5 to 8 stale introductions per cohort cycle. modeled lift. - Admin reporting time: Compress reporting prep from hours to minutes for one chapter. modeled lift. ## Prospect Fit - Runs a chapter, partner group, association, or referral-heavy revenue community. - Has at least 75 active members or partner accounts. - Currently tracks referrals in spreadsheets, forms, CRM notes, or meeting recaps. - Chapter directors and Association executives can validate the pilot without replacing their core system. ## Scope ### Tenant setup Configure brand tokens, subdomain, member roles, referral stages, and launch assets for the pilot chapter. Deliverables: - White-label chapter workspace - Member roster import and profile readiness - Member roster import template - Member roster import map Acceptance: Referral board, follow-up task, and recognition card update together. ### Data onboarding Map member roster fields, validate required records, flag duplicates, and produce an import exception list. Deliverables: - Roster import and validation - Referral intake, status tracking, and warm-intro owner assignment - Sponsor report sample - Referral history import map Acceptance: Markdown and JSON exports include GTM and launch package fields. ### Workflow configuration Configure stale referral reminders, meeting recognition prep, sponsor report checkpoints, and manual CRM export. Deliverables: - Referral follow-up operations - Follow-up queue for stale handoffs and meeting recognition prep - Chapter launch checklist - Sponsor reporting fields import map Acceptance: Permission matrix ready; needs client sign-off. ### Pilot review Deliver KPI snapshot, report sample, backlog recommendation, and CRM integration decision for the next phase. Deliverables: - Sponsor-ready evidence package - Sponsor and leadership report export with pilot KPI summary - Role and permission matrix Acceptance: Confirm chapter admin, sponsor viewer, and member coordinator access boundaries. ## Timeline - Kickoff (Week 1): Client sponsor. Buyer action: Client sponsor: approves the pilot offer, success criteria, and weekly launch decisions. Deliverable: confirm roster fields, chapter roles, and sponsor-safe reporting rules. Exit: Import template approved and pilot chapter roles assigned. - Configuration (Weeks 2-3): Implementation lead. Buyer action: Chapter admin: provides source data, validates import exceptions, and confirms cutover readiness. Deliverable: import pilot roster and review duplicate/member-category exceptions. Exit: Admin review passes roster, referral, reminder, and report scenarios. - Pilot (Weeks 4-6): Chapter admin. Buyer action: Chapter admin: tests the workflow against real records before broader rollout. Deliverable: configure invite copy, referral statuses, and first activation campaign. Exit: Sponsor report exported with agreed pilot KPI summary. ## Commercial Terms - Recommended tier: Cohort pilot. Buyer can approve one chapter, one admin owner, one sponsor report audience, and a six-week pilot without board procurement. - Pilot setup: $18k-$32k. Brand tokens, chapter subdomain, referral stages, member roles, and launch copy configured for one cohort. - Recurring support: $750-$2.5k/month. Shared launch thread: Business days during pilot; Weekly pilot review: One 45-minute session per week - Roster import and data cleanup: $5k-$8k. Import up to 250 member records, flag duplicate contacts, map sponsor fields, and produce an exception list. - Referral workflow configuration: $5k-$10k. Configure submission, acknowledgement, stale follow-up reminders, meeting recognition, and manual CRM export. - Pilot hosting and support: $750-$2.5k/month. Hosting, workflow tuning, report edits, and weekly pilot review during the paid pilot period. ## Buyer Commitments - Chapter roster export with member categories, sponsor fields, and contact permissions. - Referral stage definitions, stale-follow-up threshold, and meeting-recognition cadence. - Sponsor report recipients, sample report expectations, and approved attribution language. - One chapter admin and one executive sponsor assigned for weekly pilot review. - Two 60-minute kickoff sessions plus one roster import review. before configuration begins. - Shared launch thread with Next business day response during setup. ## Assumptions - Data path: Run a dry import into the tenant preview, reconcile duplicates with the chapter admin, then open logging for one meeting cycle before enabling sponsor reporting. - Identity model: Email magic link for pilot users, with optional Google Workspace SSO after the first chapter launch. - Session model: Tenant-scoped sessions with chapter id, role claim, and sponsor-viewer restrictions enforced server-side. - Domain strategy: Use a client-owned subdomain such as connect.clientdomain.com for production and keep referral-network.ideas-realized.com as the sales preview. - Payment milestone: 50 percent due at signature to reserve implementation slot and start roster mapping. ## Out of Scope - No member billing, event ticketing, or dues management in the first pilot. - No bidirectional CRM sync unless the integration add-on is signed. - Private deal value fields stay hidden from sponsor views unless legal and chapter policy approve the aggregate format. - Do not promise private member-to-member messaging as part of the pilot. - Do not commit to real-time CRM writeback before API review. - Do not expose referral value by member without explicit buyer approval. - Deferred module: Bidirectional CRM sync - Deferred module: Member billing and renewal workflows - Deferred module: AI referral scoring or automated relationship recommendations ## Acceptance Criteria - Roster import completes with fewer than 3 percent blocking exceptions. - Chapter admin logs or updates at least 25 referral records during pilot. - Stale follow-up queue is reviewed weekly and exported in the sponsor report. - Pilot review produces a go, pause, or expand decision for CRM integration. - Submit a referral and move it through acknowledgement: Referral board, follow-up task, and recognition card update together. - Export partner cohort implementation spec: Markdown and JSON exports include GTM and launch package fields. - Hide private value from sponsor viewer role: Permission matrix ready; needs client sign-off. - Roster import completes with fewer than 3 percent blocking exceptions. - Chapter admin logs or updates at least 25 referral records during pilot. ## Risk Controls - Pilot risk control 1: Implementation lead; Do not sell this as a social network, CRM replacement, or member billing platform in the first pilot. - Pilot risk control 2: Product engineer; No member billing, event ticketing, or dues management in the first pilot. - Pilot risk control 3: Growth lead; No bidirectional CRM sync unless the integration add-on is signed. - Referral attribution can become political if sponsor credit is not defined.: Client sponsor; Lock the attribution rule and report wording before the pilot starts. - CRM integration can expand scope before the network proves adoption.: Implementation lead; Ship CSV export first and evaluate CRM sync after the chapter report review. ## SEO/AEO Expansion - Referral management software for business networks: /industries/referral-management-software-for-business-networks - What software helps a professional group track member referrals? (FAQPage) - How do referral groups prove follow-up happened? (HowTo) - Referral network software vs spreadsheet referral logs - Referral network software vs generic CRM ## Next Steps - Approve Cohort pilot and confirm $18k-$32k setup band. - Send required assets: Member roster export, Sponsor reporting rules, Activation message. - Schedule Two 60-minute kickoff sessions plus one roster import review.. - Choose launch domain: referral-network.ideas-realized.com preview now, then referral-network.ideas-realized.com for production. - Use Submit a referral and move it through acknowledgement as the first go/no-go decision. ## Signature Blocks - Client sponsor: Approves budget, pilot scope, and launch decision. - Buyer operations owner: Provides source data, validates workflow language, and accepts launch criteria. - Ideas Realized implementation lead: Owns configuration, runbook, QA evidence, and post-pilot backlog recommendation.