1. Start From The Closed Referral Proof Boundary
Begin with the approved proof line, quote, or compact slot that already exists. Do not start by drafting a bigger public narrative.
Signal Foundry
Revenue Partner Intro Referral Public Story Boundary BoardClient-referral public-page boundary page
A client-referred result can be commercially useful on a public page, but that does not mean the whole private story should go public. This page helps choose the smallest safe public version: a trust proof line, a compact proof card, a quote-led mini story, or a fuller case route only when the buyer, referrer, and hidden economics can stay protected.
Referral Public Story Map
Begin with the approved proof line, quote, or compact slot that already exists. Do not start by drafting a bigger public narrative.
Many referral wins should stay in repeat lanes, reply threads, or proof slots. Go public only if that creates clear leverage.
Open Partner Intro Public Story Lane Open Partner Intro Referral Public Story LaneStart with the smallest public-safe layer: anonymous proof, brandless before-after, one quote-led mini story, or one trust-focused result line.
Open Partner Intro Referral Public Trust PageKeep buyer identity, screenshots, margins, internal mechanics, and the private referral path outside the public version unless approved separately.
Put the asset on one public destination first: a trust page, a proof page, or a case-study page. Do not spread it everywhere by default.
Open Partner Intro Referral Public Trust Page Open Partner Intro Referral Public Proof Page Open Partner Intro Referral Public Case Study PageIf the compact public proof is not enough, widen into the case-study boundary first instead of improvising a larger public story.
Open Partner Intro Referral Public Case Study Router Open Partner Intro Referral Public Proof Page Open Partner Intro Referral Public Case Study PagePublic-Safe Formats
One short public line that makes the process feel credible without unpacking the full private win.
A generic before-after card that shows the shift without naming the buyer or exposing delivery context.
One approved named or role-based line plus a small amount of public-safe context.
A narrow public page that names the account type and shift while keeping the buyer and referral path hidden.
A compact asset can be public only if it still behaves like one bounded block instead of a broad public claim.
If public use adds more exposure than leverage, keep the proof in repeat lanes, reply threads, or the slot system instead.
Public Snapshot
| Format | Safe Public Detail | Keep Hidden | Best First Page | Review Trigger |
|---|---|---|---|---|
| Trust proof line | Process credibility and result shift | Buyer name and internal mechanics | Trust page | Before any wider story rewrite |
| Brandless public card | Before-after summary | Logos, screenshots, and pricing detail | Proof page | If a case request appears |
| Quote-led mini story | One approved quote and context line | Broader testimonial rights | Proof or trust page | Before using on multiple public pages |
| Anonymous public story | Account type and shift | Traceable buyer and referrer details | Proof page or case page | If naming becomes useful later |
| Fuller case story | Broader narrative with boundaries | Referral path and hidden economics | Case-study page | Before wider proof-slot reuse |
Pasteable Lines
Before we make this public, I want to check whether a compact public proof line is enough instead of a broader story.
If this goes public, names, screenshots, margins, and the referral path should still stay outside the page.
I want this to land on one public destination first so we do not quietly turn one proof unit into a site-wide claim.
Open Partner Intro Referral Public Trust Page Open Partner Intro Referral Public Proof Page Open Partner Intro Referral Public Proof RouterI would rather start with an anonymous, brandless, or quote-led public version than jump straight into a bigger public story.
If a fuller public page is really needed, I want that to pass through a separate case-study boundary decision rather than an automatic expansion.
Open Partner Intro Referral Public Case Study Router Open Partner Intro Referral Public Case Study PageIf the small public proof already does the job, there is no need to publish the whole private story behind it.
Best Next Routes
If the main job is public credibility rather than a fuller story, route into the trust router first.
Open Partner Intro Referral Public Trust Router Open Partner Intro Referral Public Trust PageIf the asset should sit inside a wider referral proof system, route into the public proof router first so the next page choice stays narrow and deliberate.
Open Partner Intro Referral Public Proof Router Open Partner Intro Referral Public Proof BoardIf the public version should keep the buyer hidden, widen into anonymous proof first.
If even buyer-hidden detail is too revealing, use a brandless public proof asset first.
If one named or role-based line adds the most trust, route into the quote page before anything broader.
If the asset should stay reusable but smaller than a public page, route back into the referral proof-library slot.
If the audience truly needs a larger before-after story, move into the case-study boundary before the public case page.
Open Partner Intro Referral Public Case Study Router Open Partner Intro Referral Public Case Study PageIf the proof should help repeat the same lane more than it helps a public audience, route into repeat instead.
Wallet
Keep the public page narrower than the private referral path that made the win possible, and widen only when the extra exposure is worth it.
0xB3e9568A9cbB624403743340358c85CCce130893
Open Payment Page