How you get there

The Revenue Architecture Operating System (RAOS)

Playbooks, plays and Operating Agents that build Revenue Architecture, and a human-orchestrated review loop that keeps it connected as your business moves.

Talk to the authors See the end state

Start from the destination

Every build starts from the Map.

Which of the eleven components on the Revenue Architecture Map are in place, which are connected, and where the business sits. RAOS works back from that picture.

Explore Revenue Architecture

Build it

Three layers, nine playbooks, twenty-seven plays.

3 layers · 9 playbooks · 27 plays · 5 Operating Agents

Strategy decides where and how the firm competes. Platform carries the revenue. Production creates, converts and grows it. Every play has a defined purpose and output, and the outputs connect from one play to the next.

Layer I

Revenue Strategy

The foundational logic that dictates where and how the firm competes for profit.

1 · Market Definition

Who the firm serves, who influences the decision, and where to concentrate resources.

  • 1.1 ICP Architecture

    Define the profile of the customer most likely to buy, succeed, and expand.

  • 1.2 Stakeholder Mapping

    Identify everyone who influences, blocks, or authorizes the decision.

  • 1.3 Segment Prioritization

    Allocate finite resources to the highest-value segments.

2 · Value Positioning

Connect the offering to the outcomes buyers actually care about.

  • 2.1 Value Architecture

    Build the complete value proposition and messaging architecture.

  • 2.2 Price-Value Engineering

    Design pricing that reflects value and withstands buyer scrutiny.

  • 2.3 Offer Structuring

    Package capabilities into a coherent offer with expansion pathways.

3 · GTM Architecture

The routes to market and revenue models that convert opportunity into revenue.

  • 3.1 Market Access Design

    Establish the fundamental GTM model and the most efficient paths to the ICP.

  • 3.2 Channel Orchestration

    Select the archetype mix and design the coordinated channel architecture.

  • 3.3 Revenue Modeling

    Translate GTM strategy into an assumption-explicit revenue model.

Layer II

Revenue Platform

The brand, technology, and operating system that carry revenue end to end.

4 · Brand System

The firm’s complete market-facing identity, from narrative to digital presence.

  • 4.1 Identity & Narrative

    Produce the brand platform and complete identity system.

  • 4.2 Authority Assets

    Build the IP and collateral that establish category authority.

  • 4.3 Digital Presence

    Build the website, email, social, and conversion infrastructure.

5 · Revenue Technology

The stack that captures, connects, and activates data across the lifecycle.

  • 5.1 Stack Blueprint

    Design a non-redundant three-tier revenue technology architecture.

  • 5.2 Cognition Engine

    Design and deploy the intelligence layer and its agents into production.

  • 5.3 Data Governance

    Establish the standards and stewardship that keep the stack trusted.

6 · Revenue Operations

The operating system that makes revenue measurable and accountable.

  • 6.1 Lifecycle Design

    Define the end-to-end lifecycle with binary entry/exit criteria.

  • 6.2 Revenue Governance

    Establish the meeting architecture, cadence, and FACT-based forecast.

  • 6.3 Performance Enablement

    Build the playbook library and coaching infrastructure.

Layer III

Revenue Production

How pipeline is created, converted, and expanded against live revenue events.

7 · Demand Generation

The campaign architecture that creates and develops demand.

  • 7.1 Market Awareness

    Deploy the governing narrative across all awareness activity.

  • 7.2 Intent Acquisition

    Convert awareness into identified, offer-engaged prospects.

  • 7.3 Pipeline Nurture

    Develop prospect readiness through segment-specific relevance.

8 · Opportunity Orchestration

The deal-management layer, from discovery to economic close.

  • 8.1 Collaborative Discovery

    Open the cycle, climb the Pain Ladder, and confirm fit progressively.

  • 8.2 Deal Orchestration

    Navigate stakeholders and competition to build consensus.

  • 8.3 Economic Validation

    Finalize the economic case and execute the mutual close plan.

9 · Account Optimization

Secure, grow, and elevate customer relationships over time.

  • 9.1 Impact Validation

    Secure renewal by verifying ROI and governing the account.

  • 9.2 3C Expansion

    Grow the account through continuations, crop rotations, and colonizations.

  • 9.3 Strategic Partnership

    Cultivate institutional alpha through deep strategic partnership.

Run it

Five Operating Agents operate the plays.

The playbooks say what to do. The Operating Agents do the operating: they diagnose, sequence, adapt and run the plays against live revenue events. Every agent output is a draft for a human decision.

Diagnostic Agent

Maps where revenue is breaking down and where opportunity sits across the whole architecture.

Architect Agent

Designs the play-activation roadmap and keeps outputs flowing coherently between plays.

Calibration Agent

Adapts canonical methodology to each client’s reality — language, cycle, data, and stakeholders.

Demand Agent

Operates the demand-generation plays continuously against live demand activity.

Engagement Agent

Operates the deal and account plays continuously against live deals and accounts.

Keep it connected

A human-orchestrated review loop keeps it connected.

Strategy reaches the live deal, and the deal teaches strategy back. People make the calls; the agents operate the plays.

  1. Step 1

    Plays run

    The Operating Agents run the plays against live demand, deals and accounts.

  2. Step 2

    Outputs feed outputs

    Each play’s output is the next play’s input, across all three layers.

  3. Step 3

    People review

    On a set rhythm, people review what the plays produced and make the calls.

  4. Step 4 · then back to step 1

    Playbooks update

    What the front line learns goes back into the strategy and the playbooks.

It keeps the architecture connected, written down so it transfers, fit to where the business sits, and getting better each cycle.

Authors and the mark

Written by John Stone and Sherwin Uretsky.

RAOS is written by John Stone and Sherwin Uretsky. The structure on this page (the layers, playbooks, plays and agents) is public. Revenue Architecture is a registered service mark of Revenue Architects.

About the authors Glossary

Revenue Architects is the team that implements RAOS. Work with the team →

Start from the Map.

Questions about RAOS or how it applies to your firm? Write to John Stone and Sherwin Uretsky.

Talk to the authorsExplore Revenue Architecture