Which product boundaries should be set for referral sources, opportunities, and performance reporting?
Scope referral sources, relationships, introductions, consent, attribution, opportunities, status, communication, recognition or fees, conflicts, and performance reporting. Treat referral sources, relationships, and opportunities as one operated product boundary. A credible first release makes performance reporting observable and defines how exceptions involving conflicts are recovered.
Best for: Teams planning Referral Relationship CRM that need to agree on referral sources, opportunities, and performance reporting before detailed scope.
The first release should connect referral sources to performance reporting and expose a clear recovery path for exceptions involving conflicts.
Good fit / poor fit
Test whether referral sources and opportunities require an operated product
This topic is specific enough when referral sources has durable state, opportunities changes that state, and the team can own exceptions around conflicts while observing performance reporting.
Good fit when
Referral Relationship CRM needs a durable workflow connecting referral sources, opportunities, and observable evidence for performance reporting.
People in the customer-facing user role need a repeatable path from introductions through opportunities.
The revenue operations must govern relationships and intervene when exceptions involve conflicts.
Progress can be observed through performance reporting, not merely visits or screen activity.
Choose a narrower model when
An existing tool or simple information surface can already handle referral sources without owning its lifecycle.
relationships does not need separate permissions, history, or accountable state.
No operated workflow must connect introductions to opportunities.
The team cannot yet name who resolves exceptions around conflicts or what evidence is needed for performance reporting.
End-to-end workflow
Trace referral sources through opportunities and evidence for performance reporting
Use one representative Referral Relationship CRM journey. Keep relationships, exceptions around conflicts, and manual operator work visible so the release boundary reflects the real product rather than an idealized happy path.
1
Frame Introductions
Customer-facing user
A person in the customer-facing user role enters with introductions and enough context to begin working with referral sources.
Revenue operations
The revenue operations function defines eligibility, ownership, and the initial state for referral sources.
Boundary question
Who may begin with introductions, and what makes referral sources ready?
2
Establish Relationships
Customer-facing user
A person in the customer-facing user role creates, selects, or confirms relationships before progressing.
Revenue operations
The revenue operations function validates permissions, quality, and lifecycle rules around relationships.
Boundary question
Which version of relationships is authoritative, and which changes need history or review?
3
Operate Opportunities
Customer-facing user
A person in the customer-facing user role moves through opportunities with visible state, next actions, and feedback.
Revenue operations
The revenue operations function observes status, stalled work, and interventions that cannot be safely automated.
Boundary question
Which state changes prove progress through opportunities, and where does status branch?
4
Handle Conflicts exceptions
Customer-facing user
A person in the customer-facing user role receives a clear recovery path when an exception involving conflicts interrupts the expected journey.
Revenue operations
The revenue operations function resolves the exception, records the result, and captures evidence for performance reporting.
Boundary question
Who owns exceptions around conflicts, and what evidence is needed for performance reporting?
First-release boundary
Scope the smallest release that makes performance reporting observable
The first release of Referral Relationship CRM should connect introductions to performance reporting before expanding every variant of communication, integration, automation, or reporting need.
Prove in the first release
Name one primary customer-facing user segment and the exact role of referral sources in its journey.
Model the minimum state and permissions needed for relationships and introductions.
Implement one complete path through opportunities, including the essential branch around status.
Give the revenue operations a practical way to detect, inspect, and recover exceptions involving conflicts.
Capture evidence of performance reporting so the team can continue, narrow, or revise the product boundary.
Hold until evidence justifies it
Additional audiences, variants, and advanced permissions around referral sources and relationships.
Automation, integrations, and optimization for communication before the core workflow is reliable.
Sophisticated reporting or personalization beyond the evidence needed to verify performance reporting.
Decisions that materially change effort
The number of roles and permission boundaries controlling referral sources and relationships.
Lifecycle branches, approvals, reversals, and recovery paths across opportunities and status.
Operational exposure when exceptions involving conflicts occur repeatedly or at scale.
External systems that create, change, or depend on introductions or communication.
Audit, accessibility, availability, localization, and support expectations attached to performance reporting.
Trust, exceptions, and operations
Assign ownership for opportunities, exceptions around conflicts, and performance reporting
The interface for Referral Relationship CRM is only the visible layer. The operating model must also govern referral sources, keep relationships trustworthy, and make recovery from exceptions involving conflicts practical.
Ownership of Referral sources
The revenue operations function needs explicit rules for creating, changing, and retiring referral sources while keeping relationships consistent.
Who creates or approves referral sources, and which roles may change it?
What happens when referral sources and relationships disagree?
Which changes need history, notification, approval, export, or deletion controls?
Control of Opportunities
Every important transition through opportunities needs a visible owner, especially where status changes the normal path.
Which states make progress through opportunities visible to each role?
Where can status be automated safely, and where is review required?
How is duplicated, abandoned, or contradictory work returned to a valid state?
Recovery for Conflicts exceptions
A credible release makes exceptions involving conflicts visible, gives the revenue operations a workable response, and preserves evidence for performance reporting.
What can the customer-facing user do when an exception involving conflicts occurs without contacting support?
Which evidence does the operator need to investigate and resolve exceptions around conflicts?
Which signal demonstrates performance reporting without relying on vanity metrics?
Useful next steps
Turn the planning boundary into an evidence-backed first release
For Referral Relationship CRM, use the CRM guide to verify the wider product model, then choose whether a quick range or a detailed plan is the useful next step. These links are limited to routes that advance this decision.
Focus on contracts or terms, renewal dates, owners, health, stakeholders, tasks, forecasts, expansion opportunities, pricing context, approvals, and handoffs.
Planning basis and review
A complete catalog brief with room for deeper research
This page is generated from the reviewed WebGrid opportunity catalogue and application-type decision model. The baseline was reviewed 17 August 2026; its next scheduled review is 17 February 2027.
This guide defines product responsibilities. Payment, tax, consumer, identity, privacy, and marketplace obligations depend on jurisdiction, provider configuration, contracts, and operating choices; verify them with the relevant specialists.