MQL vs SQL: How to Define Each for a Startup

A relay team can field four fast runners and still lose the race at the handoff. The baton has to change hands inside a short stretch of track, at full speed. Good teams agree on a mark before the race: when the incoming runner reaches it, the outgoing runner starts to run.

A startup's marketing and sales teams pass leads the same way. A rep opens the CRM on Monday to a fresh list of MQLs, and the first two are a student and a competitor. By lunch she's stopped opening them, and the one real buyer near the bottom waits a week for a call. Marketing called every name on that list qualified, and nobody had written down what qualified meant.

An MQL and an SQL mark the two ends of that exchange. Two questions decide where the line between them sits. What has a contact shown before marketing passes them on, and what has a salesperson confirmed before the lead becomes a deal?

MQL and SQL compared

The two runners carry the same baton with different jobs. An MQL is marketing's prediction that a contact deserves a sales conversation, and an SQL is sales confirming it after one.

Lead definitions are one part of revenue operations, and what RevOps covers shows where the rest fits. In HubSpot, both lines become lifecycle stages with written entry rules.

Some teams now pass a different baton. Forrester released a new version of its B2B Revenue Waterfall in 2021, built around buying groups and opportunities. Its guide to the model tells companies to move beyond MQLs. A self-serve product can add a PQL (product-qualified lead), set off by trial activity such as inviting teammates.

When the MQL still fits: a contact-level MQL suits a company with low lead volume and one person making the buying decision. When a committee buys, track the account and its buying group rather than one contact.

Writing the handoff rule

A relay team marks its exchange point on the track. A startup writes its handoff rule on one page, signed by whoever leads marketing and whoever leads sales. At a startup that's often the founder, or a fractional CMO brought in to run marketing as a system.

Signed by: [marketing lead] and [sales lead]
Date: [date]    Next review: [date]

MQL (marketing-qualified lead)
Fit, all of these:
- Role: [titles that buy or champion the product]
- Company: [size, industry, location]
- Excluded: [competitors, students, current customers, others]
Interest, at least [number] of these within [number] days:
- [action that signals buying intent, such as a pricing page visit]
- [action]
- [action]
Skips the count: [a fit contact who asks for a demo or a price]

Handoff
- Each MQL goes to: [named person or rotation]
- First response within: [hours]
- Sales accepts or rejects within: [days]
- Rejection reasons: [no fit / no interest / bad contact data / already in a deal / timing]

SQL (sales-qualified lead)
A salesperson has spoken with the buyer and confirmed:
- Problem: [the problem the product solves, in the buyer's words]
- Decision: [the buyer decides, or the rep knows who does]
- Budget: [money set aside, or a budget conversation underway]
- Timing: [a reason to act within (months)]
Becomes a deal when: [a second meeting is booked, or a proposal is requested]

Recycle
Rejected or stalled leads go to: [nurture list], with the reason recorded.

Fill it in with sales in the room:

1. List the fit criteria from your ideal customer profile in terms a CRM field can check, then add the exclusions.
2. Pick a few actions that signal buying intent, and set how many a contact needs within a time window.
3. Name who receives each MQL and how fast they respond. Then agree on the short list of reasons sales can reject one.
4. Write the SQL criteria as questions a rep answers on the first call. BANT (budget, authority, need, timing) is a common starting point.
5. Set a review date. Your first rule is a guess, and the reasons sales gives for rejecting leads tell you how to fix it.

When one person holds both jobs: write the rule anyway. The first hire who takes one of those jobs will need something to read.

Worked example

A written rule proves itself in a real exchange. Take a hypothetical company selling scheduling software to dental groups, with this rule:

• Fit: a practice owner or office manager, at a group with two or more locations.
• Interest: two of these in 30 days: a pricing page visit, the demo webinar, a case study download.
• Skip: a fit contact who asks for a demo goes straight to sales.

An office manager at a three-location group watches the webinar, then visits the pricing page a week later. She's an MQL, and a rep calls her the next morning.

On the call, she says no-shows are costing every location chair time. The owner approves new software, and this year's budget already has room for it. The group wants a fix before a fourth location opens in the spring, so the rep books a demo the owner agrees to join. That makes her an SQL, and a deal opens in the pipeline.

A month in, sales has rejected a run of MQLs for the same reason: those groups are locked into a competitor's contract. Marketing adds a form question asking when that contract ends, and those contacts wait in nurture until renewal. The rule got better because every rejection carried a reason.

Common mistakes

A rejection with no reason drops the baton, and so do these:

• Counting every form fill: an ebook download proves curiosity. Once every download becomes an MQL, sales stops trusting the label.
• Letting a score make the SQL call: a lead score predicts. Only a conversation confirms, so no number moves a contact to SQL on its own.
• One team writing the rule: marketing alone sets the bar low enough to hit its target, and sales alone sets it high enough that nothing qualifies.
• Never revisiting it: a rule written before any deals close is a draft. Compare it with what actually closed, and change one criterion at a time.

Deciding where the line sits

Put the MQL line at fit plus real buying interest, and the SQL line at a conversation that confirms the deal. The signatures matter more than the exact criteria. A rule both teams signed settles a lead-quality argument faster than another meeting.

Write the page this week, with sales in the room. If you'd rather have it built into your CRM and run for you, that's part of my fractional CMO work. I've built HubSpot from scratch, and it's where I'd start most early-stage companies.

Agree on the mark before anyone starts running.