The discipline
Revenue built to fit where each offer sits.
Revenue Architecture is the discipline: revenue built to fit where each offer sits, and kept fit as offers move.
The Continuum
The Continuum places each offer by what carries the value the buyer pays for, and who is accountable for it.
The Continuum, with example offers. The Continuum places each offer by what carries the value the buyer pays for, and who is accountable for it. Ordered by who does the core work the buyer pays for · not a ranking. Expertise: Judgment of named, accountable people, working with agents; the buyer pays for the person’s call (Advisory, Consulting). Service: A team’s method, scope set before the sale; the firm is accountable (Project, Managed). Automated Service: The provider’s systems and agents; the provider is accountable at machine volume; people supervise (Supervised, Autonomous). Product: An asset the buyer uses (physical, software, data); the buyer is accountable for its use (Complex, Scalable). Network: Participants the provider connects; the provider is accountable for the rules. The line between people and systems sits between Service and Automated Service. Three example offers from one company. Each starts at its position on the Continuum. Offer A · an implementation project, at Service; Offer B · a managed service, at Service, heading right toward Automated Service (shift right · more systems); Offer C · a software product, at Product, heading left toward Automated Service (shift left · more people).
It applies to each offer, never to the company. A company usually has offers at more than one position, and each one needs its own fit. It is not a ranking or a maturity path: an offer can move in either direction.
Offer positions
Five positions. Each is the business model of an offer.
- Expertise · Advisory · Consulting
- Judgment of named, accountable people, working with agents; the buyer pays for the person’s call.
- Service · Project · Managed
- A team’s method, scope set before the sale; the firm is accountable.
- Automated Service · Supervised · Autonomous
- The provider’s systems and agents; the provider is accountable at machine volume; people supervise.
- Product · Complex · Scalable
- An asset the buyer uses (physical, software, data); the buyer is accountable for its use.
- Network
- Participants the provider connects; the provider is accountable for the rules.
The people | system boundary sits between Service and Automated Service. Ordered by who does the core work the buyer pays for · not a ranking.
Fit
The same components look different at every position.
An Expertise offer sells the judgment of named people, so its proof, sales assets and selling process are built around them. An Automated Service offer sells what the provider’s systems deliver at volume, so the same components are built around the system, with people supervising. Offers that sit close together share what’s built once; offers far apart each get their own.
Movement
Offers move, in either direction.
Shift right is toward Network: more of the value moves into systems. Shift left is toward Expertise: more of it moves back to people. AI is moving many offers across the line between people and systems. When an offer moves, the components it depends on have to be refit.
Calibration tests each offer’s architecture against where it sits on the Continuum and against the evidence, and ends in a decision: shift · tune · no change needed. How Calibration works
Does each offer’s revenue architecture fit where that offer sits today, and where it is heading? When it doesn’t, the symptoms show up first. The problem
The Model and the system
What it’s made of, and how it runs.
The Model is the 23 components every company’s revenue runs on; each offer depends on 14. See the Model
The Revenue Architecture Operating System (RAOS) is the operating system that runs it, made of five parts. How RAOS works
Where do your offers sit?
The Diagnostic places each offer on the Continuum and shows where its revenue architecture doesn’t fit.