1. Keep The Paid Step Fixed
Delivery should still point back to the referral brief and kickoff packet so nobody quietly widens the work once execution begins.
Open Partner Intro Referral Brief Open Partner Intro Referral KickoffClient-referral delivery page
After referral kickoff is clean, ship one narrow paid step without dragging the referrer back into execution.
This page is for the live execution stage after referral kickoff. The payment proof, owner, and startup packet already exist. The job now is to ship the agreed first step fast, keep the referrer boundary explicit, handle one light revision without widening scope, and route the finished work into proof, balance collection, and handoff without adding another sales loop.
- 1 paid first step shipped
- 1 referrer boundary preserved
- 1 light revision window
Referral Delivery Map
Use one sequence from referral kickoff packet to finished first-step delivery.
2. Preserve Owner And Referrer Boundary
Keep it explicit who answers fast questions and whether the original buyer stays visible, becomes optional, or is fully out while the work is live.
Open Partner Intro Referral Visibility Open Partner Intro Referral Handoff3. Ship Only The First-Step Assets
Deliver only the pages, flows, summaries, or SOP material that belong to this first paid step, not the referred buyer's full backlog.
Open Delivery Board4. Handle Light Revision Without Drift
Tighten tone, CTA, or structure if needed, but treat new flows, extra pages, or another bottleneck as new scope.
Open Partner Intro Referral Revision5. Summarize The Win For Proof
Once the first step is shipped, compress the before-after story into a concise proof pack the buyer and partner can approve fast.
Open Partner Intro Referral Proof Pack Open Partner Intro Referral Proof Capture6. Close Into Balance And Handoff
After approval, collect the remaining balance if relevant and hand over the final owner-facing materials in one clean packet.
Open Partner Intro Referral Balance Open Partner Intro Referral Final HandoffWhat Usually Ships
These are the referral-delivery assets that most often matter in the first paid step.
Buyer-Facing Asset
One page, message path, or handoff structure that removes the highest-friction buyer bottleneck first.
Referrer-Safe Boundary Note
One explicit note on whether the original buyer stays visible, becomes optional, or steps out while delivery runs.
Owner SOP
One short operating note so the person running the thread can use the shipped asset without guesswork.
Approval Summary
One concise explanation of what shipped, what changed, and what the approver should confirm next.
Proof-Safe Snippet
One summary that can become reusable proof if the buyer or partner approves it without breaking trust.
Final Handoff Packet
One clean packet of links, notes, and next-step rules so the work can be used after the sprint ends.
Revision Boundary
Use revisions to tighten the referral first step, not to invent a second one.
Within Scope
Wording changes, CTA tightening, structural cleanup, and small clarifications inside the delivered step are normal.
New Scope
Additional flows, unrelated pages, another bottleneck, or a new stakeholder workflow should be treated as a separate decision.
Referrer-Side Risk
If a revision changes whether the original buyer stays visible, that is not a minor edit. Reconfirm the boundary before changing it.
Approval Logic
Tie revision handling to one clear approver so delivery does not stall in multi-person silence.
Short Delivery Lines
Use direct lines that keep the referral first step moving.
Scope Line
I am keeping delivery tied to the exact first paid step already approved so the work stays fast and easy to approve.
Boundary Line
Before I ship this, I want to keep the referrer boundary explicit so nothing shifts accidentally back through the original buyer.
Revision Line
Small tightening is fine inside this step. Anything that adds a second workflow or wider rebuild should be treated separately.
Proof Line
Once this is shipped, I will compress it into one short summary so approval, proof, and handoff stay clean.
Best Next Routes
Route to the page that removes the last referral-delivery blocker fastest.
Need Deeper Brief First
If constraints or stakeholder reality are still fuzzy, route back to the referral brief before pushing delivery further.
Open Partner Intro Referral BriefNeed Kickoff Packet First
If the owner, links, and startup packet are not yet clean, route back to the referral kickoff page first.
Open Partner Intro Referral KickoffNeed Generic Delivery Rules
If the project is no longer referral-specific, switch to the broader delivery board for the generic sprint rules.
Open Delivery BoardNeed Proof Summary
If the work is shipped and the next concern is approval proof, route into the intro proof pack.
Open Partner Intro Referral Proof PackNeed Revision Boundary
If one small in-scope tightening still matters before approval, route into the intro revision page next.
Open Partner Intro Referral RevisionNeed Partner-Safe Proof
If the work landed and you want reusable proof without breaking white-label trust, route to partner proof capture.
Open Partner Intro Referral Proof CaptureWallet
Preferred route: proof attached, kickoff clean, first step shipped, close-out started.
Keep the same wallet-backed commercial trail attached to execution. Once the referral first step is shipped, move directly into proof, balance, and handoff instead of letting delivery sprawl.
0xB3e9568A9cbB624403743340358c85CCce130893
Open Payment Page