MQL vs SQL, marketing qualified lead versus sales qualified lead, describes how far along a prospect is before it is worth someone's time to call them. An MQL has shown enough interest to be worth nurturing. An SQL has shown enough intent to be worth a real conversation.
That distinction matters even if you have never hired a salesperson, because every founder doing their own selling is already making this call, just without the vocabulary for it. The problem is that almost every explanation of MQL vs SQL online assumes a marketing team, a sales team, a CRM with lead scoring, and a documented handoff process between departments that do not exist yet in a two-person startup. You do not need any of that to use the distinction. You need three questions and five minutes per lead.
What MQL and SQL actually mean, without the RevOps vocabulary
A marketing qualified lead is someone who fits your ICP and has engaged enough to be worth more attention, someone who read three blog posts or signed up for a trial and logged in twice. A sales qualified lead is someone who has told you, directly or through their behavior, that they are trying to solve the problem now, not someday.
The vocabulary comes from an era when marketing and sales were separate departments arguing over whose job it was to follow up on a lead. MQL vs SQL: definitions, differences, and how to define both is one of the more thorough breakdowns available, and it is written for RevOps teams running a documented lead-scoring model, a routing SLA, and a dedicated SDR queue. None of that changes what the two terms mean. It just makes the definitions sound more complicated than they need to be.
Why the standard framework breaks for a two-person startup
Most MQL and SQL frameworks assume three things: a point-based lead-scoring model, a CRM that tracks page visits automatically, and a handoff SLA between two different teams. If you are the founder doing your own sales, all three assumptions are wrong, and forcing your funnel into that structure wastes the resource you have the least of, your own time.
GitLab's public MQL handbook sets a two-business-hour window for a sales rep to accept or reject a lead that marketing operations has already scored against a 100-point model. That system exists because GitLab runs a dedicated SDR org and a marketing ops function to maintain the scoring engine. A pre-seed founder has neither. Building a 100-point lead-scoring model before you have closed 20 customers is a way to feel productive without doing the one thing that actually moves revenue: talking to the right ten people this week.
The 3-question test that replaces lead-scoring software
Instead of a point-based score, ask three questions about every lead before spending any time on them: do they match who you actually built this for, did they do something that cost them real effort, and did that happen recently.
- Fit. Are they inside your ICP? Not a broad title and headcount range, but the specific role and situation you already know converts.
- Effort. Did they do something that costs more than a click? Replying with a specific question, booking a call, or asking about pricing counts. Downloading a guide does not. That is curiosity, not signal.
- Recency. Did it happen in the last 14 days? Interest decays fast. A lead who engaged heavily two months ago and went quiet is colder than a lead who asked one sharp question yesterday, the same trigger-event logic that separates buyers who are actually looking from ones who are just curious.
Two yeses, on fit and effort, is your MQL equivalent and worth a personal note today. All three yeses, fit, effort, and recency, is your SQL equivalent and worth a call this week, not a nurture sequence.
This is not a simplified toy version of lead scoring. It is the same signal a 100-point RevOps model is built to capture, minus the software and the two departments arguing over where the threshold should sit.
What this looks like with a real funnel
Say 40 people started a trial this month. Twelve match your ICP. Of those twelve, five did something beyond signing up within the trial window: invited a teammate, connected an integration, or asked a support question about a paid feature. Those five are your MQL-equivalent list.
Of those five, two reached out unprompted asking about pricing or renewal terms. Those two get a phone call today, not an automated sequence. The other three get a short, specific note referencing exactly what they did in the product. The 28 who signed up but never fit or never engaged go into a monthly check-in email, not a twelve-touch drip campaign.
This replaces the entire MQL-to-SAL-to-SQL routing architecture that larger teams build inside a CRM. The signal is the same, just captured by hand instead of by software. Pipeline is not demand, it is captured attention covers the adjacent mistake: treating this qualified list as your total addressable pipeline, when it is really just the leads who were already looking.
What to do this week
Pull the last 30 days of signups or inquiries into a spreadsheet with three columns: fit, effort, recency. Score each yes or no. Anyone who scores three for three gets a call within 48 hours. Anyone who scores two for three gets a personal email today. Run this by hand for one month and you will learn your real SQL threshold faster than any framework borrowed from a company running Salesforce with a RevOps team behind it. Once you have qualified 50 leads this way, sharpening your ICP into a moment instead of a headcount range finally becomes worth the time.
Frequently asked questions
What is the difference between MQL and SQL in simple terms?
An MQL is a lead worth nurturing because it fits your ICP and showed some interest. An SQL is a lead worth calling now because it fits, showed real effort, and did so recently. The difference is readiness, not enthusiasm.
Do I need a CRM to track MQLs and SQLs as a solo founder?
No. A spreadsheet with fit, effort, and recency columns handles qualification for your first several hundred leads. A CRM earns its setup time once you have more leads than you can review by hand in about 20 minutes a week, usually well past your first 50 customers.
What is a good MQL to SQL conversion rate for early-stage B2B SaaS?
Published benchmarks cluster around 13 to 15 percent for B2B SaaS overall, according to HubSpot's 2026 conversion data, but that number describes companies with defined lead sources and enough volume to segment by channel. At pre-seed volume, converting one or two out of every ten qualified leads is a normal, healthy rate.
Should I use a framework like BANT or MEDDIC before I have a sales team?
Not yet. Those frameworks assume a rep running a structured qualification call as their full-time job. The three-question test above captures the same signal with less overhead, and it is easier to run consistently while you are also writing the code or answering support tickets yourself.
When should I hire someone to own lead qualification instead of doing it myself?
Once qualification takes more than a couple of hours a week, or once qualified volume regularly exceeds what you can review in one sitting. That point usually arrives around 50 to 100 monthly qualified leads, not before.
What is the biggest mistake founders make with MQL vs SQL?
Treating every signup as equally worth their time. Time spent on a lead who never fit your ICP is time not spent on the two or three leads that quarter who were always going to become customers, if someone had called them fast enough.
The vocabulary of MQL and SQL was built for teams big enough to need a handoff contract between departments. You have the opposite problem: too few hours and too many signups that look identical at a glance. Three questions, checked weekly, tell you which five people in a list of forty deserve a phone call this week. That is the whole system worth building before anything more complicated.