Before You Hire: MQL vs SQL for a Founder-Led Sales Team

The mql vs sql distinction separates a lead marketing considers ready for sales follow-up from one sales has qualified as a potential customer, using HubSpot's definitions. Before you hire a marketing leader, agree the evidence, owner and next action for each stage so you can judge the role against shared numbers.

I'd settle those rules before writing the job scorecard, because you can't fairly assess someone against a definition that changes during the Monday meeting. You can still hire while improving the process. Give the person a clear starting point.

What do MQL and SQL actually mean?

MQL means marketing qualified lead. SQL means sales qualified lead. The difference is who has qualified the lead and what evidence supports their decision.

For your business, I’d define an MQL as a relevant buying enquiry with enough evidence to justify a sales follow-up. That might mean a suitable company, an identifiable need and a request to discuss your service. Choose the evidence your team can actually record.

I'd reserve SQL for an enquiry that sales has checked and accepted for active pursuit, because marketing activity alone shouldn't determine the sales forecast. Require a note explaining the need, the fit and the agreed next action.

A download or email click can inform the assessment. Don't make either sufficient on its own. For the rules below, qualification means a recorded decision about a buying enquiry, rather than a score attached to every person who interacts with you.

Which mql vs sql rules belong in a small CRM?

Use a short stage definition with an entry rule, a named owner and an exit rule. Start with rules people can apply without asking you to interpret every lead.

The table below is a suggested working agreement. It isn't a universal standard, so change the evidence to suit how your customers buy.

Decision	MQL	SQL	Opportunity
Entry evidence	Relevant company and a credible buying signal	Sales has checked fit and the buying need	A defined piece of work is being pursued
Decision owner	Person responsible for marketing qualification	Person responsible for selling	Person responsible for the deal
Required note	Why sales should follow up	Why sales has accepted it	Scope, commercial next step and unresolved questions
Next action	Sales review or contact	Agreed follow-up with the buyer	Action that advances the buying decision
If it cannot progress	Record why it wasn't accepted	Close or return for later follow-up	Record the loss reason or agreed pause

Keep these definitions somewhere the team can find them (a document will do, founders don't need another constitution). Ask the people applying them to check actual records before you make them part of a new hire's targets.

How should a lead move through your CRM?

Record a stage change when the agreed evidence exists. For mql vs sql to mean anything, the CRM needs to show why an enquiry moved and who made that decision.

I'd use the following sequence as a starting process, because it separates incoming activity from qualification and commercial work.

1. Record the enquiry with its source, arrival date, contact details and a named owner. Check for an existing record before creating another one.
2. Mark it MQL when the agreed marketing evidence is present. Record the qualification date, the reason and the person responsible for the sales review.
3. Mark it SQL after sales has checked and accepted it. Record the acceptance date, the buying need and the next action with a due date.
4. Create an opportunity when there is a defined piece of work to pursue. Add the commercial next step and the information still needed before a proposal or decision.
5. Close or return the record for later follow-up when it cannot progress. Record the reason and, where relevant, the trigger for contacting the buyer again.

Allow a direct sales enquiry to enter at SQL when the evidence supports it. Don't force someone through a marketing stage merely to complete the sequence.

Keep the original source and each qualification date when the stage changes. If your CRM can't retain that history, keep a controlled export or spreadsheet alongside it. Otherwise, you won't have the records needed to compare cohorts later.

Who owns qualification when you still do the selling?

You own the sales acceptance decision if you're the person selling. In that situation, the mql vs sql boundary needs your explicit acceptance or a reason for returning the enquiry, rather than an assumption from marketing.

Give each enquiry one named person responsible for its next action. Marketing can own the evidence needed for handover, while you or a salesperson owns the review and subsequent contact. Agree a review deadline that your team can meet, including cover when the owner is away.

Keep three outcomes separate: accepted, returned with a reason and awaiting review. An enquiry that hasn't been reviewed cannot tell you much about the quality of marketing's qualification.

Ask for specific return reasons, such as service mismatch, no current buying need or duplicate enquiry. Record failed contact attempts separately from confirmed poor fit. “Couldn't reach them” doesn't establish whether they would have been a suitable customer.

You can delegate this decision later. Write down the evidence now so the next salesperson can apply the same rule without borrowing your judgement every time.

Which conversion numbers should you review?

Review conversion between stages alongside the records still awaiting a decision. Your mql vs sql report should let you distinguish rejected enquiries from enquiries sitting with an overdue follow-up.

Use these calculations for a defined group of enquiries:

MQL-to-SQL conversion = MQLs that became SQLs ÷ MQLs in the cohort × 100

SQL-to-opportunity conversion = SQLs that became opportunities ÷ SQLs in the cohort × 100

Opportunity-to-win conversion = opportunities won ÷ opportunities in the cohort × 100

Choose one counting unit before using those formulas. I'd count distinct buying enquiries, because several contacts discussing the same purchase shouldn't create several apparent sales chances. Record the contacts against that enquiry rather than inflating the denominator.

Keep direct sales enquiries separate when reviewing marketing-qualified conversion. You can include them in the wider sales report, but label their route so the team knows which enquiries went through marketing qualification.

Alongside conversion, show the number awaiting review, overdue next actions and the reasons enquiries were returned. Assign someone to investigate the records behind an unusual change before deciding what it means.

How do you avoid misleading monthly conversion figures?

Compare enquiries from the same starting group and allow time for their outcomes to develop. Dividing this month's SQLs by this month's MQLs can mix enquiries that arrived at different times.

For mql vs sql reporting, start with the enquiries that became MQLs during a chosen period. Follow those same records into sales acceptance and opportunity creation. Show how many remain unresolved rather than treating them as failures.

As one hypothetical example, suppose a fully reviewed cohort contains 40 MQLs, of which 10 became SQLs. Four of those became opportunities and one opportunity was won. The conversion rates are 25%, 40% and 25% respectively. Those figures illustrate the calculation, they aren't targets for your business.

Use your recorded sales cycle to decide when a cohort is old enough to assess. Until you've collected that history, label the report as provisional (especially if you're tempted to put it in a board pack).

