The MQL Is Dead. The Signal Isn't.

What the MQL was actually for

The marketing-qualified lead solved a real problem, and it is worth remembering what that problem was. Marketing and sales needed one shared unit. Marketing needed a way to say "this one is ready," sales needed a way to trust the handoff, and both needed a line in the sand they could count and argue about. The MQL was that line. Fill out the form, clear a score threshold, and you crossed from "audience" to "lead." A rep picked it up. Everyone knew what the word meant.

That worked because it matched how buyers behaved. When the only way to learn about a product was to talk to the company that made it, buyers raised their hand early. The form fill was a genuine signal, because filling out the form was one of the first things a serious buyer did. The MQL measured the hand-raise, and the hand-raise came near the start.

What broke it

The buyer changed. The unit did not.

Most of the evaluation now happens before anyone fills out anything. Buyers read the docs, work the trial, come back to pricing a third time, and pull up a competitor in the next tab, all anonymously, on surfaces you own, long before they identify themselves. We walked through that shift in Where the Other 83% Goes: the part of the journey a form can see is the smallest part of it. By the time someone raises a hand, the opinion is mostly formed.

So the MQL breaks in four specific ways, and they compound:

• The form fires late, or never. It sits at the end of a decision that already happened anonymously, so it catches the buyer on the way out, not on the way in.
• The score lags. A nightly batch model scores yesterday's behavior against last quarter's fit definition. It describes the account you had, not the one that is live right now.
• Routing runs on a schedule. Leads drop into a Tuesday queue and get worked in order, on a calendar, not on the signal's clock.
• The unit itself is a claim, not a behavior. A form fill is what a buyer typed, once. It is the thinnest possible read of intent, and it arrives with the least context.

None of this means the MQL was a bad idea. It means it was built for a buyer who no longer shows up the way it assumed.

Declared intent is not revealed intent

Here is the distinction the MQL papered over. There is what a buyer declares, and there is what a buyer reveals. The MQL measured the declaration: the box someone checked, the form they filled, the demo they requested. Useful, but shallow, and easy to fake to yourself. The signal measures the revelation: what an account actually did, this week, on your site, in your product, in your CRM. Harder to tidy into a row, and far more honest.

Put the same account on the table twice and the gap is obvious.

Same company. One record captures what they typed three weeks ago and scored on a batch job. The other captures what they did this week and scored it now. The first is a claim. The second is behavior. Behavior is the more honest signal, and it is the one the MQL was never shaped to hold.

The replacement is not a better lead score

It is tempting to answer all this by tuning the model: more inputs, a fresher batch, a smarter threshold. That is still an MQL. It still ends in a number that describes the past and a queue that runs on a calendar.

The replacement is a different unit entirely: signal-based routing. It has three parts, and none of them is a score in isolation.

1. Name the pattern by its parts. Not "lead score 82," but "pricing viewed three times, docs read, a second seat added, comparison page hit." A pattern you can read, argue with, and point a rep at, because it says what actually happened.
2. Score it transparently. Score the pattern against your own definition of a good account, in a way you can open up and inspect, so the number is a summary of the behavior rather than a black box that replaces it.
3. Run the Play while the signal is still warm. The value of a signal decays. Acting inside the window it is alive is the whole point, and the faster that happens the more of the signal's worth you keep. Our CEO made the balance-sheet version of this case in You Already Paid for This Pipeline: intent you have already paid to generate quietly expires when nobody works it in time.

Toggle one account between the two views and the choice makes itself.

The same company, read as a dead MQL and read as live signal. Toggle between the two. Values illustrative, not a benchmark.

AS A DEAD MQL · STALE

SOURCE

Form fill (what they typed, once)

SCORE

Lead score 82, nightly batch (lags the behavior)

ROUTING

Routed Tuesday, round robin (runs on a calendar)

SIGNAL AGE

21 days old (the window has closed)

AS LIVE SIGNAL · WARM

SIGNALS

Pricing x3, docs, seat added, comparison page (what they did this week)

SCORE

Scored now, your fit definition (named by its parts)

ROUTING

Play run in the live window (fires on the signal's clock)

SIGNAL AGE

This week, still warm

Enable scripting to toggle one account between the two views. Values illustrative, not a benchmark. You would rather a rep call the live-signal account: the pattern is happening now and still worth a move.

Toggle with click or arrow keys. The whole exercise: ask which one you would rather a rep call today. Values illustrative, not a benchmark.

Read as an MQL, the account is a stale row: a form fill, a score of 82, routed last Tuesday, and by now the window has closed. Read as live signal, the same account is a pattern that is happening right now, scored against your fit, ready for a move today. Ask which one you would rather a rep call, and you have found the unit your funnel should be built on.

The MQL is dead. Long live the signal.

The MQL is not dead because qualification stopped mattering. It is dead because it measured the wrong thing: the declaration instead of the behavior, the past instead of the present, the calendar instead of the signal's clock. The intent it was trying to approximate is more alive than ever. It just stopped arriving as a form.

Signal-based routing keeps the job the MQL was doing, one shared unit between marketing and sales, and moves it onto what an account actually did. That takes something watching the stream, scoring the pattern, and running the next step while it is still warm.

Bryn is not another dashboard to watch. It is the governed execution layer that runs Plays through your stack. This is the concept piece, so we will leave it at one line: the point is not that you need a specific tool, it is that qualification only pays off when the unit is live behavior and the move happens while the signal still is.

Do it this week

Take one account that converted to MQL last month, and one that never filled out a form but hit your pricing and docs three times last week. Put them side by side. Now ask your team a single question: which one would you rather a rep call today?

Almost everyone will pick the second account. That answer tells you which unit your funnel should be built on. The next step is to name that second pattern once, out loud, by its parts, and wire it to a single action, even a manual one. That is the whole exercise. Nearly everyone has the signal. Very few run it.

The MQL measured the hand-raise. The hand-raise moved. Stop qualifying the form. Start qualifying the behavior.

Bryn is the Signal-Based GTM agent for Growth teams. For teams that want live signal watched, scored, and run for them, see it at civic.com/bryn.

Sources and further reading

• "Where the Other 83% Goes" (Team Civic), on how much of the buying journey now happens anonymously, before any form: civic.com/field-notes/where-the-other-83-percent-goes
• "You Already Paid for This Pipeline" (Chris), on perishable intent and speed to action: civic.com/field-notes/you-already-paid-for-this-pipeline
• "Everyone Has Signals" (Chris), the signal thesis: civic.com/field-notes/everyone-has-signals