1. Confirm Relationship Owner
Decide whether the partner keeps the client-facing role, whether there is a shared channel, or whether the client now speaks directly.
Partner execution handoff page
Move the partner deal into execution without commercial drift.
A partner deal often breaks at the moment when the intro is made, the payer is known, but nobody has cleanly handed over the buyer context, links, owner, and transfer proof. This page turns that messy moment into a repeatable operating handoff.
- 1 buyer owner named
- 1 payer and hash confirmed
- 1 minimum context package
Partner Handoff Map
Use one path from partner introduction to live kickoff.
2. Confirm The Payer
Name whether the direct client pays, the partner pays, or the partner wraps delivery inside their own billing.
Open Partner Activation3. Share The Context Packet
Send the bottleneck, desired outcome, links, approver, and any screenshots or notes that prevent re-explaining the whole deal.
Open Intake Board4. Share The Payment Proof
If funds already moved, include the tx hash or equivalent payment confirmation inside the handoff packet.
Open Partner Payout5. Choose The Kickoff Route
Decide whether the work is clear enough for a light intake or whether a fuller kickoff note is still required.
Open Kickoff Board Open Intake BoardBy Model
The handoff changes slightly depending on the partner model.
Referral Handoff
Keep it light: partner introduces the buyer, states the bottleneck, and leaves a simple payout rule in the background.
Open Referral BoardWhite-Label Handoff
Keep the brand and client control with the partner, but make the delivery context explicit enough that work can begin cleanly.
Open White LabelReseller Handoff
Confirm what the reseller controls, what the internal delivery base is, and how much direct client visibility exists.
Open ResellerOperator Handoff
If an operator is steering the project, the handoff should name who approves, who gives assets, and where the real bottleneck sits.
Open Founder OperatorMinimum Packet
Use one compact package instead of scattered context.
Buyer Owner
Name who owns the relationship now: partner, shared contact, or direct client route.
Main Bottleneck
State the one issue to fix first so the sprint does not inherit five competing problems on day one.
Desired Outcome
State what should improve first: response speed, intake clarity, payment path, close path, or another narrow result.
Relevant Links
Send the pages, docs, screenshots, and assets that make the current commercial path understandable.
Payer And Proof
If funds have moved, include the tx hash. If not, name the payer so the transfer route is not ambiguous later.
Approver
Name the person who can answer questions and approve the work so the handoff does not stall midstream.
Do Not Do This
Most partner handoff problems are avoidable.
Do Not Dump Raw Chat Logs
Summarize the buyer situation instead of forwarding long message threads and expecting someone else to reconstruct the deal.
Do Not Blur Ownership
If nobody knows whether the partner or the client is driving the project, the work will drift before kickoff.
Do Not Over-Collect
Use the minimum context needed to start. Do not turn a qualified paid deal into a new discovery maze.
Do Not Skip Payment Proof
If the transfer already happened, attach the hash so commercial uncertainty does not spill into execution.
Best Next Routes
Route the blocker to the right next page.
Need Stage Label
If the partner is already moving but you need one lifecycle label, use partner status first.
Open Partner StatusNeed Practical Answers
If the same ownership, payout, or handoff questions keep looping, answer them once with the partner FAQ page.
Open Partner FAQNeed Resistance Handling
If the handoff is blocked by client-control or payout concerns, handle the objection directly before forcing delivery forward.
Open Partner ObjectionsNeed Activation First
If the payer and model are not even confirmed yet, route back to activation before trying to hand off execution.
Open Partner ActivationNeed Payment Proof
If the handoff is blocked by settlement questions, route to partner payout and close the loop there.
Open Partner PayoutNeed Post-Win Expansion
If the first cycle is already landing cleanly and the next job is choosing the follow-on revenue motion, route here next.
Open Partner ExpansionNeed Approved Proof
If the handoff is clean and the next job is turning the result into safe reusable proof, route here next.
Open Partner Proof CaptureNeed One More Warm Intro
If the first cycle is landing cleanly and the next goal is one more aligned introduction, route to the referral-forward page.
Open Partner Referral ForwardNeed Kickoff Path
If the context is already clear, move into kickoff instead of reopening the commercial discussion.
Open Kickoff BoardNeed Minimal Inputs
If the sprint is already well-defined, use the intake board and collect only the minimum package.
Open Intake BoardNeed Repeat Channel Logic
If this handoff pattern may happen again, route to the repeat channel page and standardize the motion.
Open Channel RepeatWallet
Preferred route: transfer, context packet, then kickoff.
If payment is already part of the handoff, include the tx hash in the same packet so the sprint can move without extra drift.
0xB3e9568A9cbB624403743340358c85CCce130893
Open Payment Page