A revenue leak is an observed condition in a public customer path that may add friction before a booking, call, inquiry, or purchase. The label identifies a risk to investigate; it does not prove that revenue was lost.
Revenue Leak
The operational definition, the public evidence boundary, and the nearby concepts an operator needs before using the term in a diagnosis.
Definition before diagnosis.
What the term can—and cannot—support.
Read the definition as a contract. It keeps a useful public observation from expanding into an outcome the scan cannot see.
- 01
Examples include an unclear primary action, missing service context, contradictory contact details, or a public booking route that cannot be reached from the inspected page. Revvye records the observable condition and the page evidence that supports it rather than inventing visitor behavior.
- 02
Establishing actual loss requires customer-owned evidence such as funnel analytics, submitted leads, completed transactions, or controlled tests. Until that evidence is connected, a Revvye finding is a prioritized public-path hypothesis with a verification step—not a causal revenue claim.
The term travels with its limit.
- 01Observe
Inspect the submitted public surface and the declarations it returns.
- 02Preserve
Keep the rule, page signal, severity, and stated limitation together.
- 03Exclude
Do not infer private revenue, conversion, delivery, or customer behavior.
Inspect the public path. Keep the private result private.
The free scan begins with the page you submit and routes its result through a private email-linked intake. It does not access private analytics or CRM data.
Public pages only. The $97 report comes after the result.