The operating system

The Revenue Architecture Operating System (RAOS)

RAOS is Revenue Architecture in action: the operating system a company runs its revenue on, across people, process, rhythm and technology. It sits above the tools you already use.

On this page

How it runs

A closed-loop revenue system

Five parts: Continuum · Model · Calibration · Connections · RAI.

Revenue Architecture: Strategy, Platform and Production as one loop around the offers, with Calibration running around it.

Human-orchestrated. AI-enabled.

Part 1 · Continuum

Five positions, set offer by offer.

The Continuum places each offer by what carries the value the buyer pays for, and who is accountable for it. 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.

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, Systems-run). 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).

Offers shown are examples. Each ring is one offer’s Strategy, Platform and Production: Strategy Platform Production
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 · Systems-run
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.

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.

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.

Part 2 · Model

Six build units, twenty-three components.

The Model holds the 23 components every company’s revenue runs on. They are built in six units: the components that are developed and changed together. Each offer sits at the centre, and its position on the Continuum sets what each unit must contain for it.

Value to MarketWho the offer is for, why it wins, what the buyer gets and on what terms, and what it delivers.4 components
Market PresenceHow the market sees the company and checks it out.4 components
Route to RevenueWho the offer reaches, how, and the stages that turn interest into agreement.4 components

Example offer

Offer A · implementation project

  1. Expertise
  2. Service
  3. Automated Service
  4. Product
  5. Network

Its position on the Continuum sets what each unit must contain for it.

Deliver & GrowWhat’s delivered and proven, and how accounts stay and grow.5 components
Commercial BackboneTerms, quoting, billing and the systems they live in.3 components
Operating CoreWho decides, who does the work, and the rhythm that runs it.3 components
Strategy · decide Platform · build once, use many times Production · run and measure Six build units, 23 components. Open a unit to see its components.

The diagnosis view: layers and domains

For diagnosis, the same 23 components are read by layer (Strategy, Platform, Production) and domain. Each offer depends on 14 of them. Move an example offer along the Continuum to see how its scope changes, or open a component to see what it holds.

What every company's revenue architecture is made of. Offers shown are examples. This view shows the 14 components an offer depends on. The full Model has 23.
Example offers on the Continuum

Move an offer along the Continuum. The bars show which offers share each component (not a score). Open any component to see what it holds.

Three example offers from one company. Each starts at its position on the Continuum.

Move an offer to see what changes.

How the sharing rules work

Each component starts at its default scope and changes only on its stated condition (open a component to see both). In this example only an offer’s position moves the bars. “Distant” means two or more positions apart. Product-like renewals and a self-serve funnel mean an offer at Product or Network. Conditions such as a sub-brand, separate sides, shared buyers or a different cadence are described in each component but not modelled here.

Calibration: how it works

The Continuum: what carries the value the buyer pays for

  • Company-wide: one for all offers
  • Shared: one for nearby offers
  • Per offer: one for each
  • Company-wide parent, with a cell per offer

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; Offer C · a software product, at Product. Offer B is heading right toward Automated Service (shift right · more systems). Offer C is heading left toward Automated Service (shift left · more people).

Strategy

decide

Platform

build once, use many times

Production

run and measure

Calibration

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.

  1. 1 · Something changes

    An offer moves along the Continuum, or the market moves around it.

  2. 2 · The review

    Inside the Operating Rhythm, the offer’s components and Connections are tested against where it sits and against the evidence.

  3. 3 · The call

    People make it: shift · tune · no change needed.

shift
Move the offer’s position or direction, and rebuild what depends on it.
tune
Keep the position; adjust the components that have drifted from it.
no change needed
The architecture fits where the offer sits. Leaving it alone is a valid design.

Nearby offers share. Distant offers each get their own.

See all 23 componentsWhat each one holds and its default scope, by layer.

23 components in three layers and six domains. Each is one object: what it holds and its default scope. ★ marks the 14 an offer depends on.

