The term gets used for three different things. Only one of them is a job somebody can do.
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.
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.
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.
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.
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.
Would rather just book time? Here is the calendar.
We use cookies to run the site and to understand how it is used. You can accept all or necessary only. See our privacy notice.Privacy notice