Referral public family selector

Decide whether one approved referral-safe public asset should stay in the referral public family or strengthen the partner public family next.

Once one delivered-win quote, proof snippet, trust page angle, or case-study asset is approved, the next job is not spraying it across every path. The real job is deciding whether that asset should keep serving the referral public system that created it or become part of the broader partner-channel public system.

Open Referral Public Family Map Open Referral Public Lane

2 public family options
3 main public destinations
0 hidden relationship leaks required

Referral Public Family Rule

Keep the asset in the referral public family unless the public job now clearly belongs to the broader partner family.

Referral-safe public assets can travel farther without becoming generic. Good routing chooses one family first, keeps buyer and referrer context locked, and stops one asset from drifting between referral and partner claims without a deliberate reason.

Choose: the public family first
Route: into one public system
Protect: the hidden referral layer

Referral Public Family Map

Use one sequence from approved referral-safe public asset to the right public family.

1. Start From One Approved Referral-Safe Public Asset

Use this page only after one delivered-win story, approved quote, public-safe proof line, or compact trust asset already exists and is cleared for use. If approval is still fuzzy, keep it out of public family routing for now.

Open Case Converter Open Referral Public Proof Capture

2. Decide Whether The Asset Should Stay Referral-Specific

Some assets should keep helping the next client-sourced intro, while others can now reinforce the broader partner public family because the signal pattern has become portable enough.

Open Referral Family Open Partner Family Open Referral Public Lane Open Referral Public Story Family Open Referral Public Story Lane Open Referral Public Router Open Referral Public Board Open Referral Public Proof Open Partner Public Family Open Partner Public Story Family

3. Keep It In The Referral Public Family When The Next Win Still Depends On Client Context

If the asset mainly helps another client-sourced introduction, keep it inside the referral public family and choose the narrower proof, case, or trust-support path there.

Open Referral Public Router Open Referral Public Story Family Open Referral Public Story Lane Open Referral Public Story Boundary Open Referral Public Boundary Open Referral Public Trust Open Referral Public Proof Open Case Converter Open Referral Public Proof Capture Open Referral Public Trust

4. Repurpose It Into The Partner Public Family Only When The Public Job Is Now Broader

If the signal can now support partner acquisition, reseller trust, or white-label collaboration without depending on client context, move it into the partner public family and choose the narrower trust, proof, or case route there.

Open Partner Public Router Open Partner Public Lane Open Partner Public Story Family Open Partner Public Story Lane Open Partner Public Story Boundary Open Partner Public Boundary Open Partner Public Trust Open Partner Public Proof Open Partner Public Family Open Partner Public Proof Open Referral Public Case Study

5. Freeze What Must Stay Hidden

Referrer identity, buyer identity, private screenshots, economics, and relationship logic remain attached to the family that created them even if one asset becomes reusable elsewhere.

Open Referral Public Board Open Referral Public Payout Open Referral Public White Label Open Proof Board

6. Keep The Payment Path Attached To The Chosen Family

Once the public family is chosen, keep the next ask, payment path, and commercial follow-through inside that same family instead of reopening the routing decision every time the asset gets reused.

Open Referral Public Payout Open Payment Page Open Renewal Board

First Destinations

Most approved referral-safe public assets belong in one of these first public-family destinations.

Referral Public Board

Best when the asset already has a public family, route, and one exact live job inside the referral public system.

Case Converter

Best when the asset should make the next referral ask easier before it widens into a broader channel narrative.

Proof Board

Best when the asset should stay compact as a public-safe proof layer for future intros.

Trust Board

Best when the buyer still needs confidence in process, outcome, or delivery before the story needs to get broader.

Partner Public Family

Best when the same public-safe asset should now help broader partner-channel demand more than referral asks.

Partner Proof

Best when the signal now needs partner-specific payout, repeatability, or white-label framing.

Case Study Board

Best when the signal is strong enough to become a reusable public case instead of a narrow referral proof line.

Family Snapshot

Freeze the chosen public family, the first public system, and the hidden layer before the asset spreads.

Public Family	Best Asset	First Public System	Keep Hidden	Promotion Trigger
Referral public family	One approved asset tied to a delivered buyer story	Referral Public Board	Referrer path, buyer detail, and delivery context	The next best move is another client-sourced intro
Partner public family	One portable signal no longer dependent on referral context	Partner Proof	Channel source and commercial terms	The pattern now supports broader partner conversion
Proof-first public branch	One concise public-safe result line	Proof Board	Anything not cleared beyond proof use	The signal is commercially useful but not yet a full public case
Trust-first public branch	One believable but still narrow credibility asset	Trust Board	Anything not cleared beyond public trust use	The buyer needs confidence before heavier proof or broader story

Wallet

Once the referral-safe public family is chosen, keep the next paid step inside that same route.

Choose the public family first, lock the hidden relationship layer, then move payment through the matching route so the asset does not drift between referral and partner claims.

0xB3e9568A9cbB624403743340358c85CCce130893 Open Payment Page