public recovered revenue
No pilot has produced a public, owner-approved recovered-revenue receipt yet. Until that changes, this stays zero.
Proof ledger
Receipts before claims.
This is the public bridge between the RelayLaunch promise and the owner dashboard. It shows what is measured, what is projected, what is prepared for approval, and what Relay held back.
Four states
Every proof item has to name its state.
The product gets stronger when the proof grammar is visible. A projected example is useful, but it is not a measured result. A blocked send is valuable, but it is not revenue.
sample recovery ranges
Sample briefs and calculators can show projected ranges, but they are labeled before they are treated as proof.
actions staged for approval
Relay can prepare follow-ups, slot rescue, and review prompts, but owner approval remains the line before contact.
unsafe or unready work refused
Blocked events are receipts that Relay protected the owner. They never count as wins, recovered dollars, or billable proof.
Brake Receipts
The moat is not just what the AI did. It is what it refused to do.
RelayLaunch treats a held-back action as a trust receipt. If a message lacks consent, sender readiness, owner approval, or policy confidence, the system records the brake instead of pretending silence is success.
Held back
Customer contact refused
Reason class: consent gate. Source: owner approval workflow. Outcome impact: none. Billing impact: none.
Public to private bridge
The website explains the rule. Relay Deck shows the receipts.
Public pages can explain the proof model. Signed-in owners see the tenant ledger in Relay Deck, including approvals, held-back actions, and outcome receipts when real outcomes exist.