# LoopLedger procurement and security packet A buyer-facing approval packet for turning Referral Network into a paid pilot: commercial scope, data boundaries, access model, hosting plan, support coverage, automation limits, and sign-off evidence. Canonical product page: https://ideas-realized.com/demo-library/referral-network Live app: https://referral-network.ideas-realized.com Decision window: Weeks 8-12 Approval owner: Client sponsor Commercial snapshot: Referral network management software pilot package: $18k-$32k setup and $750-$2.5k/month recurring. Buyer can approve one chapter, one admin owner, one sponsor report audience, and a six-week pilot without board procurement. ## Approval Sections ### 1. Commercial approval Owner: Sales lead Status: ready Packages the referral network demo into a signed pilot order: one branded workspace, roster import, referral workflow configuration, weekly support, and a sponsor evidence package. It keeps CRM sync, billing, and multi-chapter rollout out of the first deal unless separately approved. - Recommended tier: Cohort pilot - Payment milestones: 50 percent due at signature to reserve implementation slot and start roster mapping. 30 percent due after branded workspace, referral stages, and admin review are accepted. 20 percent due after sponsor-ready pilot report and expansion recommendation are delivered. - Gross margin model: Target 60-70 percent implementation margin after roster cleanup, launch support, hosting, and weekly report tuning. ### 2. Data handling and import Owner: Implementation lead Status: needs-client The first live pilot can start from CSV exports instead of a direct CRM integration. The import map focuses on member identity, referral status, relationship attribution, and recognition reporting. - Cutover: 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. - Privacy note: Referral notes should exclude sensitive deal details unless the network has explicit member consent and a data-retention policy. - Sources in scope: Member roster (80 to 250 member records); Referral history (50 to 500 referral records); Sponsor reporting fields (10 to 30 sponsor-visible metrics) ### 3. Access and role boundaries Owner: Security reviewer Status: scoped The referral network pilot needs role boundaries around referral value, private notes, roster imports, and sponsor-facing reports before a chapter can invite real members. - Identity provider: 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. - Permission scopes: Referral lifecycle; Roster import; Sponsor reporting ### 4. Hosting and domain launch Owner: Deployment owner Status: scoped A production handoff plan for taking Referral Network from sales preview to a client-owned launch domain with Netlify hosting, environment gates, monitoring, rollback, and canonical SEO/AEO checks. - Hosting model: Single Next.js application deployed from GitHub to Netlify, with demo subdomains rewritten into app-only routes and canonical SEO pages kept on ideas-realized.com. - Preview domain: referral-network.ideas-realized.com - Production domain: referral-network.ideas-realized.com ### 5. Support and SLA coverage Owner: Shared launch thread Status: ready A buyer-ready support model for launching Referral Network with triaged tickets, service levels, training artifacts, success milestones, and renewal proof tied to the first pilot cohort. - Launch channel: Shared launch thread: Business days during pilot - Renewal signal: Demo to discovery: 6 qualified discovery requests per quarter - Service levels: Shared launch thread Next business day; Weekly pilot review Scheduled ### 6. Automation and notification guardrails Owner: Product lead Status: scoped The live pilot should reduce manual chapter admin work by turning referral status changes into reminders, recognition prompts, and reporting tasks. - Rules: Stale introduction reminder (template); Meeting recognition queue (ready); Sponsor report checkpoint (optional) - Escalations: Unacknowledged referral: No acknowledgement after four business days.; Private note risk: Sponsor-visible report includes private referral notes. ### 7. Billing and renewal readiness Owner: Client sponsor Status: ready Commercial controls for selling Referral Network: invoice milestones, pilot entitlements, seat packaging, renewal checkpoints, legal readiness, and upgrade triggers tied to the rebrand-ready pilot offer. - Billing model: Cohort pilot: Target 60-70 percent implementation margin after roster cleanup, launch support, hosting, and weekly report tuning. - Pilot price: $18k-$32k - Recurring price: $750-$2.5k/month ### 8. Statement of work and signature packet Owner: Client sponsor Status: ready The SOW package turns the proposal and deal desk into signable scope, milestones, service levels, exclusions, and signature blocks for Northstar Referral Guild. - Statement of work: /demo-library/referral-network/statement-of-work - SOW JSON: /demo-library/referral-network/statement-of-work.json - Client proposal: /demo-library/referral-network/client-proposal ## Redlines and Change Controls - 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. - Additional chapters, billing, or member renewal workflows: Scope as a separate expansion package after the first sponsor review. - Bidirectional CRM sync or automatic activity creation: Requires API review, field map approval, and integration estimate. ## Approval Checklist - Pilot order accepted: Signed order form, chapter owner, sponsor report audience, and six-week pilot window confirmed. - Roster import approved: Member records loaded with fewer than 3 percent blocking exceptions and sponsor fields validated. - Sponsor evidence accepted: Pilot KPI report reviewed and expansion decision captured as go, pause, or revise. - 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. - Canonical and noindex routing verified: Main-domain landing pages remain canonical while app-only routes are used for subdomain launch URLs. - Client proposal and implementation spec approved: LoopLedger pilot proposal and JSON/Markdown implementation spec are reviewed before production domain cutover. - 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.