A Lead Qualification Framework That Connects Marketing to Sales

The MQL to SQL handoff challenge

I have sat in this room more times than I can count. Marketing says the leads are good. Sales says the leads are junk. The CRO wants a dashboard that settles it. Nobody trusts the numbers on the dashboard.

So the team does what teams do. They buy a tool. They add fields. They rebuild the lead scoring model. Six months later, they are having the same argument with better software.

Here is my position: most RevOps teams do not have a tool problem. They have a process problem. Marketing and Sales are not aligned because nobody agreed on what each stage of the funnel is supposed to prove. The CRM supports the process. It is not the process.

That is the job of a lead qualification framework for marketing and sales. A lead qualification framework is the agreed set of tests a lead has to pass before it moves to the next stage, plus who runs each test. Most teams have the tests. Almost none have agreed on who runs them.

What follows is the framework I use to fix that. I don't think it is the final answer. I think it is a good place to start.

BANT is not the problem. Timing is.

Sales teams already have a qualification framework. BANT: Budget, Authority, Need, Timeline. It works. And if you're not familiar with it, get familiar here: HubSpot's guide to BANT.

The trouble is that BANT gets asked all at once, by one person, in one call. The SDR is expected to confirm budget before anyone knows if the prospect has a real problem. Marketing gets blamed for leads that fail a test they were never designed to pass.

BANT tells you what to ask. It does not tell you who should ask it, or when. That missing sequence is where the handoff breaks.

Don't get me wrong. I like BANT. It's a solid guide when you're a rep on the phone with a decision maker.

But if you lead RevOps, zoom out. The question isn't what to ask. It's where in the funnel each question belongs.

The Four Rights: a lead qualification framework for the whole funnel

The Four Rights takes the questions you already ask and spreads them across the funnel. Each stage proves one thing. Each stage has one owner. Nobody gets judged on a question that wasn't theirs to answer.

If the names look familiar, they should. Each Right is one letter of BANT, moved to the stage where it can actually be answered.

Right	BANT	Owner	Funnel stage	What it proves
Right Problem	Need	Marketing	Lead to MQL	They engaged with an offer that names a problem you solve
Right Person	Authority	SDR	MQL to SQL	We are talking to someone who can move this forward, a decision maker, budget holder, or executive leader
Right Time	Timeline	SDR	SQL to Opportunity	They plan to act in a real window (30 days by default, until your data says otherwise)
Right Budget	Budget	AE	Opportunity	The deal works: proposal, scope, and negotiation

A few things matter here.

Marketing owns the problem, not the deal. An MQL means one thing: this person raised a hand around a problem we solve. That is the job of the offer. It is not a promise that they will buy.

Right Budget is not "can they pay." It is whether the deal makes sense for both sides. That gets worked out in the proposal and the negotiation, not in a discovery call.

SDR and AE are responsibilities, not headcount. On a small team, the founder might do all four. That's fine. The point is knowing which question you are answering right now.

BANT doesn't go away. It stays in the rep's pocket as a quick way to disqualify in conversation. The Four Rights just decides where in the funnel each question belongs.

Want help mapping the Four Rights to your own funnel? Work with me.

Retire "not a fit"

The most common rejection reason I see in any CRM is "not a company fit." It is also the least useful. It could mean the company is too small. It could mean the wrong industry. It could mean the rep didn't feel like calling.

If Sales is going to reject a lead, the reason has to be specific, and it has to be backed by data. Break "not a fit" into real sub-reasons your team agrees on. A starting list might look like this:

• Below our minimum company size
• Outside the industries we serve
• Already a customer, or a duplicate record
• Student, job seeker, or researcher
• Competitor
• No plan to act in the next 12 months

Each one points to a different fix. "Outside the industries we serve" is a targeting conversation with Marketing. "Duplicate record" is a CRM cleanup job. "Not a fit" points nowhere.

Make the reason required. Then look at the patterns every month.

One more rule I push for: if a lead from a new industry shows high intent, they get at least one conversation before anyone rules them out. Your ideal customer profile should come from closed-won data, not from what the team assumed last year. Sometimes the market is telling you something new. You only hear it if someone picks up the phone.

A starting line, not a finish line

I am not handing you a finished system. I'm handing you version one. Your first set of definitions will be wrong in places. That's the point. You can't improve a process nobody has written down.

Here is how I'd start:

1. Get Marketing and Sales in the same room. Write the definitions together. If one side writes them for the other, the other side will not own them.
2. Agree on one handoff SLA. For example, first touch on every MQL within one business day. Pick a number both teams can live with, then measure it.
3. Build it into the CRM last. Map each Right to a stage and an owner. Keep the required fields to the few that matter. Reps avoid systems with too many fields. And make sure reps can actually work in the CRM day to day. If you're on HubSpot, my onboarding checklist for sales reps covers that setup.
4. Review at 30 and 60 days. Look at where leads stall and why they get rejected. Adjust the definitions. Then do it again.

If that sounds like a sprint review, it is. You don't need to call it agile. You just need a team that inspects what it built and makes it better.

Connect the work before you connect the tools

RevOps exists to connect what Marketing does with what Sales needs. That connection doesn't come from the integration between your CRM and your marketing platform. It comes from shared answers to simple questions. What does an MQL prove? Who owns the next step? How fast? What counts as a real rejection?

Answer those first. Then build the system that carries the answers.

Popular CRMs like HubSpot and Attio are built to support your process. Use them to set guardrails: required rejection reasons, SLA alerts, clean routing. But remember that building guardrails should not remove the human in the loop. A workflow can flag a lead. It takes a person to have the conversation.

Disclosure: the Attio link is a referral link. You get 10% off, and I may receive a credit, at no extra cost to you. I have no referral relationship with HubSpot. Nobody paid for either mention.

So I'm curious: where does your funnel break today? Is it at the problem, the person, the timing, or the budget? Email me and tell me. And if you'd rather fix it together, here's how I work with teams.