1. Keep Payment Proof Attached
Intake should stay tied to the verified transfer so startup never detaches from the commercial proof.
Open Partner Intro Referral Payment ProofClient-referral intake page
After referral handoff is clean, collect only the minimum startup inputs that keep the paid first step moving.
This page is for the moment after payment proof, owner, and the referrer boundary are already clear. The remaining risk is loose startup intake. Keep the paid first step visible, ask only for the bottleneck, desired outcome, relevant links, and decision owner, then route into a fuller brief only if the first step genuinely needs it.
- 6 minimum inputs
- 1 owner and boundary visible
- 0 rediscovery loops needed
Referral Intake Map
Use one sequence from clean referral handoff packet to a start-ready intake.
2. Reuse The Handoff Decisions
Owner, visibility, and the referrer boundary should already be decided before intake starts collecting project inputs.
Open Partner Intro Referral Handoff Open Partner Intro Referral Model3. Capture The Main Bottleneck
Ask for the one bottleneck this first paid step is supposed to remove before optional ideas start widening the work.
4. Capture The Desired Outcome
Define the first visible shift the buyer wants from this step so execution has a concrete operating target.
5. Collect Only Relevant Links
Ask for only the pages, docs, screenshots, and assets needed for this first step instead of every artifact in the account.
6. Choose Brief Depth Intentionally
If the first step is obvious, move into referral kickoff. If constraints, stakeholders, or dependencies are still fuzzy, escalate to a fuller brief once.
Open Partner Intro Referral Brief Open Partner Intro Referral KickoffMinimum Inputs
These are usually enough to start a paid referred first step cleanly.
Tx Hash
Keep the confirmed transfer attached to intake so the startup packet always points back to a real paid event.
Approved First Step
Name the exact first step that was bought so intake does not quietly mutate into a wider discovery project.
Main Bottleneck
Ask for the single visible problem that should improve first once work starts.
Desired Outcome
Describe the concrete shift the buyer wants from this first step, not a generic long-term vision statement.
Relevant Links
Capture only the assets that help execute this paid step now: live pages, docs, screenshots, repos, or recordings.
Decision Owner And Boundary
Keep one person accountable for quick answers and make it clear whether replies stay direct, shared, or visible to the referrer.
Copyable Intake
Send this when the referred buyer asks what you need next.
|
Partner Intro Referral Intake
1. tx hash or receipt link 2. the exact first paid step we are starting with 3. the main bottleneck to remove first 4. the concrete outcome you want from this step 5. only the links, docs, screenshots, or assets needed now 6. who owns questions and whether the original referrer stays visible |
Escalation Rules
Use more depth only when the first step actually needs it.
Use Referral Intake
Use this page when payment, owner, and the referrer boundary are already clear and the remaining job is the lightest startup packet.
Use Intro Brief
Route to the intro brief page when stakeholders, dependencies, or delivery constraints genuinely need one deeper pass.
Open Partner Intro Referral BriefUse Generic Intake
If the project is no longer client-referral specific, switch to the broader intake page instead of carrying referral logic.
Open Intake BoardUse Intro Model
If owner, payer, or visibility is still fuzzy, solve that first so intake does not try to compensate for a messy handoff.
Open Partner Intro Referral ModelUse Referral Kickoff
Once the inputs are gathered, route directly into the referral kickoff path instead of creating another admin layer.
Open Partner Intro Referral KickoffUse Referral Activation
If the blocker is still commercial status, payout logic, or live operating control, move back into referral activation first.
Open Partner Intro Referral ActivationDo Not Do This
Most referral intake drag comes from collecting the wrong kind of detail.
Do Not Restart Discovery
The buyer already bought a narrow first step. Intake should not become a fresh strategy workshop.
Do Not Ask For Every Asset
Pull only the material needed for this step or the intake packet becomes another sorting problem.
Do Not Lose The Paid Scope
Keep the approved first step visible inside intake so kickoff does not expand into adjacent work by accident.
Do Not Blur Owner And Referrer Boundary
If nobody knows who answers or whether the original buyer stays visible, intake will not save the start from drift.
Best Next Routes
Route to the page that removes the last startup blocker fastest.
Need Payment Proof First
If the transfer still is not verifiable, close the proof loop before gathering startup inputs.
Open Partner Intro Referral Payment ProofNeed Handoff Packet First
If owner, visibility, or the referrer boundary is still fuzzy, route back to the referral handoff page first.
Open Partner Intro Referral HandoffNeed Generic Intake
If this is not really a client-referral workflow anymore, switch to the broader intake board for the minimum generic input set.
Open Intake BoardNeed Fuller Brief
If delivery complexity is still too high for minimum intake, run one fuller brief pass before kickoff.
Open Partner Intro Referral BriefReady For Referral Start
If the inputs are gathered and the paid step is still tight, move directly into the referral kickoff route now.
Open Partner Intro Referral KickoffNeed Broader Partner Control
If the real blocker is activation status or the wider partner operating model, route into the broader partner system.
Open Partner Intro Referral Activation Open Partner Intro Referral ModelWallet
Preferred route: proof attached, owner fixed, intake compressed, kickoff started.
Keep the same wallet-backed commercial trail tied to intake. Once the proof, owner, and minimum inputs are visible, route the referred deal straight into execution.
0xB3e9568A9cbB624403743340358c85CCce130893
Open Payment Page