Engagement is not authority: why engaged deals still stall
Pipeline shows who showed up, not whether the people who can authorize the deal are aligned.
Picture the strongest deal in your forecast on engagement alone. The meetings are frequent and the technical questions keep coming. The people you work with are enthusiastic, and every stage in the CRM has been completed on time.
Chapter 12 of Era Six, my book on the next era of B2B revenue, opens with a deal like that. A manufacturer is evaluating a predictive maintenance solution. Engineering is enthusiastic and engagement is heavy. But finance has not reviewed the capital required, and enterprise architecture has unresolved integration concerns.
The deal was not rejected. It was deferred in favor of other initiatives. Activity was high and authorization was never possible.
"Enterprise deals rarely stall because buyers lose interest." (Chapter 12, When Engagement Does Not Lead to a Decision, Era Six) I think that sentence describes a good share of the slipped quarters I have seen in my nearly three decades in B2B growth.
The signal was real. It measured something else
We have become exceptionally good at measuring engagement, intent, meetings, stage progression and pipeline movement. Yet very few of those measures tell us whether the people who must say yes are in the conversation at all.
Nobody in the manufacturer's deal misread anything. Engineering's interest was genuine, and the seller's activity was sound. ABM made an important leap from the lead to the account, and RevOps made that activity visible and manageable. Both did what they were built to do.
The gap is in the standard. Engagement tells you where energy is flowing. It does not tell you where the power to decide is held, or whether those holders have seen the proposal yet. A map that shows motion beautifully can still be the wrong map for the terrain.
Why authority is spread out, and why that is healthy
It is tempting to treat the finance review or the architecture review as friction, a hurdle the buying group puts in the seller's way. The book argues for a different reading.
Large organizations distribute authority across functions because each function guards against a different kind of risk. Capital allocation protects against financial risk. Technical feasibility protects against architectural risk. Operational capacity protects against the risk that the organization cannot absorb the change. Strategic alignment protects against spending on something that does not matter. As technology initiatives reach into data, security, compliance and customer experience, more of these checks come into play, not fewer.
Those functions will pull against each other, and the chapter names three recurring tensions: fiscal discipline against platform resilience, vision against execution, and regulatory adherence against market agility. It is easy to read them as politics. The book says otherwise: "These tensions are not evidence of organizational dysfunction." (Chapter 12, How Authority Dynamics Interact, Era Six)
They are how an enterprise tests whether an initiative holds up. A deal that has been through them is better grounded than one that never met them. Enthusiasm in one area does not offset a gap in another, and in many enterprises technical leaders can block even well-backed initiatives.
This is governance working as designed. Revenue teams will do better reading that structure than working around it.
What it does to the forecast
If a deal is missing one of the four, the failure usually does not look like a loss. "The most common failure mode here is not outright rejection but indefinite deferral." (Chapter 12, A Philosophy of Decision Readiness, Era Six) Operational gaps in particular tend to produce deferral rather than a clean no.
That is why the cost shows up where it does: slipped quarters, commit calls that will not hold, and a pipeline that looks healthy until the final weeks. A deferred deal never turns red. It just stops moving, and the CRM keeps showing activity.
For a CFO, a board member or an investor reading that pipeline, the question changes. It is no longer only how much is in the pipeline and how engaged it is. It becomes whether the pipeline shows who can authorize, or only who showed up. The book puts the distinction this way: "Engagement measures activity; authority dynamics measure power." (Chapter 12, Reading the Signals of Readiness, Era Six)
The chapter describes two common gaps. One is deep technical engagement with no view into capital allocation. The other is operational enthusiasm without an executive sponsor.
Take a typical deal: an operations team is keen, runs a thorough evaluation and champions the solution internally. No executive owns the outcome, so the evaluation stays tactical. Strategic sponsorship can move an initiative from a tactical evaluation to a priority, but until someone provides it, the deal has energy and no route to a decision.
This is where the idea of Buyer Group Intelligence matters. "Buyer Group Intelligence is the continuous understanding of who holds decision power, how influence flows between stakeholders, and whether the conditions for commitment are forming across the lifecycle of an account." (Chapter 11, Defining Buyer Group Intelligence, Era Six) Engagement is one input to that understanding. It cannot stand in for it.
What to do differently
I would not suggest rebuilding anything this quarter. I would change the question the pipeline answers, from "Are they interested?" to "Are they structurally capable of making a decision?"
In practice, that starts with a check at every stage of an active deal. Ask which of the four areas has no engaged name against it yet:
- Capital allocation: who has reviewed the capital required?
- Technical feasibility: who owns the integration and architecture questions, and are they resolved?
- Operational capacity: who will have to absorb the change, and have they weighed in?
- Strategic alignment: who ties this to a priority the organization has already named?
An empty line is not a failure of the rep or the champion. It is information. The engineers who download documentation and request proofs of concept are doing their jobs, and they often cannot authorize alone. The most useful thing a seller can do is help them bring finance and architecture in earlier, which is also what moves a stalled deal forward.
The second change is in what leaders expect to hear. A revenue organization should be able to explain why a deal is stalled, not only whether it is. Saying that engagement is high is a description. Saying that finance has not yet seen the capital case, and that architecture has open integration concerns, is a diagnosis you can act on.
The third change is the unit of measurement. High engagement with narrow alignment is a high-risk bet. Moderate engagement with broad alignment is a stronger foundation. Moving from tracking individuals to reading the alignment of the group is the practical shift, and it is the shift Era Six and Catalysi are built around. I believe it should become the standard for what a revenue organization measures.
I hold that view with some humility, and I welcome disagreement as much as resonance. Where have you seen a deal with every sign of interest that had no one yet able to authorize it?
Read a preview of Era Six on the book page (Era Six), then join the Catalysi waitlist with the button at the top of every page.