FAQ
Questions buyers ask
Direct answers
The questions revenue leaders bring us, about AI, orchestration, and running strategy, marketing, and sales as one system.
What is Revenue Architecture?
Revenue Architecture is the practice of running revenue as one engineered, governed operating system — strategy, marketing, and sales orchestrated together rather than managed in silos. It is human-orchestrated, AI-enabled: people make the calls that matter while agents operate the plays at machine speed. Revenue Architects has developed and practiced Revenue Architecture since 2009 and holds it as a registered service mark.
What is the Revenue Architecture Operating System (RAOS)?
RAOS is the method and AI operating system behind Revenue Architecture. It is organized as three layers, nine playbooks, twenty-seven plays, and five Operating Agents. It is the layer above your decks, your tool stack, and your AI agents that keeps them coherent as you scale.
What is a revenue operating system?
A strategy deck tells you what to do; a tool stack gives you somewhere to do it; an AI agent does a task. A revenue operating system is the engineered layer that decides what each part of revenue is for, how the plays run, and how the agents operate on top — versioned and governed so it improves instead of decaying. It sits above your decks, your stack, and your agents and keeps them coherent as you scale.
Is RAOS a methodology or software?
Both, working together. The playbooks and plays set out what to do and why; the Operating Agents run the plays every day in your workspace; people review the results and make the calls. What the work teaches goes back into the playbooks, so the knowledge stays with the firm. The method is the canon; the Operating Agents run it; people orchestrate it.
What is Revenue Architecture built for?
Revenue Architecture is built for high-consideration selling: advisory, professional services, and complex solutions, where deals turn on trust, expertise, and multi-year value. Revenue Architects has developed and practiced Revenue Architecture since 2009 and holds it as a registered service mark. RAOS builds it and keeps it connected every day, so the plays keep working, and improving, long after the strategy is set.
Why aren't my AI sales and marketing tools working together?
Because tools operate tasks. Nothing above them decides what each part of revenue is for or how the plays connect, so each tool optimizes its own corner while the whole engine drifts. That missing orchestration layer is a revenue operating system — not another tool.
Does RAOS replace my CRM, marketing automation, or AI agents?
No. RAOS is not another tool in your stack — it is the layer that designs and directs the stack. Your CRM, marketing automation, and AI agents hold the execution: they send, score, route, and automate. RAOS holds the strategy and the reasoning — what to run and why — and keeps those tools serving one logic instead of pulling in three directions. The tools keep doing what they do best. RAOS decides what is worth doing.
How does RAOS connect to my existing tools?
Two ways, both human-orchestrated. RAOS reads from your stack — pipeline, signals, history — so its reasoning stays grounded in your reality rather than a whiteboard. And it pushes only approved output back to your tools: a practitioner reviews the brief, the sequence, or the play before anything runs, so the tools never act on raw, unreviewed AI output. RAOS also designs the stack in the first place, so capacity is bought against a strategy rather than ahead of one.
How do I make AI actually drive revenue instead of just doing tasks?
Put the agents inside a governed system where people orchestrate and agents operate the plays. Automate only where the design is already coherent — otherwise you scale dysfunction faster than you ever could by hand. RAOS is human-orchestrated, AI-enabled: the system carries the logic, the agents run it, and the calls that matter stay with people.
Does RAOS replace my revenue team?
No. RAOS is built to make your team better, not smaller. In high-consideration sales, judgment, insight, and trust are what the buyer is actually buying — and those are human. RAOS keeps people on the podium: they orchestrate the system and make the calls that win deals, while the agents run the plays at machine speed. You decide how much the agents do; the authority always stays with your team.
What does "human-orchestrated, AI-enabled" mean?
It means people direct the work and AI performs it. The practitioner sets the logic and makes the judgment calls on every play; the agents execute within that logic, and a human stays in the loop throughout. The distinction is one of elevation: rather than a person simply approving what a machine produced, the human role moves up the stack — to direction, judgment, and orchestration. Every agent output is a draft for a human decision.
Strategy, marketing, and sales are disconnected — how do I unify them?
Run all three as one system with RAOS, the operating system above them, so they improve together each cycle instead of being managed in silos. It is not a tool you bolt on; it is the engineered layer that decides what each function is for and how their plays connect. It also sits above the agent and orchestration tools you already run — RAOS does not replace your CRM, your marketing automation, or the agent frameworks operating inside each function; it directs them. Those layers are good at executing tasks; they do not know what the tasks are for. RAOS supplies that logic: the strategy, the plays, and the connected logic that turns isolated automation into one coordinated motion.
How do I connect GTM strategy to what the front line actually does?
You run one canon end to end. Three layers and nine playbooks mean Revenue Strategy, Revenue Platform, and Revenue Production all trace back to the same architecture, so what leadership designed is what the front line actually runs. Layer I — Revenue Strategy — produces the decisions: your ICP, the personas and Pain Ladder behind each, and the Value Architecture (the BVP → OVP → AVP → CVP messaging chain). These do not sit in a strategy deck; they synthesize into a Segment Plan for each priority segment, which rolls up into the GTM Plan — the deliverable that bridges strategy and execution. From there the cascade runs into Revenue Production, where the front line works: the BVP becomes the governing narrative of awareness, the OVP drives acquisition, the AVP carries nurture, and the CVP is struck in the deal. Same propositions, same architecture — now in the language of a campaign and a sales conversation.
Who is RAOS designed for?
RAOS is built for firms selling considered, high-trust offerings: professional services, consulting and solution providers, complex B2B products, and financial services. These are markets where deals are won on trust, expertise, and multi-year value. RAOS fits the plays to your firm’s actual commercial dynamics.
What are the three layers, nine playbooks, and five Operating Agents?
The three layers are Revenue Strategy (where and how you compete), Revenue Platform (what carries the revenue), and Revenue Production (how pipeline is made and grown) — nine playbooks and twenty-seven plays in total. The five Operating Agents are the named actors that run the work: Diagnostic, Architect, Calibration, Demand, and Engagement.
What is the Business Architecture Continuum (BAC)?
The Business Architecture Continuum is the framework that locates a firm across three business modes and six positions — Consulting (Advisory, Consulting Practice), Solutions (Service-Led Solutions, Product-Led Solutions), and Products (Complex Products, Scalable Products) — ordered left to right by increasing scale and decreasing margin. Position tells you how revenue is made today; the direction of any shift left or right tells you what is about to break. Revenue Architecture is fit to that position, and RAOS applies it in Playbook 3 (GTM Architecture, Play 3.1), where a firm’s coordinates on the continuum set how its go-to-market and operating model are configured. Like every framework in RAOS, it is authored by John Stone and Sherwin Uretsky.
Is the Business Architecture Continuum part of TOGAF?
No. TOGAF’s Architecture Continuum classifies enterprise IT architecture assets. The Business Architecture Continuum is unrelated: it shows where a firm’s business sits, from expert-led consulting to scalable products, and which way it is moving, which sets how the firm should go to market.
How does RAOS use AI, and is our data safe?
RAOS runs the plays in your workspace through its Operating Agents. It reasons through revenue problems with the consistency of a machine, but it operates within the governed canon and surfaces drafts for human decision at every play. Model access is server-side and never exposed to the browser.
How do consultants and advisors use AI without being replaced by it?
In an agentic world the practitioner conducts the AI rather than competing with it: their expertise goes on the podium, at machine scale. RAOS is the governed method beneath them, so their judgment stays distinctly theirs — amplified, not homogenized. That path is built for advisors and practitioners.
Can consultants work with RAOS?
Yes. Consultants can work alongside the authors’ firm as fractional architects, or adopt RAOS independently in their own practice. The Partners page explains both.
Go deeper: see Revenue Architecture, RAOS and the glossary. Advisors and practitioners can explore the path built for them on the Partners page.
Still have a question?
Write to John Stone and Sherwin Uretsky. They read every note.