1. Keep The Paid Step Fixed
Start by anchoring the kickoff to the exact first paid step that was approved and paid. Do not let startup reopen scope.
Open Partner Intro Referral Payment ProofClient-referral startup page
After referral payment proof is attached, compress the referred deal into one clean kickoff packet.
This page is for the moment after the deposit is real and the commercial side is effectively closed. The goal now is to stop context drift: confirm who owns the thread, keep the approved first step fixed, send the minimum brief and links, and move into a live start without dragging the original referrer back into startup ops.
- 1 owner named
- 1 minimum startup packet
- 0 commercial drift tolerated
Referral Kickoff Map
Use one sequence from confirmed referral payment proof to live work.
2. Name The Direct Owner
Confirm who will answer questions, approve details, and carry the thread so the kickoff does not scatter across multiple people.
Open Partner Intro Referral Activation3. Keep The Referrer Out Of Startup Ops
The original buyer opened the door. They should not become the default traffic manager for assets, questions, and next steps.
Open Partner Intro Referral Close Pack Open Partner Intro Referral Visibility4. Send The Minimum Packet
The strongest referral starts usually need only the tx hash, the main bottleneck, the desired outcome, and the relevant links.
Open Partner Intro Referral Intake5. Choose Brief Depth Deliberately
Use the short intake path if the scope is already obvious. Use a fuller brief only when it meaningfully reduces delivery risk.
Open Partner Intro Referral Brief6. Confirm The Start Path
Once owner, proof, and the minimum context are in, move into the same delivery lane immediately instead of building another admin stage.
Open Partner Intro Referral Delivery Open Partner Intro Referral ActivationMinimum Packet
This is usually enough to start a referred first step cleanly.
Payment Proof
Keep the tx hash attached to the startup packet so commercial confirmation never detaches from execution.
Main Bottleneck
Name the one visible problem the first paid step is supposed to solve before optional ideas start leaking in.
Desired Outcome
State the outcome in practical terms so the kickoff packet is not just a stack of assets with no operating aim.
Relevant Links
Send only the links needed to execute the first step, not a pile of every page the buyer has touched so far.
Decision Owner
Name the person who can answer questions fast enough to keep the kickoff from stalling in silence.
Brief Depth
Decide whether the intake path is enough or whether the brief really needs one deeper pass before work starts.
Short Start Lines
Use direct lines that turn the paid referred deal into a clean start.
Owner Line
Since payment is already confirmed, the main thing I need now is the person who will own questions and approvals during the first step.
Packet Line
The fastest start is the tx hash, the main bottleneck, the desired outcome, and the links that matter for this first step.
Boundary Line
The original referrer does not need to stay in the middle of the startup thread unless they explicitly want visibility.
Scope Line
Kickoff should stay tied to the first paid step already bought, not quietly expand into adjacent work.
Move Line
Once the startup packet is in, the next move is execution, not another round of commercial explanation.
Do Not Do This
Most referred starts slow down because too much gets added after payment.
Do Not Reopen Scope
The paid first step should not become vague again just because the deal has moved into startup.
Do Not Over-Collect
Asking for every possible asset and answer before beginning often creates a fake discovery phase that the buyer did not buy.
Do Not Leave Owner Unclear
Referral kickoffs drift quickly when nobody knows who can make the next small decision.
Do Not Put The Referrer Back Into Startup Ops
The original buyer is not the default startup coordinator just because they made the intro.
Do Not Separate Payment From Start
The proof of payment should remain attached to the startup path so the deal does not split into commercial and delivery threads.
Best Next Routes
Route to the page that resolves the remaining startup blocker fastest.
Need Payment Proof First
If the transfer is not fully attached yet, close the referral proof loop before trying to start.
Open Partner Intro Referral Payment ProofNeed Owner And Context Packet
If the startup is blocked by ownership, visibility, or missing links, route to the intro handoff page next.
Open Partner Intro Referral HandoffNeed Minimal Intake
If the first step is already obvious and you just need the smallest usable input set, route to intake.
Open Partner Intro Referral IntakeNeed Fuller Brief
If the first step needs more structured project input before work begins, route to the intro brief page next.
Open Partner Intro Referral BriefNeed Formal Activation
If the next concern is still the commercial operating model, referral boundary, or partner-side live status, move back into activation.
Open Partner Intro Referral ActivationReady To Start
If the owner, proof, and startup packet are all clear, move directly into the intro delivery route now.
Open Partner Intro Referral DeliveryWallet
Preferred route: payment proof attached, startup packet sent, kickoff started.
Once the transfer is confirmed, keep the same commercial route intact. Attach the proof, send the minimum packet, and move the referred deal into a real start path immediately.
0xB3e9568A9cbB624403743340358c85CCce130893
Open Payment Page