Signal Foundry
Revenue Partner Intro Referral Public Proof BoardClient-referral public-proof hub
Referral public proof works when the asset stays compact. This board helps choose the right proof shape, decide whether the story belongs on a trust page, proof page, or library slot, freeze what stays hidden, and widen only when a small public block stops doing the job.
Referral Public Proof Map
Build the public asset from proof that already exists. Referral public proof should come from approved capture or a compact slot, not a blank rewrite.
Open Partner Intro Public Proof Family Open Partner Intro Referral Public Proof FamilyMost referral public proof should begin as an anonymous line, brandless before-after, quote-led block, or redacted evidence tile.
Decide whether the asset should live first on a proof page, a trust page, or a case-study route. One destination keeps the claim believable.
Open Partner Intro Referral Public Proof Page Open Partner Intro Referral Public Trust Page Open Partner Intro Referral Public Case Study RouterBuyer identity, screenshots, margins, internal mechanics, and the referral path stay outside the public asset unless those rights are cleared separately.
A referral public proof asset should stay narrower than a case page. If a trust block or proof block already clears doubt, keep the larger story unpublished.
Open Partner Intro Referral Public Trust Page Open Partner Intro Referral Public Story BoundaryIf the compact block is too small, widen deliberately into a case-study route instead of improvising a broader public claim.
Open Partner Intro Referral Public Story Boundary Open Partner Intro Referral Public Case Study Page Open Partner Intro Referral Public Case Study RouterProof Shapes
One line on buyer type, bottleneck, and shift without exposing who the buyer or referrer actually was.
A compact summary that shows movement without logos, screenshots, or traceable brand detail.
One approved line with a short context sentence when voice adds trust without needing a longer public story.
One masked artifact when a concrete detail helps more than a plain summary but raw proof would expose too much.
One public-safe line that supports credibility on a trust page without becoming a broader narrative.
A referral public proof asset that stays valuable precisely because it does not expand into every page and claim at once.
Proof Snapshot
| Proof Shape | Public Signal | Keep Hidden | Best First Page | Escalate If |
|---|---|---|---|---|
| Anonymous strip | Buyer type plus shift | Buyer identity and screenshots | Proof or trust page | The audience still wants harder proof |
| Brandless card | Before-after summary | Brand clues and private stack | Proof page | The block feels too abstract |
| Quote-led block | Speaker plus shift | Broader testimonial rights | Trust or proof page | One line is not enough |
| Redacted tile | Masked concrete result | Raw evidence and margins | Proof page | More visible detail is requested |
| Trust note | Public-safe trust line | Private referral path | Trust page | Buyers need a fuller story |
Pasteable Lines
I want the public layer to carry one believable proof block, not the whole private history behind this referral win.
The public block should name the bottleneck and the shift so the result is clear without retelling the whole referral path.
Open Partner Intro Referral Public Proof PageNames, screenshots, deal mechanics, and the referral path stay outside the public block unless those rights are approved separately.
Let us give this proof one public job first so it does not drift into trust pages, proof pages, and case studies all at once.
Open Partner Intro Referral Public Proof Router Open Partner Intro Referral Public Trust Page Open Partner Intro Referral Public Proof PageIf one compact public block already creates enough trust, the better move is to leave the larger story unpublished.
Open Partner Intro Referral Public Trust PageIf this compact proof block stops working later, we can widen deliberately through case-study routes.
Open Partner Intro Referral Public Story BoundaryBest Next Routes
If the asset belongs on one proof page block instead of the wider referral public proof layer, route through the public proof router first.
Open Partner Intro Referral Public Proof Router Open Partner Intro Referral Public Proof PageIf the main job is public credibility, route into the trust page instead of building a heavier proof section.
Open Partner Intro Referral Public Trust PageIf the asset should stay reusable but smaller than a public page, route into the proof-library slot instead.
If the block should keep the buyer hidden, route into anonymous proof before placing it publicly.
If even buyer-hidden detail is too traceable, route into a brandless version before public placement.
If one approved voice line adds the most trust, route into the quote page before widening the public proof.
If one proof block is not enough and the audience needs a broader before-after story, route into the case-study board next.
Open Partner Intro Referral Public Case Study RouterIf the same proof should mainly help repeat the lane, route into repeat instead of giving it a bigger public role.
If the proof layer has done its job and the buyer is ready to move, send them into the payment page next.
Open Payment PageWallet
Referral public proof rises faster when the block stays believable and the private relationship path never has to be exposed.
0xB3e9568A9cbB624403743340358c85CCce130893
Open Payment Page