1. Start From The Approved Referral Asset
Use this page only after the referral win already has one clean approved proof asset or summary worth making public.
Client-referral public case page
Turn one closed referral win into a public case-study page without exposing the hidden referral path behind it.
A referral-backed case page can help future demand, but it should stay narrow. The strongest version is one bottleneck, one fix, one visible shift, and one page destination. That gives a future buyer useful public proof while keeping the original referrer, buyer context, hidden economics, and operating details out of sight.
- 1 case page per approved story
- 1 before-after spine
- 0 need to expose the referral chain
Referral Case Map
Use one sequence from closed referral proof to one narrow public case-study page.
2. Pick One Public-Safe Story Shape
Most referral case pages should still begin from a tighter public trust or proof format before they widen into a fuller case page.
Open Partner Intro Referral Public Trust Page Open Partner Intro Referral Public Proof Page3. Keep The Referrer And Buyer Path Hidden
The public page should show the bottleneck and shift, not the original buyer introduction path, referrer identity, or deal mechanics.
4. Publish Into One Case Page First
Give the story one home before it spreads into multiple forwards, pack variants, or site-wide claims.
5. Use The Page To Support Real Forwarding
The public page should help the next referred buyer move faster, not become a loose marketing artifact without a sales path.
6. Review Again Before Broader Reuse
If this page should later become broader public proof, repeat support, or renewal support, review the boundary again explicitly.
Case Shapes
Most referral public case pages should start from one of these tighter story formats.
Anonymous Mini Case
Show the buyer pattern, the bottleneck, and the visible shift without exposing names or a traceable referral path.
Brandless Before-After
Show the problem and the result without logos, screenshots, or context that reveals the original buyer too easily.
Quote-Led Referral Story
Use one approved line and one context sentence when a voice cue helps the page without widening it into a bigger testimonial set.
Proof-Backed Mini Page
Use one safe proof block to anchor the story when plain summary alone would feel too soft.
Do-Not-Sprawl Page
Keep the page valuable by not letting it expand into every public asset, outbound forward, and proof slot at once.
Short Lines
Use short lines that keep the public referral case page commercially useful and narrow.
Need Line
We only need one narrow public case page here, not a broader public story that exposes the original referral path.
Spine Line
I want this page to follow one before-after spine so the result is clear without publishing the whole delivery timeline.
Hidden Layer Line
Names, screenshots, deal mechanics, and the original referrer should stay outside the case page unless they are cleared separately.
Forward Line
This page should help the next referral move faster, not become a detached marketing asset with no clear sales route.
Best Next Routes
Go to the page that removes the current referral proof blocker fastest.
Need The Case Route First
If the page feels too specific and you need to recheck story shape, hidden layer, and route choice, go back to the referral public case router first.
Open Partner Intro Referral Public Case Study RouterNeed The Pack First
If the next job is helping one buyer forward the story now, tighten the referral pack before widening the public page.
Need The Message First
If the public page exists but the actual intro line still is weak, route into the message board next.
Need The Proof Page First
If a case page still feels too large, shrink back into a tighter public proof page or trust page first.
Open Partner Intro Referral Public Proof Page Open Partner Intro Referral Public Trust PageNeed The Repeat Path First
If the story should support another similar buyer or broader next move, route into repeat or expansion next.
Wallet
Preferred route: one referral case spine fixed, one public page live, one broader rollout deferred until needed.
Keep the public case page narrow, keep the referral path hidden, and send payment through the same wallet every time.
0xB3e9568A9cbB624403743340358c85CCce130893
Open Payment Page