Record when a qualification rule changes. Compare cohorts using the same rule, or flag the difference clearly. Otherwise, you might attribute a change to the new hire when the team has simply changed which enquiries count.

What should you check before blaming lead quality?

Check the records at the point where progression slows. A lower conversion rate tells you where to investigate, but you still need the qualification notes and follow-up history to decide what to change.

If MQLs are waiting for review, resolve ownership or sales capacity before asking marketing to generate more. If sales is reviewing them and repeatedly recording a service mismatch, check the campaign, website promise and marketing qualification rule.

If accepted SQLs aren't becoming opportunities, inspect the sales notes. Check what need was confirmed, what was offered and whether the buyer agreed to a next step. Don't send every stalled record back to marketing without that review.

I'd use mql vs sql to locate the work needing attention, because a single blended conversion rate gives a new hire very little to act on. Compare sources separately once you have enough reviewed records to make the comparison useful, and keep the unresolved count visible.

If the problem starts before qualification, use the broader checks in why marketing spend is not generating leads. This qualification report begins when an enquiry arrives, so it won't explain a missing enquiry by itself.

How should these numbers affect the marketing hire?

Use the stage rules to define the job, then agree what the new hire owns. They might own campaigns, website enquiries and marketing qualification, while someone else owns sales acceptance, proposals and closing.

Give them the baseline report, the qualification definitions and the unresolved records. Ask them to assess those records before agreeing improvement targets. Don't invent a target percentage because it looks tidy in a job description.

Treat mql vs sql as a shared operating agreement when judging the role. A useful scorecard should show qualified enquiries, progression into sales and opportunities, plus the follow-up work owned elsewhere. Record any changes to the definitions during the review period.

Use the wider decisions in what to put in place before you hire a marketing director to assess the role's authority and remit.

If the definitions and follow-ups already work, and you need senior judgement and team management, I'd hire the leader because that is the job you need done. You don't need Founder Engine to relabel a functioning CRM. An agency can also be the right choice when the brief is clear and someone inside the business owns the handover.

What else should you decide before hiring?

Do we need lead scoring before we can qualify enquiries?

No. Start with explicit evidence and a recorded decision. I'd add scoring only when you've identified a repeated assessment it would help the team make, then check that it supports the agreed qualification rules.

Should budget always be required for an SQL?

Make that decision according to what sales needs to know before accepting the enquiry. You might require an affordability discussion rather than an approved budget, particularly when the proposed scope hasn't been agreed. Write down which evidence is required and which can be collected later.

Should existing customers go through the same stages?

Keep renewal and additional-work enquiries identifiable so you can report them separately from new-customer enquiries. You can apply the same evidence rules where they fit, but agree which route counts towards the new hire's responsibilities. Don't let a change in customer mix silently change their scorecard.

If agreeing mql vs sql has exposed gaps in qualification, follow-ups or reporting, The Growth Install can address those within its agreed scope. It runs for 90 days and installs three agreed growth workflows on your own accounts, with tracking and a dashboard. The work includes the people who will own those workflows, and you keep ownership of the accounts and systems.

If you want help working out where growth is getting stuck, talk to Founder Engine.