Strategy · decide · 7 components

  • Strategy · Market & Value 1 ★
    Audience & Position

    Build unit · Value to Market

    Who the company or offer serves, the problem, the competitive alternatives, where it stands against them.

    Company + each offer
  • Strategy · Market & Value 2 ★
    Value Story & Messaging

    Build unit · Value to Market

    The argument for choosing this company and offer; cascades company → offer → audience → engagement.

    Company + each offer
  • Strategy · Offer & Economics 5 ★
    Packaging & Pricing

    Build unit · Value to Market

    What the buyer gets and on what terms: each offer’s packaging, revenue model and price, under a company-wide portfolio and price architecture.

    Company + each offer
  • Strategy · Delivery & Realization 13
    Delivery Model

    Build unit · Value to Market

    How each offer is fulfilled: the human, AI and technology mix, capacity, cost to serve, quality standard, outcome commitments.

    Per offer
  • Strategy · Demand & Acquisition 8 ★
    GTM Plan

    Build unit · Route to Revenue

    How each offer reaches new buyers: routes to market, channels and partners, agent channels, selling model, targets, coverage.

    Shared by position
  • Strategy · Retention & Growth 16
    Account Growth Plan

    Build unit · Deliver & Grow

    Which accounts to keep and grow, renewal and expansion paths across offers, referral and advocacy approach.

    Company-wide
  • Strategy · Operations & Governance 19
    Governance & Decision Rights

    Build unit · Operating Core

    How revenue work is organized and governed: offer ownership, roles, decision rights, which metrics count, controls, and who decides what is company-wide, shared or per offer.

    Company-wide

Platform · build once, use many times · 10 components

  • Platform · Market & Value 3 ★
    Brand Identity

    Build unit · Market Presence

    Name, mark, voice, visual system.

    Company-wide
  • Platform · Market & Value 4 ★
    Proof & Evidence

    Build unit · Market Presence

    The verified base for every claim: cases, results, references, credentials, each with its source.

    Shared
  • Platform · Offer & Economics 6
    Offer Catalog & Terms

    Build unit · Commercial Backbone

    The authoritative offer definitions: packages, price books, contract and SOW templates, commercial terms, readable by people and machines.

    Company-wide
  • Platform · Demand & Acquisition 9 ★
    Presence & Discoverability

    Build unit · Market Presence

    Owned digital surfaces, search and AI-assistant presence, listings, structured offer data.

    Company-wide
  • Platform · Demand & Acquisition 10 ★
    Sales Assets

    Build unit · Market Presence

    Assets used to persuade: decks, proposal templates, playbooks, case summaries.

    Shared
  • Platform · Delivery & Realization 14
    Delivery Methods & Tools

    Build unit · Deliver & Grow

    Methods, IP, templates, tools and agents used to deliver.

    Shared
  • Platform · Retention & Growth 17
    Customer Programs

    Build unit · Deliver & Grow

    Standing programs for existing accounts: onboarding, reviews, success plans, community.

    Company-wide
  • Platform · Operations & Governance 20 ★
    Revenue Stack & Data

    Build unit · Commercial Backbone

    Commercial systems and data: CRM, marketing and sales systems, interfaces to quoting and billing, customer data.

    Company-wide
  • Platform · Operations & Governance 21
    Team & Capabilities

    Build unit · Operating Core

    The people and agents who do revenue work: roles, skills, capacity, incentives.

    Shared
  • Platform · Operations & Governance 23 ★
    Revenue Process

    Build unit · Route to Revenue

    The defined way revenue runs: lifecycle stages and exit criteria, qualification standard, hand-offs, forecast method, metric definitions.

    Company-wide

