Beyond Revenue Architecture: How to Develop the Reasoning Behind Pipeline Decisions
Updated: Oct 6
We have become increasingly deliberate about designing commercial work. How deliberately do we develop the thinking it depends on?
An opportunity has been sitting at the same stage for six weeks.
The pipeline makes this visible. A pipeline review looks at stage progression, activity levels, qualification criteria and follow-up discipline. A sales coaching conversation may then address what the salesperson should do next.
Yet the decisive moment may have happened much earlier: in how a buying signal was read, in which explanation of the customer's hesitation seemed credible, or in how the salesperson concluded that the opportunity was ready to move forward at all.
We know a great deal about how the opportunity has moved. We may know much less about the reasoning that moved it.
Why this matters more now
When customers arrive with research and sometimes AI-assisted analyses of their own, the commercial conversation requires careful interpretation of the information they bring. People need to identify what is relevant, test assumptions without dismissing them, and recognise when a question has moved beyond their authority.
Commercial and customer-facing roles have strong development traditions: consultative questioning, negotiation, account planning, objection handling. These methods already draw on reasoning. Making the underlying forms explicit gives development a further point of focus: how that reasoning can be recognised, practised and carried across situations. It also creates a way to examine the habits of thinking acquired through education, career experience and personal development.
Experience adds another layer. Seasoned leaders read situations quickly. They recognise patterns, weigh considerations and reach judgements in ways that have become second nature. That is often exactly what expertise looks like. But reasoning that has become second nature is hard to explain, hard to pass on, and hard to examine when it begins to miss something. Examining it often takes careful questioning, with attention to what was known at the time: an explanation given afterwards can incorporate information that became available only later.
Revenue architecture connects commercial strategy with the design of the revenue system. Here, the focus is on its expression in pipeline stages, ownership and the conditions under which an opportunity moves forward. Making those conditions explicit does not, by itself, ensure that the reasoning used to interpret them is deliberately developed.
That interpretation is where much of the commercial outcome is decided.
Types of reasoning in sales and commercial work
We usually describe reasoning in broad terms. Someone is analytical, commercially minded, strategic, a good problem-solver. These descriptions are useful as far as they go, but they rarely tell anyone what to develop next.
It helps to name the forms of reasoning that problem-solving draws on. Diagnostic reasoning investigates a situation: it asks relevant questions and separates symptoms from possible causes. Causal reasoning examines what is actually producing an effect. Comparative reasoning evaluates alternatives against relevant considerations. Integrative reasoning brings several considerations together into a decision. Anticipatory reasoning explores possible developments and consequences, including unintended ones. Critical examination of evidence asks how reliable information is, what it assumes and where its limits lie. Metacognition monitors and regulates the thinking itself.
These are not separate compartments. Good diagnosis usually involves causal reasoning and critical examination of evidence. Anticipatory reasoning depends on causal reasoning too, since predicting a consequence assumes some understanding of what produces it. Comparison and integration are hard to separate in practice.
So this is best understood as a practical repertoire for examining reasoning, not a definitive classification of separate cognitive abilities. It is a set of reference points, not another competency framework with neat boxes.
Its value shows up in development. Consider two colleagues who would both be called good problem-solvers. The first investigates thoroughly, explores alternative explanations and usually reaches a sound diagnosis. But when choosing a course of action, she is less inclined to anticipate side effects or to weigh several competing considerations at once. The second spots risks before anyone else. Once he has formed an explanation, though, he finds it hard to revise when contradictory information appears.
Both carry the same label, yet they have different developmental needs.
With shared reference points, feedback can change. Instead of "You need to improve your judgement," a manager can say: "Your diagnosis was well developed. You identified the relevant information and explored alternative explanations. The next thing to strengthen is how you bring those findings together when choosing between possible responses."
A named form of reasoning also becomes something both people can return to. Over the following weeks, they can notice whether integration is improving, in which situations it matters most, and when it has started to happen without prompting.
Reasoning and technique
Forms of reasoning and the techniques that support them are different things.
A premortem, which means imagining that a plan has failed and working out why, is a technique that supports anticipatory reasoning. Scenario exploration is another. "Five whys" can support causal reasoning, although it can also lead a team down a single chain of explanation when several causes are at work.
Counterfactual examination needs particular care. Asking what would have happened under a different decision can inform causal reasoning, but it does not by itself establish what caused an outcome. Its value depends on the quality of the assumptions being examined. Done carelessly, it produces a convincing story built on hindsight: we already know how things turned out, and the alternative history is constructed to fit.
The broader point is that a technique can be practised without the reasoning it is meant to support. A team can run a premortem as a ritual, filling the whiteboard and ticking the box, without becoming any better at anticipating consequences. Equally, someone can reason well about the future without ever using a named technique.
Techniques are useful because they make reasoning easier to practise and discuss. The reasoning is the aim.
An outcome is incomplete evidence of the reasoning behind it
Managers are often pressed for time. Their experience lets them reach interpretations quickly, and the employee receives a conclusion rather than an explanation of how the manager arrived at it.
A shared language for reasoning makes a different conversation possible.
Imagine two account managers, each preparing a renewal in which the customer has signalled that they intend to reduce the number of licences.
The first offers a discount, but the customer still intends to reduce the number of licences. When her handling of the account is examined, it turns out she investigated thoroughly. She spoke to several users, reviewed the usage data and recognised several relevant uncertainties, including a budget review under way and a key internal champion about to leave. Where she went wrong was in bringing those findings together. She gave the budget conversation more weight than usage data showing declining adoption in two teams and treated a lower price as sufficient to address the reduction. She also offered the discount without seeking the required approval. Her development focus is integrating her findings and recognising decision boundaries.
The second secures the renewal on a smaller package. He recognised a familiar pattern, concluded the reduction was budget-driven and proposed a package the customer accepted. But he never examined whether adoption might also be contributing to the reduction. His development focus is examining alternatives before committing to an interpretation.
Judged by outcome alone, the first appears to need correction and the second appears to need none. Judged by reasoning, the first showed considerable capability, and the second has a development need that nobody has yet noticed.
If declining adoption is contributing to the second customer's decision, a smaller package may leave that issue unresolved. At the next renewal, the customer could seek a further reduction or question whether to renew at all.
This does not mean rewarding elaborate reasoning regardless of consequences. The first renewal still needs fixing. Outcome and reasoning are connected, but an outcome alone tells us only part of how it was reached.
The same applies across the architecture. An opportunity that advances a stage may have been qualified on solid evidence, or on an optimistic reading of an ambiguous signal. Both look identical in the pipeline until one of them stalls.
Matching the reasoning to each sales stage and meeting
We routinely identify the knowledge, skills and responsibilities a role requires. We much less often identify the reasoning demands of the situations people meet within it.
The aim is not to prescribe one correct way of thinking. It is to recognise what kind of intellectual work a situation deserves.
Commercial stages make different demands. Qualification is largely diagnostic and evidential: what do we actually know about this customer's need, authority and timing, and how confident are we? Designing a proposal is more integrative, balancing the customer's priorities, commercial viability and delivery capacity. Renewal planning is strongly anticipatory. The architecture defines what must be true at each stage; the repertoire describes the thinking needed to judge whether it is.
Meetings work in a similar way. A forecast review often contains several purposes at once: establishing what has changed, interpreting what it means, deciding whether to intervene and agreeing who will act. When those purposes stay implicit, the meeting can keep returning to diagnosis even when the available information is already enough to make a decision.
Purpose of the work | Reasoning worth considering |
Investigating an unexpected variation in performance | Diagnostic and causal reasoning; examining competing explanations |
Deciding between interventions | Comparative and integrative reasoning; examining trade-offs |
Preparing a significant change | Anticipatory reasoning, supported by scenario exploration or a premortem |
Reviewing a decision with an unexpected outcome | Causal reasoning and reflection, with care about hindsight |
Interpreting conflicting information | Critical examination of evidence, assumptions and uncertainty |
Reviewing a recurring management practice | Metacognition: examining the assumptions behind the practice |
The table is a reference point, not a rulebook. Its value lies in the question it prompts at the start of a discussion: what kind of thinking does this purpose require, and what might we otherwise overlook?
It also helps a team recognise which contribution is needed at a given moment. Someone who diagnoses well may be most valuable during an investigation. A colleague who integrates conflicting priorities may become more valuable as the discussion moves towards a decision. These are not fixed identities. Everyone can develop each form of reasoning, and the aim is to use a team's current strengths while broadening them.
Examining how we have chosen to think
It is not enough to ask whether a team used diagnostic, anticipatory or integrative reasoning. It is also worth asking whether that was the right approach in the first place.
Imagine a leadership team investigating why renewals in one segment keep slipping. They begin with diagnosis. Several meetings later, they are still refining it. Each time they reach a slightly better explanation, and each time nothing changes in practice.
The quality of analysis can keep improving long after its practical value has started to decline.
Continued investigation may be entirely justified. The decision may carry significant financial consequences, affect people's jobs, or involve commercial risks that are genuinely unresolved. The useful question is not simply whether it is time to stop analysing. It is whether further diagnosis is still proportionate to the decision at hand.
Perhaps the situation now calls for a decision under uncertainty. Perhaps the team needs to examine an assumption it has treated as fixed, such as the belief that the problem sits in the sales process rather than in the product or pricing. Or perhaps an established procedure would have been enough all along.
This is metacognition applied to collective work: regulating not only what we think, but how we have chosen to think.
What reflective infrastructure is made of
Reflective infrastructure is the combination of shared resources, deliberate opportunities, continuity and conditions that allows people to examine and develop the reasoning behind their work. It is more than time and space for reflection.
A shared repertoire. This is a common understanding of the forms of reasoning, the techniques that support them, and their purposes and limits, along with a language for discussing them.
Deliberate opportunity. Training, coaching, pipeline reviews, management meetings and everyday decisions become occasions to practise and examine reasoning, not only to review results.
Continuity. This is what turns useful conversations into infrastructure. Go back to the two renewals. A manager has identified different reasoning strengths and needs in each account manager. What happens next? Does the observation carry into the next coaching conversation, or does that conversation start again from the latest result? When a third account manager meets a similar signal, does the earlier learning reach them? If several people misread the same kind of signal, or offer concessions beyond their authority, does anyone notice the pattern? Can the management team then ask whether its own guidance on discounting is contributing to it?
None of this requires an elaborate recording system. It does require that learning has somewhere to go: coaching notes that record reasoning as well as actions, team discussions that revisit recurring cases, and a route by which patterns reach the people who can change guidance or process.
Conditions. Some things have to be true for any of this to work. People need to be able to explain how they reached a decision that went wrong without the explanation being treated as an excuse. Decision boundaries need to be clear enough that misjudging one can be told apart from never having been told where it was. Some meetings need protected time for examining reasoning, not just reporting status. Managers need to make their own reasoning visible, because a team will rarely examine its thinking more openly than its leaders do. And the effort needs to stay proportionate: not every decision deserves examination.
Infrastructure also raises practical questions of ownership. Who looks after the repertoire, so that it stays relevant without drifting into jargon? Which roles keep challenge alive in meetings, and should they rotate? Where can technology help us notice patterns in how we reason, and where might it simply produce a new kind of verdict? And what can perspectives from outside the organisation offer that internal discussion cannot? There is no single answer to any of these, but how an organisation answers them will shape whether reflective infrastructure becomes part of how work is done or remains a good intention.
What it cannot do
A shared repertoire does not eliminate arbitrary decisions or prevent shortcuts. Managers still exercise judgement, as they should.
It also carries a risk of its own: the language can become a source of authority. A manager can describe an employee's reasoning as "insufficiently diagnostic" on no more evidence than "be more careful" once had, only now it sounds more precise. Vocabulary can spread faster than the thinking it is meant to describe.
So the repertoire has to stay open to challenge, including when managers apply it. An assessment of someone's reasoning is itself a piece of reasoning, and the same questions apply to it.
Architecture and infrastructure
Within revenue architecture, the pipeline makes an important part of commercial work visible: where opportunities stand, how they progress, where they stall, and who is responsible for what. That visibility is valuable.
Reflective infrastructure addresses what happens inside that structure: how people interpret the evidence that moves work from one stage to the next, and how their capacity to do so keeps developing.
If reasoning shapes how work moves through the architecture, then developing that reasoning is arguably part of designing the architecture itself.
The aim is not to standardise people's conclusions. It is to make the reasoning behind those conclusions visible, discussable and developable.
Developing the Thinking Behind Commercial Performance
Commercial capability depends partly on how opportunities are interpreted, how buying signals are assessed and how decisions are made as accounts progress. Developing that reasoning alongside sales methods and processes creates opportunities to strengthen judgement within everyday commercial work.
Our Sales Effectiveness overview brings together different entry points into commercial performance development, depending on where the need or opportunity sits.
Comments