# LoopLedger tenant cutover plan A buyer-and-implementation cutover packet for moving Referral Network from polished demo to branded live tenant: commercial approval, domain, data dry-run, access, automation, release gates, rollback, support, and SEO/AEO publication. Product: LoopLedger Tenant: Northstar Referral Guild Preview URL: https://referral-network.ideas-realized.com?screen=matcher Preview screen: Matchmaker (matcher) - relationship matching and referral capture Production domain: referral-network.ideas-realized.com Launch window: Medium Cutover score: 75/100 Cutover decision: Ready for buyer input on tenant brand and production domain. Next cutover move: Client confirms launch name, brand tokens, CNAME/TXT ownership, and fallback preview URL https://referral-network.ideas-realized.com. Primary owner: Shared launch thread JSON manifest: /demo-library/referral-network/tenant-cutover-plan.json ## Cutover Phases ### 1. Commercial signoff Owner: Client sponsor Timing: Before kickoff Status: Implementation Confirm the buyer wants this demo rebranded as a paid tenant and accepts the commercial boundaries. Entry criteria: - Buyer has reviewed the live app proof route. - Recommended offer, setup range, and recurring range are understood. Exit criteria: - Order packet approved. - SOW and rebrand rights accepted. - Implementation kickoff can be scheduled. Assets: - Client launch plan: /demo-library/referral-network/client-launch-plan - Buyer-facing launch plan with order, data, SEO/AEO, and support steps. - Statement of work: /demo-library/referral-network/statement-of-work - Buyer-signable scope, milestones, responsibilities, service levels, and change controls. - Statement of work JSON: /demo-library/referral-network/statement-of-work.json - Machine-readable scope and acceptance manifest. - Deal desk package: /demo-library/referral-network/deal-desk - Order form, pricing bands, approval gates, add-ons, and redlines. - Deal desk JSON: /demo-library/referral-network/deal-desk.json - Machine-readable commercial close manifest. ### 2. Tenant identity and domain Owner: Implementation lead Timing: Kickoff day 1 Status: Buyer input Swap the demo identity into the buyer tenant, confirm DNS, and preserve the preview fallback. Entry criteria: - Client name, logo, colors, and launch domain are available. Exit criteria: - Production domain is confirmed. - Tenant seed package references the buyer identity. Assets: - White-label kit: /demo-library/referral-network/white-label-kit - Naming, domain, terminology swaps, copy blocks, brand assets, and checklist. - White-label kit JSON: /demo-library/referral-network/white-label-kit.json - Machine-readable rebrand manifest. - Tenant clone package: /demo-library/referral-network/tenant-clone-package - Rebrand-and-launch handoff for a buyer tenant. - Tenant clone JSON: /demo-library/referral-network/tenant-clone-package.json - Machine-readable tenant clone package. - Tenant seed package: /demo-library/referral-network/tenant-seed-package - Users, roles, data sources, integrations, feature flags, automations, and notifications. - Tenant seed JSON: /demo-library/referral-network/tenant-seed-package.json - Machine-readable tenant seed manifest. ### 3. Data dry-run and tenant seed Owner: Chapter admin Timing: Kickoff days 1-2 Status: Implementation 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. Entry criteria: - Source exports and sample CSV templates are available. Exit criteria: - Dry-run import passes validation. - Required source fields and tenant boundaries are accepted. Assets: - Sample data package: /demo-library/referral-network/sample-data-package - CSV templates, sample rows, and import validation gates. - Sample data JSON: /demo-library/referral-network/sample-data-package.json - Machine-readable data dry-run manifest. - Production data contract: /demo-library/referral-network/data-contract - Entities, source systems, events, boundaries, and API-shaped routes. - Production data contract JSON: /demo-library/referral-network/data-contract.json - Machine-readable production data contract. ### 4. Access, roles, and automations Owner: Product lead Timing: Kickoff days 2-4 Status: Buyer input Confirm buyer seats, permissions, integration credentials, notification owners, and disabled-by-default automation rules. Entry criteria: - Named users and roles are available. - Required credentials and sender identities have owners. Exit criteria: - Access checks pass. - Automation fallbacks have owners. - No buyer-facing automation fires without signoff. Assets: - Sample data package: /demo-library/referral-network/sample-data-package - CSV templates, sample rows, and import validation gates. - Sample data JSON: /demo-library/referral-network/sample-data-package.json - Machine-readable data dry-run manifest. - Production data contract: /demo-library/referral-network/data-contract - Entities, source systems, events, boundaries, and API-shaped routes. - Production data contract JSON: /demo-library/referral-network/data-contract.json - Machine-readable production data contract. - White-label kit: /demo-library/referral-network/white-label-kit - Naming, domain, terminology swaps, copy blocks, brand assets, and checklist. - White-label kit JSON: /demo-library/referral-network/white-label-kit.json - Machine-readable rebrand manifest. ### 5. Release, monitoring, and support Owner: Shared launch thread Timing: Go-live day Status: Implementation 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. Entry criteria: - Release gates are reviewed. - Support owner is assigned. - Monitoring thresholds are documented. Exit criteria: - Production route is promoted. - Monitoring is active. - Support and rollback owners are known. Assets: - Live sales preview: https://referral-network.ideas-realized.com?screen=matcher - First proof screen: Matchmaker. - Canonical landing page: /demo-library/referral-network - Indexable buyer proof page and primary demo-library route. - White-label kit: /demo-library/referral-network/white-label-kit - Naming, domain, terminology swaps, copy blocks, brand assets, and checklist. - White-label kit JSON: /demo-library/referral-network/white-label-kit.json - Machine-readable rebrand manifest. - Tenant clone package: /demo-library/referral-network/tenant-clone-package - Rebrand-and-launch handoff for a buyer tenant. - Tenant clone JSON: /demo-library/referral-network/tenant-clone-package.json - Machine-readable tenant clone package. ### 6. SEO/AEO publication Owner: Growth lead Timing: Go-live week Status: Implementation A publish-ready growth kit for using the Referral Network demo as an industry pillar, answer-engine proof source, comparison asset, and sales-qualified routing path. Entry criteria: - Buyer proof claim is approved. - Canonical and industry routes are available. Exit criteria: - Industry pillar, answer blocks, and internal links route demand back to the demo proof. Assets: - Canonical landing page: /demo-library/referral-network - Indexable buyer proof page and primary demo-library route. - Industry SEO/AEO page: /industries/referral-management-software-for-business-networks - Referral management software for business networks ## Acceptance Gates ### 1. Commercial order and SOW approval Phase: commercial-signoff Owner: Client sponsor Timing: Before kickoff Status: Implementation Source: Commercial Proof: Order packet, SOW, and rebrand rights point to LoopLedger as the client launch product. Acceptance criteria: Sponsor accepts scope, $18k-$32k pilot build, then $750-$2.5k/month for hosting, support, reporting, and feature iteration, launch boundaries, and payment milestone. Rollback: Hold tenant setup and keep the app as sales-preview only until pricing or scope redlines are resolved. ### 2. Tenant brand and production domain Phase: tenant-identity Owner: Client DNS owner Timing: Kickoff day 1 Status: Buyer input Source: Brand and domain Proof: Northstar Referral Guild is seeded for referral-network.ideas-realized.com; 3 DNS records are tracked. Acceptance criteria: Client confirms launch name, brand tokens, CNAME/TXT ownership, and fallback preview URL https://referral-network.ideas-realized.com. Rollback: Keep traffic on https://referral-network.ideas-realized.com and delay production alias activation until DNS checks pass. ### 3. Source data dry-run Phase: data-cutover Owner: Chapter admin Timing: Kickoff days 1-2 Status: Implementation Source: Data import Proof: 3 source groups and 3 tenant seed sources are mapped. Acceptance criteria: Chapter admin merges or removes duplicates before pilot launch. Rollback: Use seed data and read-only import review until source exports satisfy required fields and validation gates. ### 4. Access roles and permission boundaries Phase: access-automation Owner: Implementation lead Timing: Kickoff days 2-3 Status: Implementation Source: Access control Proof: 3 roles, 3 scopes, and 3 launch permission groups are documented. Acceptance criteria: Permission test script and demo ledger event ready for pilot data. Rollback: Revert affected users to internal-only review access and disable buyer-facing invitations until roles are corrected. ### 5. Automation and integration readiness Phase: access-automation Owner: Product lead Timing: Kickoff days 3-4 Status: Buyer input Source: Integrations Proof: 4 integrations, 3 automations, and 2 notifications are in the tenant seed package. Acceptance criteria: Credentials, sender identities, fallback owners, and disabled-by-default automations are confirmed before live users enter. Rollback: Disable automation rules, keep manual queue ownership, and preserve audit entries for replay after credentials are repaired. ### 6. Release gates and first proof screen Phase: go-live-release Owner: Chapter admin Timing: Go-live day Status: Implementation Source: Deployment Proof: 5 release gates protect Matchmaker: relationship matching and referral capture Acceptance criteria: Referral board, follow-up task, and recognition card update together. Rollback: Keep the sales preview subdomain live until the client production domain passes route, SSL, auth, and acceptance checks. ### 7. Monitoring and support handoff Phase: go-live-release Owner: Shared launch thread Timing: Go-live day + 1 Status: Ready Source: Support Proof: 3 monitors and 2 support levels are defined. Acceptance criteria: Shared launch thread: Business days during pilot. Renewal signal: Demo to discovery: 6 qualified discovery requests per quarter. Rollback: Pilot support scope: $750-$2.5k/month recurring for hosting, support, and workflow tuning. ### 8. SEO/AEO publication and internal links Phase: seo-aeo-launch Owner: Growth lead Timing: Go-live week Status: Implementation Source: SEO/AEO Proof: /industries/referral-management-software-for-business-networks anchors 3 launch-calendar entries and 3 answer blocks. Acceptance criteria: Canonical page /demo-library/referral-network, industry page /industries/referral-management-software-for-business-networks, and app proof URL are internally linked with buyer-ready CTA language. Rollback: Noindex unfinished support pages, preserve the canonical landing page, and republish after the buyer proof claim is verified. ## Rollback Controls ### DNS promotion rollback Trigger: Production domain fails verification, SSL, or route rewrite checks. Owner: Client DNS owner Response: Keep the sales preview subdomain live until the client production domain passes route, SSL, auth, and acceptance checks. Evidence: referral-network.ideas-realized.com: ready; referral-network.ideas-realized.com: needs-client; _netlify.referral-network.ideas-realized.com: needs-client ### Data import rollback Trigger: Required field validation, duplicate detection, or record counts fail during dry-run. Owner: Chapter admin Response: Keep tenant in seed-data mode and rerun the import after source mapping changes are approved. Evidence: Roster duplicate review: blocking; Category taxonomy approval: warning; Private note policy: blocking ### Automation rollback Trigger: Notification, escalation, integration, or automation action sends to the wrong owner or channel. Owner: Product lead Response: Disable automation rules, keep manual workflow ownership, and replay audit events after correction. Evidence: Stale introduction reminder: template; Meeting recognition queue: ready; Sponsor report checkpoint: optional ### SEO/AEO claim rollback Trigger: Buyer proof, KPI claim, or industry language is not yet approved for public publication. Owner: Growth lead Response: Noindex unfinished support routes and keep only the canonical demo page published until claims are approved. Evidence: Referral tracking software for business networking chapters: Service + SoftwareApplication + FAQPage; How to report referral value to sponsors without exposing private notes: Article + HowTo/FAQPage; Member referral CRM vs chapter referral workflow software: Article + FAQPage ## Buyer Signoff - Approve commercial order, SOW, rebrand rights, and first payment milestone for LoopLedger. - Confirm production domain referral-network.ideas-realized.com, buyer sponsor, launch window, and support owner. - Provide source exports for Member roster, Referral history, Sponsor reporting fields and approve import validation results. - Approve role matrix for Chapter admin, Member, Sponsor viewer before inviting live users. - Approve public proof language for /industries/referral-management-software-for-business-networks and /demo-library/referral-network. ## Implementation Handoff - Seed tenant package: /demo-library/referral-network/tenant-seed-package and /demo-library/referral-network/tenant-seed-package.json. - Data contract: /demo-library/referral-network/data-contract and /demo-library/referral-network/data-contract.json. - First proof screen: Matchmaker at https://referral-network.ideas-realized.com?screen=matcher. - Monitoring: Demo app availability under Homepage and app route return 200 from production domain after DNS cutover.; Accepted referrals with owner follow-up within 5 business days under Pilot usage is visible in the buyer dashboard within the first review cycle.; Confirm CRM or spreadsheet source of truth for partner accounts. under No open launch blocker can affect first user workflow.. - North-star analytics: 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.. ## SEO/AEO Publication - Canonical page: /demo-library/referral-network - Industry page: /industries/referral-management-software-for-business-networks - Referral tracking software for business networking chapters: /industries/business-networking-referral-software - How to report referral value to sponsors without exposing private notes: /resources/sponsor-referral-reporting - Member referral CRM vs chapter referral workflow software: /compare/member-referral-crm-alternative - LoopLedger canonical demo: /demo-library/referral-network - LoopLedger app-only preview: https://referral-network.ideas-realized.com - Referral Network demo: /demo-library/referral-network ## Route Map - Live sales preview: https://referral-network.ideas-realized.com?screen=matcher (app) - First proof screen: Matchmaker. - Canonical landing page: /demo-library/referral-network (canonical) - Indexable buyer proof page and primary demo-library route. - Industry SEO/AEO page: /industries/referral-management-software-for-business-networks (industry) - Referral management software for business networks - Client launch plan: /demo-library/referral-network/client-launch-plan (commercial) - Buyer-facing launch plan with order, data, SEO/AEO, and support steps. - Statement of work: /demo-library/referral-network/statement-of-work (commercial) - Buyer-signable scope, milestones, responsibilities, service levels, and change controls. - Statement of work JSON: /demo-library/referral-network/statement-of-work.json (commercial) - Machine-readable scope and acceptance manifest. - Deal desk package: /demo-library/referral-network/deal-desk (commercial) - Order form, pricing bands, approval gates, add-ons, and redlines. - Deal desk JSON: /demo-library/referral-network/deal-desk.json (commercial) - Machine-readable commercial close manifest. - Sample data package: /demo-library/referral-network/sample-data-package (data) - CSV templates, sample rows, and import validation gates. - Sample data JSON: /demo-library/referral-network/sample-data-package.json (data) - Machine-readable data dry-run manifest. - Production data contract: /demo-library/referral-network/data-contract (data) - Entities, source systems, events, boundaries, and API-shaped routes. - Production data contract JSON: /demo-library/referral-network/data-contract.json (data) - Machine-readable production data contract. - White-label kit: /demo-library/referral-network/white-label-kit (deployment) - Naming, domain, terminology swaps, copy blocks, brand assets, and checklist. - White-label kit JSON: /demo-library/referral-network/white-label-kit.json (deployment) - Machine-readable rebrand manifest. - Tenant clone package: /demo-library/referral-network/tenant-clone-package (deployment) - Rebrand-and-launch handoff for a buyer tenant. - Tenant clone JSON: /demo-library/referral-network/tenant-clone-package.json (deployment) - Machine-readable tenant clone package. - Tenant seed package: /demo-library/referral-network/tenant-seed-package (deployment) - Users, roles, data sources, integrations, feature flags, automations, and notifications. - Tenant seed JSON: /demo-library/referral-network/tenant-seed-package.json (deployment) - Machine-readable tenant seed manifest. - Tenant cutover plan: /demo-library/referral-network/tenant-cutover-plan (deployment) - Downloadable cutover packet for buyer and implementation signoff. - Tenant cutover JSON: /demo-library/referral-network/tenant-cutover-plan.json (deployment) - Machine-readable cutover manifest for automation and QA.