Production · run and measure · 6 components

  • Production · Offer & Economics 7
    Quote-to-Cash

    Build unit · Commercial Backbone

    Quoting, approval, contracting, billing, collection, revenue leakage.

    Company-wide
  • Production · Demand & Acquisition 11 ★
    Demand & Channels

    Build unit · Route to Revenue

    Recurring demand work: campaigns, content, events, thought leadership, PR, partner co-marketing.

    Per offer
  • Production · Demand & Acquisition 12 ★
    Selling

    Build unit · Route to Revenue

    Pursuits from first conversation to agreement, and the coaching and deal support that equip sellers.

    Shared by position
  • Production · Delivery & Realization 15
    Delivery & Outcomes

    Build unit · Deliver & Grow

    The delivery work, and measurement of outcomes realized against what was sold.

    Per offer
  • Production · Retention & Growth 18 ★
    Customer Growth

    Build unit · Deliver & Grow

    Account management, renewals, expansion and cross-sell, advocacy.

    Company-wide
  • Production · Operations & Governance 22 ★
    Operating Rhythm

    Build unit · Operating Core

    Recurring management work across all components and offers: pipeline and forecast reviews, offer reviews, calibration reviews, win/loss, market sensing, planning.

    Company-wide

Part 3 · Calibration

Calibration keeps every offer fit.

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. It reads each offer on two bases: its components and the Connections between them, and its Continuum position. Strategy changes reach it through the components they touch. It is part of the Operating Rhythm: reviews on a set cadence, quarterly as the standard and monthly while an offer is shifting. Each review asks what changed, what drifted, and what to do about it.

Between reviews, a live question is answered as a Calibration note, logged in the Record; when it needs a component built or changed, that build is scoped in its unit. Calibration can start from any of four ways in: the Diagnostic, a live question, a conversation, or the Facilitated Diagnostic.

Part 4 · Connections

Lit, dim or dark.

Connections are the named hand-offs between components: what one component passes to another so the second can do its job. Each is lit, dim or dark for an offer: lit when it holds and the component downstream uses what the one upstream decided, dim when it holds in part, dark when it doesn’t. RAOS shows the state of the Connections offer by offer, and which offers each gap affects; Calibration acts on the dim and dark ones.

A few named hand-offs · illustration for one offer
  • Value story Sales assets lit
  • Target buyers Go-to-market plan lit
  • Package and price Quoting and billing dim
  • Qualified interest The right seller dim
  • Delivery outcomes Proof dark

Part 5 · RAI

Revenue Architecture Intelligence (RAI)

RAI is the intelligence layer of RAOS. It holds the Record and keeps the system current, offer by offer: the state of the Connections, which business context is up to date, and what needs calibrating before each review. People make the calls.

Today RAI is practitioner-run: our team operates a combination of tools, AI and your Record, and the technical roadmap builds more of it out over time.

RAI is part of the architecture, not a product. A reader of the book can build the layer with the AI their company already uses.

RAI does the groundwork; people lead.

Illustrative RAOS screen for a fictional company, YourCo: one offer mapped across its revenue components, with the connections that are lit and the ones that are not.
Illustrative · fictional company Every offer mapped, everything that wins work connected and calibrated.
Illustrative RAOS screen for a fictional company: the lines not lit yet, ranked, each with how it was read and what people decided.
Illustrative · fictional company RAI shows what needs calibrating before each review.
Illustrative RAOS screen for a fictional company: recent calibration runs and the next sessions, on a chosen cadence.
Illustrative · fictional company Quarterly as the standard, monthly while an offer is shifting.
Illustrative diagram: RAOS works at the level of each offer’s revenue component architecture, above process models, orchestration platforms and sales and marketing tools.
Illustrative · fictional company Offer by offer, above the processes and the tools.

The vision

Where this is going

As agents take on more of your revenue work, RAOS is where you decide what each motion should be, offer by offer. Offers will be sold by people, by agents, or both. Someone still has to decide what they sell, to whom, at what price, and whether the hand-offs hold.

Reference: the component method

Each component of the Model has a method, in three sections:

  1. Design. Decide what each component must contain for each offer, where it sits on the Continuum.
  2. Build. Make it: the assets, systems and process the design calls for.
  3. Operate. Run it, measure it, and recalibrate it as offers move.

Glossary

Authors

Written by John Stone and Sherwin Uretsky.

RAOS is written by John Stone and Sherwin Uretsky, and it belongs to the discipline. The concept on this page is public. Revenue Architecture is a registered service mark of Revenue Architects. About the authors · Glossary

Revenue Architects implements RAOS with companies, offer by offer →

Talk through your offers with the authors.