CQL and RevOps: The Conversation Qualified Lead Guide in Revenue Operations

slug: why-mql-and-sql-stopped-working-the-rise-of-cql

Why MQL and SQL Stopped Working

The classic funnel — [MQL (Marketing Qualified Lead)](/glossario/mql-marketing-qualified-lead) and SQL (Sales Qualified Lead) — was designed for a reality where the lead filled out a form, received email nurturing, and was passed to an SDR. The qualification signal was behavioral and asynchronous: clicks, downloads, automation scores.

In operations running on WhatsApp, Instagram, website chat, voice, and email simultaneously, this model breaks. The lead is no longer a static record in the CRM: they are a living conversation, with context, memory, and intent that change with every turn. Scoring forms in 2024 is measuring the shadow, not the object.

This is where the CQL — Conversation Qualified Lead comes in.

What is CQL (Conversation Qualified Lead)

CQL is a lead qualified by the conversation itself, not by the behavior surrounding it. Instead of summing points for email opens or visits to the pricing page, the CQL is validated by explicit signals extracted from the dialogue: declared intent, collected context, handled objections, and agreed-upon next steps.

A lead becomes a CQL when the conversation simultaneously presents:

• Clear Intent — the customer has declared a problem, timeline, or budget compatible with the offer.
• Sufficient Context — segment, size, decision-maker, and use case are recorded.
• Preserved Continuity — there is no memory gap between channels; the next agent (human or IAm) can resume without repeating questions.
• Next Step Commitment — meeting scheduled, proposal requested, trial started.

If one of these four pillars is missing, the lead is not a CQL — it is a conversation in progress. The CQL is the state of the conversation, not a stamp from marketing.

CQL vs MQL vs SQL: The Honest Table

MQL and SQL do not die — they become sub-states within a well-designed CQL. What changes is the unit of value: the conversation, not the lead.

Where the CQL Fits into RevOps

RevOps (Revenue Operations) exists to align Marketing, Sales, and CS around a single revenue operation. The historical problem with RevOps is that each department has its own definition of a "qualified lead" — Marketing delivers MQLs, Sales rejects them, and CS complains about the churn of poorly qualified customers.

The CQL solves this because it is a single shared definition, anchored in something all areas can see: the transcript and the context of the conversation.

In practice, within a RevOps framework, the CQL becomes:

1. The official handoff between marketing and sales — it replaces the MQL→SQL flow.
2. The primary productivity metric for the conversational team (humans + IA agents).
3. The forecast input — projected pipeline stops being "number of SQLs × win rate" and becomes "number of active CQLs × average Conversation Score".
4. The CS risk signal — a customer whose conversation has lost its CQL status (score dropped, continuity vanished) is an early churn alert.

How to Implement CQL in a RevOps Operation

1. Define CQL criteria with all three areas together

Gather Marketing, Sales, and CS and write down — on one page — which conversation signals turn a lead into a CQL in your operation. Use the four pillars (intent, context, continuity, next step) as the skeleton and fill it with the vocabulary of your market.

2. Instrument context capture

CQL only works if the conversation carries context across channels and shifts. This requires a layer of shared memory — Bandeja de Contexto, Crachá de Contexto, unified history. Without this, the CQL becomes just another CRM field that no one fills out.

3. Put the Conversation Score into production

The Conversation Score is the thermometer of the CQL over time. It combines signals such as response time, coherence of the IAm or human response, presence of context, and a clear next step. CQL is the state; the Conversation Score is the continuous variation of that state.

4. Rewrite the handoff SLA

In the MQL→SQL model, the SLA was "respond in X hours". In the CQL model, the SLA is "do not break the conversation continuity". Whoever receives the CQL must resume with context, not start over.

5. Audit with AI curation

When autonomous agents participate in qualification, it is mandatory to have a curation cycle: a sample of conversations reviewed by a human, feedback returning to the prompt, and metrics for adherence to CQL criteria. Without curation, the AI invents qualification.

slug: common-errors-introducing-cql-mci-revops

Common errors when introducing CQL

• Treating CQL as just another field in the CRM. If the definition doesn't change the handoff and the forecast, it has become mere decoration.
• Letting the IAm qualify alone without written criteria. The model needs the guide just as much as a human does.
• Keeping MQL in parallel "for safety." Two funnels = zero funnels. Make a choice.
• Measuring only CQL volume. What matters is CQL with a high Conversation Score and preserved continuity — not the raw number.

CQL is the bridge between MCI and RevOps

Marketing Conversacional Integrado (MCI) places the conversation as the unit of value. RevOps needs a shared unit of value across revenue areas. CQL is exactly that bridge: the qualified conversation becomes the object that Marketing produces, Sales advances, and CS preserves.

Those who implement CQL well stop operating three disconnected funnels and start operating a single revenue orbit, where each interaction accumulates context instead of discarding it.