A new partner channel should be good news. Then a direct seller discovers that a partner has registered an account she’s spent months developing. Customer Success is asked to support an offer it had no part in shaping. Finance finds that the channel’s reported wins include business already expected through direct sales.
Everyone can explain their own decision. The CEO is left trying to make the decisions work together.
That is a useful place to begin with revenue architecture. Before adding another approval or asking the teams to cooperate, look at the commercial arrangement they’re being asked to operate.
What revenue architecture means
At Acuity, we define revenue architecture as the deliberate design of the interconnected system through which a business creates, converts, expands, and retains revenue. It connects the customers you pursue and the value you promise with your offer, routes to market, product, customer experience, people, incentives, data and technology.
The test is whether those choices support one another. If you promise a customer an outcome across its factory network, can your package, product permissions and account ownership support that outcome? If they cannot, the sales team may win an account that the rest of the business struggles to serve or expand.
Revenue architecture gives commercial strategy an operating form. Strategy establishes where you will compete and why customers should choose you. Architecture works through how the business must fit together to make that choice viable. Revenue operations helps run and improve that design. In a small company, the same people may do all three.
The advantage is in how the choices work together
Michael Porter’s work on strategic fit explains how activities can reinforce one another and make a competitive position harder to imitate. Applied to a revenue system, the opportunity is to build a combination that works for your particular customers.
A competitor can recruit partners or buy the same software. Matching a channel whose customer focus, offer, service model and incentives support one another takes more work. That is where we would look for an edge.
You can see the opposite when growth depends on repeated intervention. An executive rescues an account dispute, Product makes another exception and Finance reconciles incompatible numbers. Those interventions may be necessary today. If the same problems return, they deserve a place in the design discussion.
A channel can report growth while weakening the economics
Consider a fictional software company selling to manufacturers through equipment distributors. The direct annual price is $24,000. Management expects eighty partner wins, suggesting $1.92 million if every account paid that price.
The proposal, however, includes a 20 percent customer discount. Partners receive 25 percent of the discounted price. Each account also carries $3,600 of variable service cost and $2,400 of company acquisition spending. The program requires a further $300,000.
Here is the comparison, one step at a time.
Step | Calculation | Result |
|---|---|---|
Price after discount | $24,000 × 80% | $19,200 |
Contribution per partner account | $19,200 − $4,800 partner payment − $3,600 service cost − $2,400 acquisition spending | $8,400 |
Contribution from 80 partner wins | 80 × $8,400 | $672,000 |
Less program cost | $672,000 − $300,000 | $372,000 |
Direct business expected without the program | 30 wins × $13,200 contribution | $396,000 |
Change against that alternative | $372,000 − $396,000 | −$24,000 |
Original Acuity illustration. Values cover the first twelve service months of each account, with no initial-term cancellation. Direct contribution is $24,000 less $3,600 service cost and $7,200 acquisition spending. Acquisition spending is assumed avoidable and excludes the separately counted partner and service costs. Other fixed costs are excluded. This is a contribution comparison, not EBITDA or a calendar-year forecast.
Thirty of the partner wins are assumed to have happened directly anyway. That leaves fifty additional wins. A channel label in the CRM cannot establish what would have happened without the program; the assumption needs evidence.
Under these assumptions, the business earns $24,000 less contribution after launching the channel. The initial volume story has survived on the dashboard while the investment case has changed.
This does not settle whether a channel is worthwhile. It changes what leadership needs to decide. Could partners reach a customer group the direct team struggles to access? Would a different package support a better price? Could partners improve adoption enough to justify their payment? Those questions connect the offer, customer work and economics. Changing the commission rate alone will not answer them.
Resolve the tension where customers will feel it
A direct seller may see months of work and part of their income put at risk. A partner may fear opening the door only to be pushed aside. Asking both to be more collaborative leaves the bargain unresolved.
Agree who does the customer work, who receives quota credit and who gets paid. These are separate decisions. Shared credit may help during a transition, but additional compensation belongs in the economics. Two teams taking credit do not create two sales.
“God is in the details” is a saying associated with the modernist architect Mies van der Rohe. The commercial parallel is useful here. An account-registration rule can determine who may contact a buyer, how long a claim lasts and who settles a dispute. What looks like administration can shape the customer’s experience and the economics of the deal.
A complementary channel adds worthwhile reach, selling capability or customer value. Some direct business may move to it and still leave the company better off. Judge the combined result, including the work your own teams continue to do. Repeated disputes over ownership, price or credit are a reason to inspect the rules and incentives, not simply repeat the training.
Start with one decision you are about to fund
You do not need a complete map of the company to use this thinking. Take a live decision, such as launching a channel or changing a package, and put the people who must make it work around the same customer example.
Ask four questions:
Which customers should benefit, and what evidence shows that they value the proposed offer?
What must change together for the promise to hold, including product, customer work and compensation?
What would happen without the investment, and which costs and outcomes really change?
What finding would make us change or stop the proposal?
Name the commercial decision owner. Ask Finance to build the comparison with Sales, Product and Customer Success, using the same customer group and period. Before the next spending commitment, agree a limited test, a spending cap and a review date. Inspect buyer evidence, actual prices, service effort and disputes during the test. Review retention when the cohort reaches renewal; early activity cannot prove it.
The aim is to give people an arrangement they can use without repeatedly asking an executive to repair it. When the customer, offer and operating choices support one another, growth has a firmer basis than the next round of exceptional effort.
Work through the full decision
The full Acuity Clarity Guide, Revenue Architecture: What It Is and How to Apply It, develops this example into an alternative channel design. It includes four visuals, a six-step method, twelve leadership questions and an editable two-page working sheet. Use it to compare the choices, examine the assumptions and decide what to test before committing further.