glossary Tracking + follow-up Diagnostic Review · Internal Revenue Audit

Internal Verification

Internal verification is the step where a visible signal is checked against the operator's internal systems before any financial claim is made. CRM, ad accounts, analytics, call records, and server-side events are the most common verification sources. Internal verification is what turns a [REQUIRES ACCESS] finding into a verified leak.

group · Tracking + follow-up scope · entity layer type · DefinedTerm

Definition

The procedural bridge between a public-signal diagnostic and a paid engagement. Internal verification turns suggestion into evidence and protects both sides from acting on noise.

Why it matters

It is the difference between "your booking flow might be losing X" and "your booking flow lost Y verified bookings in the last 90 days." Only the second supports a paid scope.

Explore related entities

  • Public Signal Any observation about a business that is visible without internal access — ad creative, website behaviour, booking flow shape, pixels, reviews, search presence, content cadence.
  • Claim/Evidence Block A finding shape used across Revenue Scan, audit, and reports: a one-sentence claim, the public-visible evidence rows that support it, and the explicit limit on the claim.
  • Diagnostic Review A 60-minute call after the Revenue Scan that maps visible signals against the business's internal data and decides whether to move into a paid audit.
  • Internal Revenue Audit A paid, fixed-scope audit of the verified leaks identified during the Revenue Scan and Diagnostic Review. Produces a prioritized leak list with internal data behind every claim.
[CLAIM BOUNDARY] Internal verification is the operator's data, not OmniLabs's. Findings stay confidential, and verification only happens under explicit scope.
See the offer ladder Back to Tracking + follow-up