The Statistic That Ends the Argument About Who Is Right

Average B2B MQL-to-SQL conversion sits at 13 per cent. That is the benchmark across UK and international B2B markets from multiple sources including First Page Sage and Ruler Analytics. It means that 87 per cent of what marketing generates and codes as qualified is rejected by sales. Eighty-seven per cent.

Marketing is not generating 87 per cent of its leads to fail. Sales is not rejecting 87 per cent of marketing's leads out of obstinacy. Both teams are applying their own definition of qualified — honestly, diligently, with genuine commercial intent — and discovering at the boundary between them that their definitions do not match. The statistic does not indicate failure on either side. It indicates the absence of a formally designed shared qualification architecture. The number will not improve through better marketing, better sales or better relationships. It will improve when the architecture is designed.

Why Alignment Is the Wrong Goal

The language of 'sales and marketing alignment' implies that the problem is one of orientation — that the two teams are pointed in slightly different directions and need to be brought into line. Alignment programmes address this: shared goals, shared metrics, shared language, joint planning sessions. They are useful interventions. They are not sufficient ones.

The problem is not that marketing and sales are misaligned. The problem is that they are operating without a shared, explicitly designed architecture for the commercial lifecycle. Alignment without architecture produces coherent misalignment: teams that agree on the language of qualification without having formally defined what qualification means; teams that share an OKR on pipeline quality without having designed the pipeline stages that would make quality measurable; teams that run joint planning sessions on the basis of a commercial process that was never designed to be planned around.

The correct goal is not alignment. It is architecture. A designed lead-to-order lifecycle that specifies, in writing and in the CRM, what a qualified lead looks like, what happens to it at every stage, who is responsible for each stage, and what must be true before any transition can occur. When this exists, marketing and sales do not need to be aligned — they are working from the same commercial truth.

What a Designed Qualification Architecture Actually Contains

A qualification architecture is not a lead scoring model or a shared definition of the ICP. It is a formally designed set of criteria that determines what must be true about a prospect before it is allowed to advance through each stage of the commercial lifecycle. It answers the questions: what signals indicate genuine commercial intent? What information must be captured before marketing passes a lead to sales? What must the buyer have said, done or committed to before a deal is allowed to move from one stage to the next?

Without these definitions, qualification decisions are made individually, in the moment, by individual marketers and sales reps applying their own judgement. The decisions are not wrong — they are reasonable responses to incomplete information — but they are inconsistent. And inconsistency in qualification data is the root cause of every downstream problem: unreliable forecasting, inflated pipeline, poor AI tool performance and the perpetual argument about lead quality.

The Pre-Sales Problem: Joining Too Late

In IT services, enterprise software, cybersecurity and management consulting, pre-sales or solutions engineering is a critical commercial resource. The timing of pre-sales engagement relative to the buying stage is one of the most significant drivers of win rates and cost of sale. Engage too early — with a prospect who has not yet made a genuine buying decision — and you invest expensive pre-sales resource in a deal that will not close. Engage too late — after commercial commitments have been made without technical validation — and you create delivery problems that damage the relationship before it has properly started.

When the lead-to-order architecture does not define the explicit trigger conditions for pre-sales engagement — the verifiable buyer signals that indicate a deal is ready for pre-sales involvement — engagement timing becomes a matter of individual judgement. Different sales reps pull in pre-sales at different stages. Pre-sales arrives without context because the handoff protocol does not exist. Commitments are made in pre-sales conversations that contradict commercial terms agreed earlier. And customer success inherits a relationship that was already complicated before the deal even closed.

What Happens to Customer Success When the Handoff Is Undocumented

Customer success inherits what sales and pre-sales committed. If those commitments were made informally — in meetings, on calls, in emails that were never captured in a structured handoff protocol — customer success inherits informally agreed scope. The onboarding conversation becomes a re-discovery session. The customer learns, in the first ninety days, that the promises made in the sales process require renegotiation. Trust erodes before the relationship has properly started.

This has a direct commercial consequence. Net revenue retention — the metric most strongly correlated with long-term company value in B2B — depends on customer success having clean, complete context from the sales team. Renewal conversations should not be about re-establishing what was agreed. They should be about the value delivered against a clearly documented baseline. Expansion opportunities should not be discovered through relationship conversations. They should be surfaced by an architecture that captures the commercial context of the original sale and uses it to identify when expansion is appropriate. None of this is possible when the lead-to-order architecture does not extend through to customer success.

The Architecture That Makes the Argument Unnecessary

When the lead-to-order architecture is designed — when the qualification criteria are formally agreed and written into the system, when the stage definitions are based on verifiable buyer commitment signals, when the handoff protocols specify exactly what information must be captured and transferred at every transition — the sales and marketing argument does not disappear. It simply becomes unnecessary.

Marketing generates leads that meet the agreed qualification standard because the standard is written into their campaign architecture and built into the CRM. Sales accepts leads that meet the standard because the standard was co-designed with their input and reflects the characteristics of deals that have genuinely converted. Pre-sales engages at the right point because the trigger criteria are defined in the stage architecture. Customer success inherits complete commercial context because the handoff protocol captures it. The argument is not won by either side. It is resolved by a designed architecture that both sides built together. O2, Vodafone, Symantec and Equifax all reached this point — not through better alignment, but through better architecture.