Revenue Architecture · Offer by offer

Design it around the offer. Run it as one system.

Every component of a company’s revenue architecture is fit to where each offer sits on the Continuum, and Calibration keeps it current as offers move.

From the authors of Revenue Architecture, forthcoming in 2027.

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

Where an offer sits on the Continuum, and which way it’s moving, sets what that offer needs.

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).

Offers shown are examples. Each ring is one offer’s Strategy, Platform and Production: Strategy Platform Production

An offer can move in either direction, and AI is moving many offers across the line between people and systems. Does each offer’s revenue architecture fit where that offer sits today, and where it is heading? More on the Continuum

The business shifts before the revenue engine does.

Growth depends on a few people.
Founders and senior experts carry the selling, and referrals don’t scale.
The story doesn’t travel.
Strategy is set once; the website, pitch materials and systems drift from it, and each team tells it differently.
There’s no common way to win.
Each expert sells their own way, so wins can’t be repeated and the forecast can’t be trusted.
Nothing learns.
Results don’t feed back into the strategy, so the same problems come back.

In our engagements, these trace to one cause: the revenue architecture doesn’t fit where each offer sits. Either an offer moved, or the architecture was built for a different mix of offers than the one that exists.

The Revenue Architecture Model: what every company’s revenue architecture is made of.

Offers that sit close together share what’s built once. Each one still gets what its position needs. Strategy decides, Platform is built once and used many times, Production runs and measures; each component is held company-wide, shared by nearby offers, or per offer. Revenue grows when every component is in place, connected, and fit to where each offer sits. These are the 14 an offer depends on; the full Model has 23.

Strategy · decide

Platform · build once, use many times

Production · run and measure

The operating system a company runs its revenue on.

The Revenue Architecture Operating System (RAOS) is Revenue Architecture deployed: the operating system a company runs its revenue on, across people, process, rhythm and technology. How RAOS works

Revenue Architects works with companies to deploy RAOS. Work with the team →

Written by the people who practice it.

John Stone and Sherwin Uretsky are the co-authors of Revenue Architecture, forthcoming in 2027. About the authors · Get the book first

Talk through your offers with the authors.

Questions about revenue architecture, RAOS or how they apply to your company? Write to John Stone and Sherwin Uretsky.