Designs the commercial logic
Revenue Design
Build the operating logic that turns demand into revenue.
Revenue growth is not one function. It is a chain of decisions: how demand enters the business, how leads are handled, when sales should act, how opportunities progress, how customers retain and expand, and how management knows what to do next. Revenue Design defines that chain before anything is built.
- Capabilities
- 5
- Layers touched
- Context, Workflows, Control
- Sold as
- Never on its own. Scoped inside an engagement.
- Entry point
- Revenue Diagnostic
Why it breaks
The operating problem
Many companies have active marketing, sales and customer teams but no shared commercial logic. Definitions differ, handoffs are informal, CRM stages do not match reality and management reports outcomes after the fact. The result is leakage between functions rather than a lack of effort inside them.
Designs the commercial logic
Capabilities
Each capability owns one problem and states where it stops. Most engagements touch two or three of the five, rarely all of them.
The reasoning model
How ROUTE applies here
Applied to design, ROUTE stops being a description of what happens and becomes a checklist of what has to be decided before anything is built.
Recognize
Name what counts as a commercial signal here, and where it is allowed to enter.
Organize
Decide the shape every signal must take before anyone is allowed to act on it.
Understand
Set the rules that give a signal meaning: fit, intent, stage, priority.
Trigger
Name the decision, the owner and the SLA attached to each state.
Execute
Define the expected action and the evidence it has to produce.
The operating architecture
Which layers this area builds
Revenue Design decides what each layer has to contain. Revenue Systems is where it gets built.
- 01
Data
No capability in this area owns the data layer. Revenue Design work lands in it rather than building it.
- 02
Context
Built here by Acquisition & Demand, Lead Management.
- 03
Workflows
Built here by Sales Pipeline, Customer Revenue.
- 04
Action
No capability in this area owns the action layer. Revenue Design work lands in it rather than building it.
- 05
Control
Built here by Revenue Intelligence.
Fit
Who this is for
This is your problem if
- Three or more teams touch the same revenue with no shared definitions.
- Your CRM is populated but nobody makes a decision from it.
- You can name the revenue you win, not the revenue you lose.
This is not your problem if
- You have one seller, one offer and one channel.
- Your problem is product or price, not process.
How it connects
Four domains, one revenue system.
- 01
Growth & Content
Creates the signals
- 02
Revenue Design (you are here)
Designs the commercial logic
- 03
Revenue Systems
Makes the logic executable
- 04
Revenue Execution
Operates the motions
Questions
Frequently asked
Is this strategy consulting?
Do we need all five capabilities?
What does the output look like?
Can our own team do this?
Next step
The entry point is the Diagnostic.
A read across the five layers tells you whether the commercial logic is genuinely the constraint here, or whether the definitions are fine and the system is not enforcing them.