Revenue systems, by industry
The same diagnostic question — where does demand stop becoming revenue — has a different answer in every operating model, because the systems that hold the truth are different. These pages map that: how revenue is made, which system owns each handoff, where the structural leaks sit, and what evidence would confirm one.
Demand arrives as a call or an appointment request and is fulfilled by a person at a fixed time, so capture and scheduling are the same problem and the leak sits between the phone and the job.
- Home Services
How revenue moves through a residential trade operation — inbound calls and online bookings, dispatch, estimates, financing, maintenance agreements — and the configurations under which each handoff stops carrying it.
- Veterinary Practices
How revenue moves through a companion-animal practice — reminders, estimates, prescriptions, referrals, wellness plans — and which system boundaries return an event and which return nothing.
- Aesthetic Practices
A booking platform and a consultation record hold different halves of the same person. Which revenue facts stop being computable in that split, and what evidence would confirm each one.
An inquiry becomes a matter, a policy or a relationship that realises revenue much later, so the leak sits in qualification, in the handoff between the intake system and the system of record, and in the long delay before value is known.
- Personal Injury Law
How contingency-fee practices lose value between intake CRM, case management and disbursement — the systems view of a revenue event that arrives after the click.
- Insurance Agencies
How commission revenue moves through an independent agency — rater quotes, agency management records, carrier downloads and renewals — and where handoffs lose it.
- Financial Advisory
How advisory firms compute a recurring fee, why a published page can become an artifact the stack cannot return, and where the path from inquiry to funded account loses its key.
Revenue renews on a schedule rather than on a decision, so the leak sits in billing state, in what the system does when a payment fails, and in whether a cancellation was chosen or merely happened.
- Pest Control
How recurring pest control revenue moves through service plans, route days, stored-card billing and termite bond renewals, and which configurations decide whether those handoffs hold it.
- Subscription Commerce
How recurring revenue is structured in subscription commerce, where billing state, entitlement state and credential state can diverge, and what evidence would confirm each divergence.
One diagnostic, not eight
Every page here points at the same Revenue Leak Scan. There is no industry-specific scan, product or offer, and none of these pages creates one. The capability domains behind the work live in the systems portfolio, and the operating model that sequences them is Revenue OS.