Signal Foundry
Revenue Partner Intro Referral Reuse Boundary BoardClient-referral proof rights page
Referral proof becomes risky at the exact moment it becomes useful. A closed first step created a result line, a quote, or a compact proof pack, and now people want to reuse it in more places. This page freezes the boundary first: what stays private, what can help future referral packets, what can support repeat work, and what still cannot travel publicly without a fresh explicit decision.
Referral Reuse Map
Begin with the real referral asset already in hand: one result line, one proof pack summary, one quote, or one captured proof item.
Open Partner Intro Referral Proof Pack Open Partner Intro Referral Proof CaptureReuse should inherit the referral visibility rule. Keep the original referrer, buyer identity, and hidden operating details protected first.
Open Partner Intro Referral Visibility Open Partner Intro Referral Final HandoffDecide whether the asset stays private, becomes referral-pack-safe, supports repeat work, or waits for a later broader review.
Open Partner Intro Referral Pack Open Partner Intro Referral Repeat Open Partner Intro Referral ExpansionFreeze what cannot travel with the asset: client names, raw screenshots, hidden economics, and any detail that exposes the referrer.
Open Partner Intro Referral Messages Open Partner Intro Referral Close PackA proof line that helps one repeat lane or renewal conversation should still be reviewed again before it becomes broader proof.
Open Partner Intro Referral Renewal Open Partner Intro Referral Retainer ConversionProof reuse should help the next referral sale, not create confusion about what has already been paid for in this cycle.
Open Payment PageReuse Classes
The asset helps the current owner and buyer, but it should not travel beyond this closed referral cycle.
The asset can support a future referral packet if names, screenshots, and hidden economics stay out.
The asset can help the next similar buyer without becoming a broad public claim or website proof block.
The asset may help a second sprint or retainer discussion, but the boundary should be reviewed again for the new paid step.
The result may be strong, but it still is not cleared for open public proof or wider case-study packaging.
Short Lines
This result is useful, but I want to keep the referral reuse boundary explicit before it travels any further.
Approval of this work helps the current deal, but it does not automatically create wider testimonial or public proof rights.
For now this can help a repeat referral packet, but it should not drift into broader public proof without a fresh decision.
If we want to use this again for renewal, expansion, or a new lane, we should review the boundary again at that point.
Best Next Routes
If the result exists but the reusable proof asset still is not cleanly documented, capture it before discussing reuse.
Open Partner Intro Referral Proof CaptureIf the immediate job is helping the next referral conversation, tighten the proof pack or referral pack first.
Open Partner Intro Referral Proof Pack Open Partner Intro Referral PackIf the same proof should support another similar referral, route into repeat or expansion next.
Open Partner Intro Referral Repeat Open Partner Intro Referral ExpansionIf the proof should support a renewal or retainer conversion, attach it to the new paid step rather than broadening it abstractly.
Open Partner Intro Referral Renewal Open Partner Intro Referral Retainer Conversion