Revenue architecture

Revenue architecture is the design of the whole revenue system: which segments you serve, which motions reach them, where the hand offs sit, and what data proves it worked. It is a blueprint, not a department and not a job title.

Start with what is being designed. The United States Securities and Exchange Commission glossary defines revenue as the total money a company generates selling goods and services, which is the number every layer below exists to produce.

A revenue operations manager is a role that runs inside the design. The architecture is the design itself, and it outlives whoever holds the role this year.

Revenue enablement is not the same thing either. Architecture decides how the system is shaped, while enablement supplies the content, training and coaching that the people working inside that shape need.

Most companies never draw theirs. It accretes instead, one tool and one reorganisation at a time, until nobody can say where a lead goes after the demo.

Drawing it is cheap. An afternoon with a whiteboard and the four people who actually know what happens will expose more lost revenue than a quarter of dashboard work — and cost rather less.

Key takeaways

• Revenue architecture is a design, not a team. It names segments, motions, hand offs and the data behind them.
• Draw it before you hire. Structure chosen by accident costs more to unpick than it ever did to build.
• Hand offs are where revenue dies. Every boundary between teams needs an owner and a measurable rule.
• One definition per metric. Two definitions of a qualified lead will defeat any amount of reporting.

How it works

Treat it as five layers stacked on each other: segments, motions, hand offs, pricing and data. Each layer answers one design question, and each has a number telling you whether the answer is holding up.

Design the layers in order. A pricing change made before the segment question is settled will be reversed within two quarters — usually by the same people who pushed for it.

The segment layer sets everything downstream. A go to market strategy that serves three segments with one motion will underserve two of them and lose money on the third.

Motions are how you reach each segment: self serve, inside sales, field sales, partner, or some mix. Pick per segment rather than per company, and cost the choice honestly.

Hand offs deserve a named owner each. Marketing to sales, sales to onboarding, onboarding to support, support to renewal — four boundaries, four places a customer gets dropped.

Write the record definitions down and date them. An account, a qualified lead and a closed deal each need one meaning across every system, and the argument is worth having once.

The data layer is where most designs quietly fail. Pipeline management is the weekly routine that depends on it, and no routine survives two competing definitions of a stage.

A business model canvas is a useful sketch of the commercial logic, but it stops short of the operating detail. Architecture carries the boundaries, owners and record definitions a canvas leaves out.

Review the design yearly, not weekly. Architecture that changes every quarter is not a design at all, and the teams living inside it stop believing any version of it.

Examples

A software firm serving both small businesses and enterprises runs two motions off one architecture. Self serve checkout handles the first, a named account team handles the second, and the pricing page tells each which it is.

A business process outsourcing provider designs around contract length rather than deal size. Its architecture puts renewal conversations with the delivery lead who knows the account, not with a new seller.

An offshore services provider with three delivery sites designs its motions around time zones rather than territories. The architecture routes a lead to whichever site can take the first call, and the account stays there.

A professional services firm maps which revenue comes from new clients and which from expanding existing ones. The split turns out to be thirty to seventy — and the hiring plan is rewritten the same month.

A subscription publisher tracks revenue per user by acquisition channel, then redesigns its motions around the two channels holding value past month twelve. The others keep running on a smaller budget.

National statistics offices face the same consolidation problem. The United States Census Bureau replaced seven annual business surveys with one integrated survey covering business revenues, expenses, payroll and employment.

Related terms

• Flywheel model: a growth shape where each turn makes the next easier, one pattern an architecture can be built around.
• Chief revenue officer: the executive usually accountable for the design holding together across teams.
• Revenue operations manager: the role that runs the systems and routines inside the architecture day to day.
• Go to market strategy: the choice of segments and motions, which the architecture then makes operable.
• Pipeline management: the weekly operating routine that the data layer of an architecture has to support.

FAQ

How is revenue architecture different from revenue operations?

Architecture is the design: segments, motions, hand offs, data definitions. Revenue operations is the function that runs and maintains that design once it exists.

Who owns revenue architecture?

Usually a chief revenue officer or an equivalent commercial executive, because the design crosses marketing, sales, success and finance. No single team can hold it alone. Finance should sign off the data layer.

When should a company design one deliberately?

Before the second motion is added, or before the first serious hiring wave. Retrofitting a design onto four teams already working is far harder.

Does a small company need one?

Yes, though it may fit on a single page. Two segments and one hand off still need an owner and an agreed definition of a qualified lead.

What breaks first in a bad architecture?

Hand offs, almost always. Work falls between two teams who each believe the other has it, and the loss never shows up as a lost deal.

See how offshore teams support revenue work across Outsource Accelerator.