SF

Signal Foundry

Revenue Partner Intro Referral Case Study Boundary Board
Command Center Partner Intro Referral Proof Capture Partner Intro Referral Proof Library Slot Partner Intro Referral Public Story Boundary Partner Intro Referral Reuse Boundary Partner Intro Referral Quote Partner Intro Referral Anonymous Proof Partner Intro Referral Brandless Proof Partner Intro Referral Redacted Proof Partner Intro Referral White Label Partner Intro Referral Case Study Board Partner Intro Referral Public Case Study Router Partner Intro Referral Public Case Study Page Partner Intro Referral Case Study Converter Partner Intro Referral Repeat Payment

Client-referral broader-proof page

Before one referral win becomes a public case page, fix the boundary that keeps the lane safe.

Small approved proof and broad published proof are not the same thing. A closed client-referred win may justify a larger public asset later, but only if the buyer boundary, referrer path, hidden economics, and publication rights are all clear. This page keeps a useful result from turning into an oversized public claim too early.

  • 4 case-study-safe formats
  • 1 publication decision per asset
  • 0 assumed naming rights

Referral Case Boundary Map

Use one sequence from closed referral proof to a broader public asset only when it is truly safe.

Safer Formats

Most referral wins should widen only into one of these narrower case-study forms.

Anonymous Case

Keep the account type, bottleneck, and shift visible while removing the buyer identity entirely.

Brandless Before-After

Explain what changed without logos, screenshots, or page details that expose the private referral context.

Quote-Led Mini Case

Use one approved partner-safe line plus stripped-down business context instead of a larger testimonial package.

Redacted Evidence Case

Use one masked concrete detail only if the proof still needs a visible artifact before a broader audience will trust it.

Public Case Spine

Route into a narrow before-after spine only when the referral path no longer creates extra privacy or relationship risk.

Stay Small Instead

If the bigger asset creates more risk than leverage, keep the win as a small public proof block and stop there.

Boundary Checklist

Freeze the destination and hidden layer before publishing anything larger.

Question Safe Now Not Yet Best First Destination
Can the buyer be identified? No, keep it anonymous or brandless Named client story Brandless or anonymous proof
Can screenshots travel? Only if redacted tightly Raw screen set Redacted proof or private approval
Can the partner be quoted? One approved line Long testimonial package Quote-led mini case
Can the story go on the public site? Only in one narrow approved format Everywhere by default Public case page, not every page
Should it help future referrals? Yes, if the same privacy rule holds Broader public claims Repeat lane or intro pack

Pasteable Lines

Use short lines that stop a small referral proof asset from quietly turning into a public case page.

Need Line

Before we widen this, I want to check whether a bigger case page is actually useful or if the smaller public proof is already enough.

Repeat Line

If the real value is helping similar referral lanes, the better move may be repeat support rather than a broader public case page.

Open Partner Intro Referral Repeat

Best Next Routes

Route into the narrowest page that still makes the proof more useful.

Need One Named Safe Line

If one narrow quote is enough, use the quote page instead of asking for a broader testimonial or case page.

Open Partner Intro Referral Quote

Wallet

Preferred route: small proof approved, hidden layer preserved, one broader destination chosen deliberately.

A larger proof asset should stay narrower than the private story behind it. Publish one safe version first and keep new reuse asks separate.

0xB3e9568A9cbB624403743340358c85CCce130893 Open Payment Page