Signal Foundry
Revenue Referral Public Brief BoardReferral public startup brief
Once payment is confirmed, the startup brief should stay narrow: name the current leak, the desired outcome, the most relevant links, the hard constraints, the owner, and the first execution boundary. This page keeps the kickoff packet usable without turning it into a long discovery document.
Referral Public Brief Map
Use this page only after the payment thread and kickoff path are already confirmed. If the tx hash or startup packet is still loose, stay in public payment or public kickoff first.
Open Referral Public Payment Open Referral Public Kickoff Open Kickoff BoardThe brief should start with one exact bottleneck. If the buyer lists ten ideas, compress them into the one issue the first sprint should solve.
Open Brief Board Open Intake BoardThe operator should still see the exact public asset that closed the deal, not a disconnected internal note that loses the context that made the buyer pay.
Open Referral Public Board Open Referral Public Page Open Referral Public KickoffPrivate source path, raw screenshots, internal economics, settlement details, and broader negotiation history stay out of the brief unless they are needed to ship the first sprint step.
Open Referral Public Boundary Open Proof Board Open Referral Public PayoutOnce the brief is clean, move into one exact execution surface: intake, delivery, or a live kickoff note. Do not duplicate the same brief across multiple pages at once.
Open Referral Public Intake Open Intake Board Open Delivery Board Open Kickoff BoardIf the operating thread now depends on a broader partner-facing owner path instead of one referral-led execution lane, move it deliberately into the partner public brief lane.
Open Partner Public Brief Open Partner Public KickoffBest Brief Routes
Best when one short written brief is still the missing piece before execution starts.
Best when the sprint is already clear and only the minimum intake packet is needed.
Open Referral Public IntakeBest when the startup packet is already enough and the thread should move directly into action.
Best when the brief is complete and the thread should move into execution tracking.
Brief Snapshot
| Brief Layer | Public Job | Keep Hidden | Main Destination | Review Trigger |
|---|---|---|---|---|
| Main leak | Name the first bottleneck to fix | All side ideas and future wish list | Brief Board | If the brief grows into multiple projects |
| Desired outcome | Define the first useful shift | Broad strategic speculation | Kickoff Board | If success is still vague |
| Relevant links | Collect only the links needed to ship | Unused screenshots and side channels | Referral Public Intake | If too many unrelated assets get attached |
| Owner path | Name who answers questions | Internal org drama and side approvals | Delivery Board | If no one owns the next answer |
| Transfer rule | Move only with an explicit family change | Ownership and partner source history | Partner Public Brief | When the owner path is no longer referral-led |
Pasteable Lines
Give me the one leak you want fixed first, not the full backlog of ideas.
Tell me what should improve first when this sprint is done, in one sentence.
Open Brief BoardSend only the pages, docs, and screenshots needed to execute the first step.
Open Referral Public IntakeThe brief can move forward without exposing names, margins, or the hidden referral path behind the result.
Open Referral Public BoundaryOnce the brief is clear, the next move is execution, not more onboarding ceremony.
Open Delivery BoardWallet
Use the same wallet and tx hash as the payment reference while the startup brief is being finalized.
0xB3e9568A9cbB624403743340358c85CCce130893
Open Referral Public Intake