# LoopLedger production evidence pack

Production evidence pack for LoopLedger

A buyer-facing evidence model that ties Referral Network demo interactions to pilot KPIs, acceptance checks, import gates, audit artifacts, and SEO/AEO proof points.

## Operator Promise

The app should prove real referral network operations work through visible records, clear owners, traceable status changes, and exportable evidence before any deeper integration is promised.

Buyer proof point: Tracked introductions: 2 to 3 logged introductions per active member per month during the pilot.

## Evidence Snapshot

- Buyer outcome: More visible referrals, clearer sponsor value, and fewer relationship handoffs lost after meetings.. The pilot model focuses on logged introductions, acknowledgement speed, stale follow-up recovery, and sponsor-ready reporting across one chapter or partner cohort.
- North star: Accepted referrals with owner follow-up within 5 business days. Instrument landing CTA, demo launch, referral create, status change, follow-up reminder, sponsor export, and implementation-spec download before the first pilot.
- Pilot KPI: Active member adoption. 70% of imported pilot members log in or update profile details. Owner: Chapter admin
- Audit source: Referral status change log. Every referral status change, member-import exception, report export, and reminder action has an owner, timestamp, source, and evidence note.

## Acceptance Evidence

- Submit a referral and move it through acknowledgement (Complete): Chapter admin; Launch readiness acceptance test. Referral board, follow-up task, and recognition card update together.
- Export partner cohort implementation spec (Complete): Sales lead; Launch readiness acceptance test. Markdown and JSON exports include GTM and launch package fields.
- Hide private value from sponsor viewer role (Queued): Client sponsor; Launch readiness acceptance test. Permission matrix ready; needs client sign-off.
- Referral attribution (In progress): Chapter admin; Keep every warm intro, follow-up, and sponsor report action traceable.. Status changes and sponsor credit stay visible before report export.
- Roster import exceptions (In progress): Implementation lead; Keep every warm intro, follow-up, and sponsor report action traceable.. Duplicate members and missing categories are held out of the live member list.
- Roster duplicate review (Blocked): Chapter admin; Import the member roster, referral log, and sponsor report fields for one chapter first.. Duplicate emails or member names prevent referral attribution.

## Proof Artifacts

- Before/after referral value report (Template): Dashboard view; owner Chapter admin. Template compares spreadsheet-only activity to tracked member introductions, acknowledgements, and won outcomes.
- Sponsor meeting proof deck (Template): CSV export; owner Referral chair. Uses logged referrals, recognition moments, and outcome totals as the sponsor retention story.
- CRM export sample (Optional): Review packet; owner Executive director. Optional handoff for accepted or won referrals once HubSpot, Salesforce, or CSV fields are confirmed.
- Referral status change log (Ready): Audit log; owner Chapter admin. Acknowledgement captured before weekly sponsor snapshot.
- Roster import exception report (Template): Export; owner Implementation lead. Reminder queued because status stayed New for 5 business days.
- Sponsor report download record (Template): Export; owner Client sponsor. 2 duplicate member records held for admin merge decision.
- Member roster import (Ready): referral-network-member-roster.csv; owner Chapter admin. Seeds the member directory, category filters, chapter assignment, and sponsor-safe profile fields.
- Referral activity import (Ready): referral-network-referral-log.csv; owner Chapter coordinator. Backfills referral records, status history, attributed value, and follow-up owners.

## Live Demo Scenarios

- Member directory: Find a partner: Network admin responds to "Filter the directory by member, company, category, or chapter group before starting an introduction." and proves Turns informal word-of-mouth activity into searchable, accountable referral records.
- Matchmaker: Clean roster for export: Chapter leader responds to "Resolve duplicate, category, and consent issues before staging member records for CRM and sponsor reporting." and proves Shows how partner networks can attribute revenue without requiring a full CRM build.
- Referral logging: Match a request: Member responds to "Review a buyer or sponsor request, compare recommended members, and create a tracked warm introduction." and proves Event activation desk connects meeting attendance, sponsor proof, referral capture, and recap publishing.
- Event activation: Log a referral: Network admin responds to "Create a referral record with source, recipient, client name, estimated value, and first status." and proves Adds referral follow-up tasks so chapter leaders can manage stale handoffs and meeting recognition.

## Buyer Handoff Questions

- What baseline can the buyer confirm for tracked introductions, and what evidence will prove the target?
- Who owns the Member roster export from Chapter spreadsheet or association CRM export, and how often can it be refreshed during pilot?
- Who owns the Referral history export from Spreadsheet, form export, or CRM activity report, and how often can it be refreshed during pilot?
- Should Stale introduction reminder run automatically at launch, or stay as a review queue until the buyer approves notifications?
- Which Chapter directors signs off that the demo scenario is realistic enough for the first live pilot?

## SEO/AEO Proof Points

- referral management software for business networks: 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.
- What software helps a professional group track member referrals? Proof source: Referral status change log and sponsor report download record
- How do referral groups prove follow-up happened? Proof source: Stale follow-up reminder queue
- Active member adoption: 70% of imported pilot members log in or update profile details.
- Referral hygiene: 80% of open referrals have next action, acknowledgement, or closed outcome.
- Operational proof artifact: Referral status change log
- Operational proof artifact: Roster import exception report

## Launch Routing

- Canonical demo page: /demo-library/referral-network
- App-only subdomain: https://referral-network.ideas-realized.com
- Implementation JSON: /demo-library/referral-network/implementation.json
- SEO/AEO primary intent: referral management software for business networks