1. Confirm It Reached The Right Approver
The first question is not whether they liked it. The first question is whether the approval pack reached the actual founder, operator, or finance owner.
Open Partner Intro Referral Approval PackClient-referral approval nudge page
When the referral approval pack was forwarded but no internal decision came back, use one short nudge.
This page is for the gap after a client-referred lead forwards the first paid step internally and the decision stalls. Do not resend the whole referral story. Use one compact follow-up to confirm the real approver, isolate the blocker, tighten the scope if needed, and collapse the next yes into payment, while keeping the original referrer out of internal decision ops.
- 1 decision owner named
- 1 blocker isolated
- 1 next move made explicit
Approval Follow-Up Map
Use one sequence from internal silence to an explicit next decision.
2. Restate The Smallest Paid Step
If the internal team stalled because the first scope still felt too broad, compress it again before asking for a decision.
Open Partner Intro Referral Scope3. Ask For The Exact Blocker
Get the decision path out of abstraction. Is the blocker scope, timing, wallet confidence, budget owner, or approval authority?
Open Partner Intro Referral Close Pack4. Route The Blocker To One Page
If the issue is post-approval payer routing, move into approval-to-payment. If the issue is commitment timing, use the deposit lock page.
Open Partner Intro Referral Approval To Payment Open Partner Intro Referral Deposit Lock5. Collapse Yes Into Transfer
Once the decision is positive, the next message should already point to payment, tx proof, and the start path.
Open Payment Page Open Partner Intro Referral Activation6. Keep The Referrer Out Of The Internal Loop
The original buyer should not have to referee internal budget or approval questions unless they explicitly offer to re-anchor trust.
Open Partner Intro Referral ConversionCommon Approval Stalls
Most internal delays after a client referral come from one of these leaks.
No Clear Approver
The buyer contact forwarded something, but it is still unclear who actually decides on the first paid step.
Scope Still Feels Wide
The internal team may like the idea but still fear the first step is doing too much at once.
Commercial Path Is Fuzzy
Sometimes the yes is real in principle, but payment owner, wallet route, or timing still feels unresolved.
Generic Check-In Loops
A weak follow-up that asks for vague thoughts usually creates more delay instead of extracting the actual blocker.
Referrer Pulled Back In
The original buyer gets dragged into internal clarification work that should now sit in the direct deal thread.
Short Nudge Lines
Use direct lines that surface the decision path without sounding soft.
Owner Line
I mainly want to confirm whether this already reached the person who can approve the first paid step internally.
Blocker Line
If the scope is directionally right but one thing is still blocking approval, the fastest move is to name that blocker directly.
Scope Line
If the first step still feels too broad, we can keep it tighter around the main bottleneck rather than reopening everything.
Decision Line
The current choice is simply whether this narrow first step is the right paid move now, not whether to start a wider program.
Move Line
If internal approval is already there, the next step is payment and kickoff routing, not more internal narration.
Do Not Do This
Most referral approval follow-ups fail because they add noise instead of clarity.
Do Not Ask For Generic Thoughts
Ask for the blocker or decision owner. Open-ended check-ins make it easier to ignore the thread.
Do Not Resend The Entire Thread
The approver needs one crisp decision path, not the whole referral backstory.
Do Not Pull The Referrer Back In By Default
The original buyer should not become the ongoing internal closer unless truly necessary.
Do Not Widen Scope Mid-Follow-Up
If the first step feels too broad, make it smaller. Do not make it larger to sound more complete.
Do Not Win Approval And Reopen Payment
The next route after yes should already be explicit while the thread is warm.
Best Next Routes
Route the deal to the page that removes the next approval blocker fastest.
Need A Cleaner Approval Pack
If the forward itself is weak, tighten the referral approval pack before nudging again.
Open Partner Intro Referral Approval PackNeed Scope First
If the real stall is that the first step still feels wide, go to scope.
Open Partner Intro Referral ScopeNeed To Hand The Yes To Payer
If approval is effectively done and the next job is transfer, move to approval-to-payment next.
Open Partner Intro Referral Approval To PaymentNeed Post-Agreement Payment Rescue
If the deal is approved but the transfer still has not happened, use payment follow-up.
Open Partner Intro Referral Payment Follow-UpNeed Generic Warm-Intro Path
If the deal is becoming more complex than a straightforward client referral, step back into the broader approval follow-up page.
Open Partner Intro Referral Approval Follow-UpNeed Buyer Re-Anchor First
If approval stalled because the direct thread lost momentum, step back into referral follow-up before chasing internal answers.
Open Partner Intro Referral Follow-UpWallet
Preferred route: one approval nudge sent, one internal blocker named, one payment path already waiting.
Client-referred warm deals recover best when the approval follow-up stays narrow, the approver path is explicit, and the thread already points to the same wallet-backed payment route once yes lands.
0xB3e9568A9cbB624403743340358c85CCce130893
Open Payment Page