We publish
- Public-safe blocker pages, dispatches, and research summaries.
- Recurrence counts with denominators and dated publication windows.
- Redacted examples that show how the brief thinks without leaking a live company.
Confidentiality
The public site is a proof layer, not a leak path
CitrusGate is designed so a cold visitor can inspect the quality of the thinking without gaining access to private company research. This page explains where the public/private stop-line sits and why it exists.
We keep private
- Raw company notes, source bundles, and internal operator artifacts.
- Company-specific diagnosis, contact context, outreach state, and sendability logic.
- The exact intervention path or ordered fix sequence for one live team.
Why the boundary exists
- The public site proves recurrence; it does not mirror the private research workspace.
- Paid delivery happens through a protected buyer flow, not through public route reuse.
- If an insight becomes less useful after abstraction, it belongs in the private brief instead of on the site.
Cold-email trust path
The public pages are designed to make the problem legible before purchase
A cold prospect may land on a blocker page or a dispatch before they know anything about CitrusGate. The public layer therefore has to show clear judgment, explicit limits, and enough proof to justify the next click without publishing the private diagnosis.
Next Step
Inspect the proof, then decide whether the private brief is warranted
The public site should make the recurring blocker legible. The brief is where one team gets the company-specific diagnosis, the safer next move, and the false reaction to avoid.