SF

Signal Foundry

Revenue Referral Public Proof Page Board
Command Center Links Hub Referral Public Proof Family Referral Public Proof Lane Referral Public Proof Router Referral Public Proof Referral Public Proof Capture Partner Public Proof Page Referral Public Trust Referral Public Case Study Page Payment

Referral public proof-page placement

Place one referral-safe proof asset on one public proof page without turning it into a broader story than anyone approved.

A referral public proof page works best when it stays compact. The right move is usually one proof block, one headline, one safe context line, and one clear page destination. That keeps the proof public enough to help trust while keeping the hidden referral path and hidden details out of view.

  • 1 proof block per page slot
  • 1 headline per approved asset
  • 0 site-wide claim implied

Referral Public Proof Map

Use one sequence from approved proof asset to one public proof page block.

3. Write One Proof-Page Headline

Use the bottleneck and the shift as the headline logic so the block is clear fast without expanding into a long public story.

Open Referral Public Proof

Good Proof Blocks

Most referral public proof pages should start with one of these smaller blocks.

Compact Result Strip

One line on buyer type, bottleneck, and visible shift without exposing who the buyer or referrer actually was.

Referral-Safe Proof Block

A compact summary that shows movement while keeping referral mechanics and hidden economics out of the public layer.

Trust-Led Note

One public-safe line that supports credibility on a trust page without becoming a broader narrative.

Proof Page Tile

One reusable evidence block that sits on a proof page without immediately widening into a broader public story.

Case Escalation Trigger

One bounded signal that tells you when a proof page is no longer enough and a case-study page should take over.

Do-Not-Widen Block

A public proof block that stays useful precisely because it does not turn into a site-wide or case-study claim too early.

Proof Page Snapshot

Freeze the block, safe context, and page destination in one place.

Block Type Headline Safe Detail Keep Out Best Page
Compact result strip Buyer type plus shift Bottleneck and result line Buyer identity and screenshots Proof page
Referral-safe block Before-after friction Generic business context Referrer detail and hidden economics Proof page
Trust-led note Credibility cue One approved line Full relationship map Trust or proof page
Case trigger Before-after spine One bounded narrative cue Full deal path Case-study page later

Best Next Routes

Route to the page that resolves the next public-proof decision fastest.

Need Proof Router

If the proof page still needs a routing decision, move back into the referral public proof router before widening the page further.

Open Referral Public Proof Router

Need Smaller Proof

If the page feels larger than necessary, shrink it into one compact public proof block instead.

Open Referral Public Proof

Need Trust-First Placement

If one credibility signal is enough, route into the public trust page instead of carrying a broader proof section.

Open Referral Public Trust

Need Case-Study Escalation

If one proof block is too small for the moment, move into the case-study system instead of improvising a broader proof story.

Open Referral Public Case Study Page

Need Payment And Start

If the page and ask are already fixed, keep the payment route attached to the same commercial story.

Open Payment Page

Wallet

Preferred route: one referral-safe proof page, one next ask, one hidden layer preserved.

A referral public proof page earns more trust when the block stays specific, the proof stays bounded, and the hidden path behind the win stays off-page.

0xB3e9568A9cbB624403743340358c85CCce130893 Open Payment Page