Glossary
The glossary is the entity layer for Revenue OS, the Revenue Leak Scan, the offer ladder, and the operating boundaries production launch must hold.
The diagnostic discipline that runs from public-signal scan through the offer ladder — what every paid step verifies before it opens.
Revenue Scan
The Revenue Leak Scan is the public diagnostic front door into Revenue OS — a diagnostic review of public-visible signals across acquisition, website, conversion path, tracking, CRM expectations, content, reviews, and reactivation surfaces.
Revenue Leak
Any point in the acquisition → conversion → follow-up → retention path where addressable revenue silently degrades.
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.
Public-Signal Diagnostic
A diagnostic review that uses only publicly observable surfaces of a business — no credentials, no shared accounts, no internal data movement.
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.
Offer Ladder
The five-step Revenue OS commercial path: Revenue Scan → Diagnostic Review → Internal Revenue Audit → Revenue OS Build Sprint → Ongoing Revenue Infrastructure.
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.
Severity Frame
The Revenue Scan way of ranking findings as diagnostic priority — visible vs requires access, severity rather than financial certainty — instead of guessed revenue impact.
Revenue OS, its modules, the implementation studio that ships them, and the custom-system lane that feeds the productized portfolio.
Revenue OS
The first active commercial system in the OmniLabs Systems portfolio. Eight modules across acquisition, conversion, tracking, CRM, follow-up, content, reporting, and operations.
Revenue OS Build Sprint
A paid, scoped sprint that builds the modules verified by the audit. Each module ships as a working part of the operator's Revenue OS instance.
Ongoing Revenue Infrastructure
A retained engagement that operates, monitors, and extends the Revenue OS modules built during a Build Sprint.
Module Mapping
The Revenue OS discipline of pairing every visible scan finding with the specific module that would own the fix — acquisition, conversion, tracking, CRM, content, reporting, reactivation, operations.
System Boundary
A reserved system category in the OmniLabs Systems portfolio that has not yet been productized. Used to signal scope of work without claiming product maturity.
Implementation Studio
The delivery-side identity of OmniLabs Systems. Builds Revenue OS modules and Custom Revenue-Critical Systems against verified findings, not generic agency briefs.
Custom Revenue-Critical Systems
Premium scoped implementation lane for revenue-critical operating workflows that do not fit the standard Revenue OS module set yet. Not "we build anything."
Campaign infrastructure, creative-to-CRM execution, and the demand portfolio (capture, creation, diagnostic) that connects to the revenue path.
Acquisition & Creative Systems
Campaign infrastructure plus creative-to-CRM execution, scoped only when attached to a validated revenue system. Not a standalone ad-management service.
Campaign Infrastructure
The acquisition-side operating layer — channel setup, creative testing, audience structure, source attribution, and ad-account observability — that paid spend lives on.
Creative-to-CRM Execution
The end-to-end execution layer that takes a creative concept through testing, into the conversion path, through CRM capture, and into follow-up — all with source attribution preserved.
Demand Capture
Capturing demand that already exists for an offer — search, comparison, in-market behaviour — through SEO, GEO, direct response, and conversion-path discipline.
Demand Creation
Creating demand that did not exist by reaching out to a defined ICP through paid acquisition, outbound, and content infrastructure that supports both.
Diagnostic Demand
Demand for a diagnostic conversation about whether a business is leaking revenue — the demand a Revenue Scan exists to capture.
Conversion Path
The subset of the revenue path that runs from first landing to a captured conversion event — landing page, form, booking flow, checkout, confirmation.
Revenue Path
The end-to-end sequence a business uses to convert attention into revenue — acquisition → conversion website → tracking → CRM → follow-up → reactivation → reporting.
Source-to-revenue visibility, tracking gaps, the follow-up system that holds captured demand, and the internal verification that turns suggestion into evidence.
Tracking Gap
A missing, duplicated, or inconsistent measurement handoff that prevents an event from being reconciled across the systems expected to record it.
Source-to-Revenue Visibility
The ability to trace a real revenue event back to the source — campaign, content, channel, referral — that produced it, using internally verified data.
Follow-Up System
The owned operating layer that turns a captured inquiry into explicit record states, next actions, exceptions, and verification evidence.
Internal Verification
Verifying a public-signal finding against the operator's internal data — CRM, ad accounts, analytics, call records, server-side events — before assigning financial impact.
Operating-process boundaries that production launch must hold (intake, consent, anti-spam, retention, launch gate). Not legal advice.
Intake Boundary
The operating boundary that defines which prospect data the public intake collects, which fields it does not, and how the surface enforces both.
Consent Boundary
The operating boundary that defines what the user is consenting to when they submit the public intake, and what the surface must show before that submission.
Anti-Spam Boundary
The operating boundary that defines the minimum spam and abuse controls a production intake surface must hold before being enabled.
Data Retention Boundary
The operating boundary that defines how long prospect data is retained after intake, when it must be deleted, and who is responsible for both.
Production Launch Gate
The operating gate that production launch must clear: reviewed Privacy Policy and Terms, intake/consent/anti-spam/retention boundaries, endpoint scope, analytics disclosure, and the production-domain plan.
The failure surfaces that appear wherever revenue crosses a system boundary — a state that is never written, a queue nobody owns, a revenue event that lands long after the click. Defined once here because the industry pages describe them repeatedly and must not redefine them.
State Object Gap
A stage that exists in an operation’s real workflow but has no corresponding record, status field or queue in any system.
Write-Back Gap
The missing return path from a downstream or edge system into the system of record, so work completed outside the record leaves no trace inside it.
Shadow System of Record
A system that holds authoritative state for one stage of a revenue path while a different system is treated as the record of truth for the relationship.
Unowned Queue
A list of records a system already produces that has no assigned owner, no ageing threshold and no rule turning an entry into work.
Cross-System Identity Join
The shared key that lets a record in one system be matched to the same real-world entity in another.
Denominator Integrity
The property of a conversion metric whose denominator includes every inquiry that occurred, not only the inquiries a system of record happened to receive.
Fulfillment Event Gap
A boundary where a system records that something was authorised but never receives an event confirming whether it was fulfilled, making non-fulfillment unobservable from inside that system.
Non-Responder Escalation
An explicit post-sequence state an operator may define when a follow-up sequence completes without a recorded response.
Documented Event Surface
The set of state changes a platform publicly documents as subscribable events, which bounds what an integration can react to without polling.
Concepts for revenue that renews on a schedule or realises long after acquisition: what a failed payment does, what a cancellation records, and how a delayed revenue event is joined back to its source.
Involuntary Churn
Recurring revenue lost because a payment instrument or billing attempt failed, rather than because a customer decided to leave.
Dunning Sequence
The ordered set of retry attempts, notices and state changes a billing system runs between a failed recurring charge and a resolved or terminated subscription.
Terminal State Configuration
The setting that determines what status a record is left in when an automated sequence exhausts its attempts, and which systems are told about that status.
Cancellation Reason Code
A required, enumerated field captured at the moment an account is cancelled, recording the stated cause as a value a report can group.
Route Density
How tightly recurring service stops cluster in geography and cycle, which sets what it actually costs to deliver a given recurring customer.
Unredeemed Balance
Value a customer has already paid for and not yet consumed, held as a balance in one system while the billing that created it runs in another.
Delayed Revenue Event
A revenue event that occurs so long after the acquisition event, and across so many record boundaries, that no advertising platform can observe it.
Offline Conversion Import
Importing a downstream event that occurred away from the advertising surface so it can be associated with an earlier ad interaction when supported identifiers or user-provided data are available.
Modeled Conversion
A conversion estimated by a measurement platform where an observable link between an ad interaction and a conversion is unavailable.
Referral Revenue Ledger
A system of record for work sent outside the business, holding the counterparty, the expected fee, the status and the aging clock.
Pre-Publication Review Gate
A control that requires a public asset to be reviewed, approved and retained as a specific artefact before it may be served.
A definition is where the work starts, not where it ends
Most entries here are short on purpose: they fix a term so the rest of the estate can use it without re-arguing it. A few are worked in full, with the checks you would run to find the thing in your own system — terminal state configuration and the unowned queue are two of them.
If naming the pattern is not the hard part, and deciding what to repair first is, a Diagnostic Review is a live working session over your own system — not a form, and not a report you wait for.
Book a Diagnostic Review