SF

Signal Foundry

Revenue Partner Intro Referral Expansion Board
Command Center Partner Intro Referral Proof Capture Partner Intro Referral Partner Intro Referral Forward Partner Intro Referral Repeat Partner Intro Referral Renewal Partner Intro Referral Retainer Conversion Partner Intro Referral Retainer Partner Intro Referral Reuse Boundary Partner Intro Referral Visibility Partner Expansion Payment

Referral post-win page

After one referral win closes, choose one next revenue motion instead of blending three asks together.

Referral momentum gets wasted when a closed win turns into mixed signals: the current buyer might know one more fit, the original partner might know similar accounts, the same buyer may have a new bottleneck, or the account may now fit recurring support. This page keeps the decision clean: one finished referral cycle, one next motion, one explicit commercial route.

  • 4 post-win motions
  • 1 next move at a time
  • 0 scope blending tolerated

Referral Expansion Map

Use one sequence from closed referral win to the next revenue step.

2. Decide Where The Next Value Actually Repeats

The main fork is simple: same buyer again, a current-buyer referral, more similar buyers through the original partner, or a recurring support pattern around the same account.

Open Partner Intro Referral Visibility

5. Use Renewal For A Fresh Same-Buyer Sprint

If the same buyer now has one new project-shaped bottleneck, keep it separate as a fresh sprint with fresh approval and payment proof.

Open Partner Intro Referral Renewal

Best Next Motions

Choose the route that matches what the closed referral win actually proved.

Client-Sourced Intro

Best when the current buyer can think of one more operator with the same bottleneck and the proof line is easy to forward.

Partner-Sourced Intro

Best when the original partner now sees a repeatable buyer pattern and can forward one safe result line quickly.

Second Sprint

Best when the same buyer now has one next bottleneck that still looks project-shaped rather than ongoing.

Monthly Support

Best when the shipped system now needs upkeep, review, or small recurring improvements around the same account.

Proof-First Pause

Best when the next ask is blocked by unclear proof or a still messy reuse boundary that needs to be tightened first.

Not All At Once

The fastest way to lose referral momentum is to mix renewal talk, repeat intros, and retainer framing inside one blurred thread.

Short Lines

Use language that keeps the next ask narrow after a closed referral win.

Choice Line

The next move is to choose one post-win path, not quietly expand this into several jobs at once.

Client Referral Line

If the current buyer knows one more fit, a single referral ask is cleaner than a broad share request.

Partner Forward Line

If the original partner can see more accounts like this one, one more aligned intro is a better ask than vague future business.

Renewal Line

If the same buyer has one fresh bottleneck, the clean route is a separate second sprint rather than stretching the old one.

Retainer Line

If the value now repeats monthly, it is cleaner to package a recurring rhythm than to keep selling small one-offs forever.

Boundary Line

Before the next ask grows, lock what stays private about the referrer, the buyer, and the closed deal mechanics.

Best Next Routes

Route to the page that matches the actual post-win condition.

Need Current-Buyer Referral

If the current buyer can introduce one more person with the same bottleneck, route into the referral page next.

Open Partner Intro Referral

Need Broader Partner Expansion

If the question is bigger than the referral lane itself, step back to the generic partner expansion page.

Open Partner Expansion

Wallet

Preferred route: closed referral win, one next motion, one clean payment path.

Once the next motion is chosen, keep the commercial step explicit: fresh scope for renewal, fresh monthly framing for retainer, or a fresh intro packet for the next buyer.

0xB3e9568A9cbB624403743340358c85CCce130893 Open Payment Page