1. Keep Proof And Scope Attached
The brief should still point back to the confirmed transfer and the exact first paid step so context never detaches from payment.
Open Partner Intro Referral Payment ProofClient-referral brief page
When minimum referral intake is not enough, run one deeper brief pass without reopening the paid first step.
This page is for the stage after payment proof, referral handoff, and referral intake are already clean. The goal is not to start discovery over. The goal is to capture the few deeper details that actually shape delivery: the main leak, desired outcome, constraints, stakeholder reality, referrer boundary, and who approves decisions once work is live.
- 7 brief items
- 1 paid first step stays fixed
- 0 reopened close tolerated
Referral Brief Map
Use one sequence from referral intake to a context-complete kickoff.
2. Reuse Handoff And Intake
Owner, visibility, bottleneck, outcome, and relevant links should already exist before the brief adds any deeper detail.
Open Partner Intro Referral Handoff Open Partner Intro Referral Intake3. Define The Current Leak Precisely
Translate the problem into the specific leak that the first step is supposed to fix first, not a general backlog of frustrations.
4. Name The Desired Shift
State the first observable improvement this work should create so the brief stays outcome-oriented.
5. Capture Constraints And Stakeholders
Record the tooling, compliance, brand, timing, and approval realities that could block delivery if they stay implicit.
6. Preserve Owner And Referrer Boundary
Keep it explicit who answers fast questions and whether the original buyer stays visible, becomes optional, or steps out.
Open Partner Intro Referral Visibility Open Partner Intro Referral Model7. Route Into Kickoff Fast
Once the deeper brief exists, stop adding admin and move into the live startup route immediately.
Open Partner Intro Referral Kickoff Open Partner Intro Referral DeliveryBrief Items
These are the deeper details that most often matter after referral intake.
Paid First Step
Keep the approved first step visible so the brief does not become an excuse to reopen scope.
Current Leak
Describe the specific operational leak the first step should reduce first.
Desired Outcome
State the measurable shift the buyer wants from this step rather than a vague long-term aspiration.
Relevant Links
Pull only the pages, docs, screenshots, recordings, or repos that explain this first step.
Constraints
Note any non-negotiable brand, timing, tooling, or compliance constraints before work begins.
Stakeholders
Name who needs visibility, who can answer quickly, and who gives final approval if revisions are needed.
Referrer Boundary
Confirm whether the original buyer stays visible, becomes optional, or steps fully out for operating speed.
Copyable Brief
Send this when the referred buyer needs one deeper context pass.
|
Partner Intro Referral Brief
1. the exact first paid step we are executing 2. the main leak or bottleneck this step should fix first 3. the concrete outcome you want from this step 4. the links, docs, screenshots, or repos that matter 5. any hard brand, tooling, timing, or compliance constraints 6. the stakeholders who need visibility or approval 7. whether the original referrer stays visible or steps out |
Do Not Do This
Most referral brief drag comes from turning one deeper pass into a second discovery cycle.
Do Not Reopen Scope
The paid first step should stay fixed while the brief adds delivery clarity.
Do Not Rebuild Intake
If the key inputs already exist, do not ask for the same packet twice.
Do Not Blur Owner
A deeper brief still fails when nobody knows who can answer the next operational question quickly.
Do Not Pull The Referrer Back In By Default
The original buyer should not become the fallback project manager just because the brief got deeper.
Do Not Delay Kickoff After Clarity
Once the deeper details are captured, move into kickoff rather than building another admin loop.
Best Next Routes
Route to the page that removes the last startup blocker fastest.
Need Referral Intake First
If the minimum inputs still are not gathered, tighten the intake before running a deeper brief pass.
Open Partner Intro Referral IntakeNeed Handoff Or Boundary First
If owner or visibility still is fuzzy, fix the referral handoff before trying to solve it inside the brief.
Open Partner Intro Referral HandoffNeed Generic Brief Instead
If the deal no longer behaves like a client-referral workflow, step back into the broader intro brief page.
Open Partner Intro Referral BriefNeed Kickoff Now
If the deeper context is already sufficient, stop briefing and move straight into the referral kickoff path.
Open Partner Intro Referral KickoffNeed Live Delivery
If the startup packet is already clean and the next job is the working lane, move into delivery now.
Open Partner Intro Referral DeliveryNeed Broader Partner Control
If the real blocker is the wider operating model or control layer, route into the broader partner system.
Open Partner Intro Referral Activation Open Partner Intro Referral ModelWallet
Preferred route: proof attached, intake done, deeper brief captured once, kickoff started.
Keep the same wallet-backed commercial trail tied to the deeper brief. Once the extra clarity is captured, route the referred deal directly into execution.
0xB3e9568A9cbB624403743340358c85CCce130893
Open Payment Page