Referral Payout
Simple referral deals should usually pay from the first cleared sprint payment, not from vague pipeline promises.
Open Referral BoardPartner settlement page
Make payout timing, settlement proof, and repeat-channel economics explicit.
This page is for the moment when a partner already likes the model but wants clarity on what gets paid, when payout happens, how settlement is confirmed, and whether recurring work creates more upside or stops at the first deal.
- 3 main partner models
- 1 clear settlement trigger
- 1 proof of payout path
Payout Map
Use one settlement rule per partner model.
White-Label Settlement
White-label work is usually cleaner as a defined internal delivery rate that the partner pays against, while the partner keeps their own client-side spread.
Open White LabelReseller Markup Logic
Reseller payout should be tied to the agreed internal base and the reseller-controlled markup, not renegotiated after the close.
Open ResellerRecurring Work Rule
Decide up front whether partner upside ends after the first paid sprint or also applies to later sprints or retainer work.
Open Retainer ConversionSettlement Proof
Confirm the amount, network or payment rail, and tx hash or transfer evidence so both sides can close the commercial loop.
Open Payment GuideNeed First Deal Live
Once the payout rule is chosen, activate the deal instead of drifting inside more abstract discussion.
Open Partner ActivationTrigger Rules
Keep the payout trigger obvious before work starts.
Client Pays Directly
If the client pays the wallet directly, partner payout should be based on the cleared incoming payment and the agreed partner rule.
Partner Collects First
If the partner invoices or collects from the client on their own side, settlement should be anchored to the agreed internal rate and not re-priced after the fact.
Recurring Work Exception
If repeat work is in play, define yes or no explicitly instead of assuming the first-deal economics will carry forward forever.
Model By Model
Match the payout math to the collaboration type.
Referral Share
Referral deals stay easiest to trust when the partner gets a fixed share on the first cleared sprint instead of open-ended percentage claims on the whole account.
White-Label Margin
White-label partners typically keep the markup they add to a defined delivery rate, so the settlement event is the internal delivery payment rather than a second revenue-share payout.
Reseller Spread
Resellers keep the difference between their client price and the known internal base, which makes the economics easier to repeat.
Retainer Or Next Cycle
If later work is included, state whether that upside is a smaller share, a one-cycle bonus, or no ongoing payout at all.
Settlement Evidence
Close the payout loop with one proof standard.
Confirm The Amount
State the project amount or internal delivery base clearly so the partner can verify what the payout is calculated from.
Confirm The Trigger
Note whether the trigger is cleared client payment, internal transfer received, or the first recurring cycle landing.
Share The Proof
A tx hash, wallet screenshot, or equivalent payment confirmation removes most payout hesitation faster than more explanation.
Archive The Rule
Keep the settlement rule in writing so repeat deals do not reopen the same negotiation every time.
Best Next Routes
Route the remaining blocker to the right page.
Need Model Choice
If the partner still needs to choose referral, white-label, or reseller, route back to the main partner board.
Open Partner BoardNeed Partner Screen
If the economics look fine but you are not sure the partner is actually worth building with, qualify them before going deeper.
Open Partner QualificationNeed Forwardable Pack
If the partner wants one page they can send internally, use the partner close pack first.
Open Partner Close PackNeed White-Label Margin
If the main question is internal delivery pricing and partner markup, route to the white-label page.
Open White LabelNeed Reseller Markup
If the partner wants to control distribution and price, route to the reseller page and lock the internal base.
Open ResellerNeed Recurring Rule
If the first deal may expand into monthly work, define the next cycle logic before the partner assumes ongoing payout rights.
Open Partner Retainer Open Retainer ConversionNeed Repeat Channel Plan
If the payout rule is clear and the next question is how to make the partnership repeatable, route to the channel repeat page.
Open Channel RepeatNeed Second Sprint Rule
If the next move is another project rather than monthly support, define the renewed scope and next-cycle economics here first.
Open Partner RenewalNeed Stage Label
If the partner is already live and you need to decide whether it is still payout pending or already ready for repeat testing, label it.
Open Partner StatusNeed Short Answers
If the same payout, ownership, and next-step questions keep repeating, route to the partner FAQ page.
Open Partner FAQNeed Objection Handling
If the settlement math is not the only problem and the partner is still resisting on control or payment friction, route here next.
Open Partner ObjectionsReady To Settle
If the model and payer are already clear, move directly into the payment page and collect the transfer proof.
Open Payment PageWallet
Preferred route: direct payment, clear rule, shared tx hash.
Keep partner settlement simple enough to repeat. Confirm the partner model, confirm the payout rule, send the transfer, then share the proof so the next deal becomes easier.
0xB3e9568A9cbB624403743340358c85CCce130893
Open Payment Page