1. Start From Activation
Visibility rules should begin from the paid referral lane that is already active, not from a fresh internal theory about delivery.
Open Partner Intro Referral ActivationClient-referral visibility page
Keep the referred deal operationally clean once the first paid step goes live.
In referral work, visibility drift is expensive. The original referrer should not quietly become an operations manager, delivery should not leak into the wrong thread, and proof should not widen before the boundary is explicit. This page keeps the first paid step clean by naming who is visible, what remains private, what can be reused later, and how the work exits into close-out.
- 1 visible operating owner
- 1 proof reuse boundary
- 0 referrer pulled into ops
Referral Visibility Map
Use one sequence from paid referral activation to protected close-out.
2. Lock The Startup Surface
Decide who sees kickoff, handoff, and intake. The buyer should not need to guess who owns the thread once work starts.
Open Partner Intro Referral Kickoff Open Partner Intro Referral Handoff3. Keep Delivery And Revision Inside One Boundary
Shipping and one bounded revision should not silently widen the audience or drag the original referrer back into operations.
Open Partner Intro Referral Delivery Open Partner Intro Referral Revision4. Separate Proof Approval From Proof Reuse
A shipped result can be approved for the client without becoming immediately reusable in public or partner-facing material.
Open Partner Intro Referral Proof Pack Open Partner Intro Referral Proof Capture5. Freeze The Close-Out Boundary
Balance collection, recovery, and final handoff should preserve the same visible owner and privacy line through the end of this cycle.
Open Partner Intro Referral Balance Open Partner Intro Referral Final Handoff Open Partner Intro Referral Recovery6. Expand Only After This Cycle Is Closed
If the work should widen into repeat or expansion, do it after the current referral lane is closed and proof boundaries are explicit.
Open Partner Intro Referral ExpansionVisibility States
Most referral execution boundaries fit one of these patterns.
Buyer Direct, Referrer Quiet
Best when the referral did its job and the buyer now needs a direct operating owner without extra routing noise.
Shared Startup, Private Delivery
Best when kickoff benefits from shared context but live execution should narrow to the actual operator and buyer.
Delivery Visible, Proof Private
Best when the client wants transparency during the first step but proof reuse still needs explicit permission later.
Partner-Safe Summary Only
Best when the work is successful but the only reusable output is a bounded summary without sensitive context or economics.
Close-Out Before Expansion
Best when more work is likely, but the current cycle still needs balance, proof, and final boundary closure first.
Short Lines
Use short language that keeps referral delivery clean.
Owner Line
From here, one operating owner should stay visible so the thread does not drift between buyer, referrer, and delivery.
Referrer Line
The referral opened the lane, but the referrer does not need to sit inside delivery unless a specific issue calls for it.
Proof Line
Approval for this result is not the same thing as permission to reuse it publicly or in partner-facing material.
Close-Out Line
Before this cycle ends, I want the same visibility boundary to hold through balance, proof capture, and final handoff.
Best Next Routes
Go to the page that removes the current referral visibility blocker fastest.
Need Startup Boundary First
If the work is paid but the startup lane is still fuzzy, tighten kickoff and handoff first.
Open Partner Intro Referral Kickoff Open Partner Intro Referral HandoffNeed Delivery Boundary First
If the first step is already live and the main risk is who sees what during execution, route into delivery and revision.
Open Partner Intro Referral Delivery Open Partner Intro Referral RevisionNeed Proof Boundary First
If the result is accepted but proof reuse is unclear, tighten the proof path before making it wider.
Open Partner Intro Referral Proof Pack Open Partner Intro Referral Proof CaptureNeed Close-Out Boundary First
If balance, recovery, or the final owner packet risks drifting the boundary, compress the close-out path next.
Open Partner Intro Referral Balance Open Partner Intro Referral Final HandoffNeed Payment Route Visible
If the commercial boundary still is not fully settled, keep the payment route explicit alongside the operating lane.
Open Payment Page