# LoopLedger statement of work package

A buyer-signable SOW packet for turning Referral Network into a paid, rebrandable referral management software for member networks and partner-led revenue teams pilot with scoped deliverables, acceptance gates, data responsibilities, support terms, change controls, and signature ownership.

Buyer default: Northstar Referral Guild
Recommended tier: Cohort pilot
Investment summary: $18k-$32k setup and $750-$2.5k/month recurring. 50 percent due at signature to reserve implementation slot and start roster mapping.
Target launch window: Weeks 8-12; 2 weeks tenant setup, 2 weeks workflow hardening, 2 weeks chapter pilot and report review.
SOW term: 6-week chapter referral pilot for one network, one chapter, and up to 250 member records.
Production domain: referral-network.ideas-realized.com
Preview URL: https://referral-network.ideas-realized.com
JSON manifest: /demo-library/referral-network/statement-of-work.json

## Agreement Snapshot

- Product: LoopLedger
- Buyer: Northstar Referral Guild
- First proof screen: matcher
- First proof URL: https://referral-network.ideas-realized.com?screen=matcher

## Scope Modules

- Tenant setup: White-label chapter workspace. Scope: Configure brand tokens, subdomain, member roles, referral stages, and launch assets for the pilot chapter. Acceptance: Referral board, follow-up task, and recognition card update together.
- Data onboarding: Roster import and validation. Scope: Map member roster fields, validate required records, flag duplicates, and produce an import exception list. Acceptance: Markdown and JSON exports include GTM and launch package fields.
- Workflow configuration: Referral follow-up operations. Scope: Configure stale referral reminders, meeting recognition prep, sponsor report checkpoints, and manual CRM export. Acceptance: Permission matrix ready; needs client sign-off.
- Pilot review: Sponsor-ready evidence package. Scope: Deliver KPI snapshot, report sample, backlog recommendation, and CRM integration decision for the next phase. Acceptance: Confirm chapter admin, sponsor viewer, and member coordinator access boundaries.

## Delivery Milestones

- Kickoff (Week 1, Client sponsor): Roster, attribution rules, and chapter goals confirmed. Exit: Import template approved and pilot chapter roles assigned. Payment: 50 percent due at signature to reserve implementation slot and start roster mapping.
- Configuration (Weeks 2-3, Implementation lead): Tenant, workflows, reports, and launch checklist configured. Exit: Admin review passes roster, referral, reminder, and report scenarios. Payment: 30 percent due after branded workspace, referral stages, and admin review are accepted.
- Pilot (Weeks 4-6, Chapter admin): Members and admins use the workflow during real referral activity. Exit: Sponsor report exported with agreed pilot KPI summary. Payment: 20 percent due after sponsor-ready pilot report and expansion recommendation are delivered.

## 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.
- 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.

## Buyer Responsibilities

- Provide roster export and confirm member communication permissions.
- Name an admin who can validate referral status language and sponsor report wording.
- Keep CRM writeback out of scope unless explicitly approved as a follow-on phase.
- 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.

## Ideas Realized Responsibilities

- Owns configuration, runbook, QA evidence, and post-pilot backlog recommendation.
- 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.
- Shared launch thread: Business days during pilot
- Maintain the demo-derived production domain plan for referral-network.ideas-realized.com.

## Data And Security Responsibilities

### Buyer operations owner

- 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.
- Member roster: provide 80 to 250 member records from Chapter spreadsheet or association CRM export with [object Object], [object Object], [object Object], [object Object].
- Referral history: provide 50 to 500 referral records from Spreadsheet, form export, or CRM activity report with [object Object], [object Object], [object Object], [object Object].
- Sponsor reporting fields: provide 10 to 30 sponsor-visible metrics from Board report spreadsheet with [object Object], [object Object].

### Ideas Realized implementation lead

- 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.
- Roster duplicate review: Duplicate emails or member names prevent referral attribution. Resolution: Chapter admin merges or removes duplicates before pilot launch.
- Category taxonomy approval: Unmapped business categories weaken member search and referral matching. Resolution: Approve a chapter category list during setup.
- Private note policy: Historical referral notes may contain sensitive deal details. Resolution: Import only summary notes until retention and consent rules are approved.

## Support And Service Levels

- Shared launch thread: Business days during pilot; response Next business day. Included: Roster import questions, workflow tuning, report changes, and launch checklist review.
- Weekly pilot review: One 45-minute session per week; response Scheduled. Included: KPI review, blocker triage, adoption notes, and next-step scope recommendations.

## Change Orders And Exclusions

- Change control: Additional chapters, billing, or member renewal workflows: Scope as a separate expansion package after the first sponsor review. Owner: Growth lead.
- Change control: Bidirectional CRM sync or automatic activity creation: Requires API review, field map approval, and integration estimate. Owner: Implementation lead.
- Exclusion: No member billing, event ticketing, or dues management in the first pilot.
- Exclusion: No bidirectional CRM sync unless the integration add-on is signed.
- Exclusion: Private deal value fields stay hidden from sponsor views unless legal and chapter policy approve the aggregate format.
- Exclusion: Do not promise private member-to-member messaging as part of the pilot.
- Exclusion: Do not commit to real-time CRM writeback before API review.
- Exclusion: Do not expose referral value by member without explicit buyer approval.

## Legal Review Notes

- This demo SOW package is a sales and implementation planning artifact, not legal advice.
- Final MSA, DPA, payment terms, taxes, procurement language, and security addenda require buyer/legal review before signature.
- No regulated production data should be loaded until data-processing, access, retention, and incident-response terms are approved.

## 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.

## Implementation Handoff Links

- Deal desk package: /demo-library/referral-network/deal-desk
- Deal desk package JSON: /demo-library/referral-network/deal-desk.json
- Procurement pack: /demo-library/referral-network/procurement-pack
- Client proposal: /demo-library/referral-network/client-proposal
- Client launch plan JSON: /demo-library/referral-network/client-launch-plan.json
- Implementation work order: /demo-library/referral-network/implementation-work-order
- Deployment launch plan JSON: /demo-library/referral-network/deployment-launch.json
- Production data contract JSON: /demo-library/referral-network/data-contract.json
- Tenant seed package JSON: /demo-library/referral-network/tenant-seed-package.json
- Buyer launch room: /demo-library/referral-network/launch-room