Revenue architecture

What revenue architecture actually means.

The term gets used for three different things. Only one of them is a job somebody can do.

No sequence, no newsletter. One reply from a person.

Got it. You will hear from hello@sapwood.io.

What each one is for

The data modelOne record per company, an object model that matches how you actually sell.Everything else sits on this
LifecycleStages with exit criteria, shared by marketing, sales and customer success.The contract between teams
Pricing and packagingWhat customers buy, in units that match the value they take.Where most leakage starts
Renewal mechanicsDates, owners, baselines and health built on usage rather than sentiment.Usually nobody owns it
CompensationWhat the plan pays for, against what the operating plan needs.Quietly decides behaviour
Reporting definitionsOne definition per metric, with an owner, so the layers above can be measured at all.The audit trail

Decide it with evidence instead of a demo

FreeRead-only, a written report with every gap priced, yours either way.
$2,000A month if you want it fixed. Up to 15 hours a week, Kaypo included.
No callYou can start from the pricing page without speaking to anyone.

Questions

What is revenue architecture?

The design of how a company makes money and how that is represented in its systems: the data model, lifecycle stages, pricing and packaging, renewal mechanics and the definitions the reporting sits on. It is the layer underneath RevOps execution.

How is revenue architecture different from RevOps?

RevOps is the function that runs and maintains the system. Revenue architecture is the design of the system itself. One is operating, the other is deciding how it should work.

When does a company need it?

Usually between 50 and 250 people, when the model built for the first product no longer matches how the company sells, or after an acquisition when two models have to become one.

Who owns revenue architecture?

In practice whoever can get finance, sales and customer success to agree. Often a COO or a RevOps lead with sponsorship, rarely a single named owner.

Want to talk it through?

Leave an email and I will reply myself, usually the same day. No sequence, no newsletter, and no calendar link unless you ask for one.

One reply from a person. Nothing else.

Got it. You will hear from hello@sapwood.io.

Would rather just book time? Here is the calendar.