The Revenue Architecture Model

Offers that sit close together share what’s built once. Each one still gets what its position needs.

Every offer runs on the same Model, but not the same build. Some components are shared across offers; others are tuned to what each offer’s position needs. Strategy makes the decisions, Platform holds what’s built once and shared, and Production runs and measures revenue day to day. Revenue performs when every component is connected and fits each offer’s position. Each offer depends on 14 of the Model’s 23 components.

Move an example offer along the Continuum to see how its scope changes, or open a component to see what it holds.

The interactive Model

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

Components

What each component holds.

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

    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

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

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

    Packaging & Pricing

    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

    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

    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

    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

    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

    Name, mark, voice, visual system.

    Company-wide
  • Platform · Market & Value 4 ★

    Proof & Evidence

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

    Shared
  • Platform · Offer & Economics 6

    Offer Catalog & Terms

    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

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

    Company-wide
  • Platform · Demand & Acquisition 10 ★

    Sales Assets

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

    Shared
  • Platform · Delivery & Realization 14

    Delivery Methods & Tools

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

    Shared
  • Platform · Retention & Growth 17

    Customer Programs

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

    Company-wide
  • Platform · Operations & Governance 20 ★

    Revenue Stack & Data

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

    Company-wide
  • Platform · Operations & Governance 21

    Team & Capabilities

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

    Shared
  • Platform · Operations & Governance 23 ★

    Revenue Process

    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

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

    Company-wide
  • Production · Demand & Acquisition 11 ★

    Demand & Channels

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

    Per offer
  • Production · Demand & Acquisition 12 ★

    Selling

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

    Shared by position
  • Production · Delivery & Realization 15

    Delivery & Outcomes

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

    Per offer
  • Production · Retention & Growth 18 ★

    Customer Growth

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

    Company-wide
  • Production · Operations & Governance 22 ★

    Operating Rhythm

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

    Company-wide

The operating system

Run on the Revenue Architecture Operating System (RAOS).

The Model is one of the five parts of RAOS, the operating system a company runs its revenue on. How RAOS works

Talk through your offers with the authors.