Signal / SaaS / 16 May 2026
The MQL / SQL taxonomy is dating: UK B2B teams are moving to field-defined pipeline stages
MQL and SQL were the dominant pipeline-stage vocabulary in UK B2B SaaS for over a decade. In 2026 they are increasingly seen as a dated framing. Three reasons (marketing-side definition, buyer self-qualification, multi-touch attribution) and what's replacing them.
The MQL / SQL taxonomy (Marketing-Qualified Lead, Sales-Qualified Lead) was the dominant pipeline-stage vocabulary in UK B2B SaaS for over a decade. In 2026 it is increasingly seen as a dated framing.
Three reasons it's losing its grip. First, MQL was always a marketing-side definition: it described a lead that had passed marketing's qualification gate, not a lead that the field actually wanted. The handoff conversation was structurally adversarial. Second, the buyer journey for UK B2B has shifted: a meaningful proportion of buyers now self-qualify through public content before any conversation with a vendor, which makes the 'MQL to SQL' transition increasingly artificial. Third, attribution is now multi-touch by default; the linear MQL-then-SQL pipeline assumed a clean origin event that no longer reflects how leads actually arrive.
The replacement language varying across UK SaaS in 2026: 'pipeline accepted' (the AE has agreed to work it), 'pipeline qualified' (it has passed MEDDPICC criteria), 'opportunity' (it has progressed past first meeting). This taxonomy is field-defined rather than marketing-defined, and tracks better against actual deal outcomes.
Sales operations teams still using MQL / SQL in 2026 should at minimum be tracking AE-accepted-pipeline as a separate first-class stage. The conversation is moving on.
Source: Editorial observation from UK SaaS RevOps practice. Synthesis of public sales-operations writing.