Lead management: MQL, SQL and the handover

What does a lead management process record?

A lead management process records what a person asked for, whether the business can help and what should happen next. The record should preserve the customer's context as responsibility moves between teams.

Distinguish a person from an opportunity. Several people may participate in one organisation's purchase. One person may also make different enquiries over time. A database that treats every form submission as a separate deal will exaggerate demand and create duplicated contact.

Separate lifecycle stage from working status. Lifecycle describes a broad relationship; status can describe whether the team has attempted contact, is waiting for information or has scheduled a conversation. The opportunity records a specific potential transaction.

These distinctions support the wider sales and marketing agreement. The purpose is to help the customer progress appropriately, not to create a complex vocabulary that only the CRM administrator understands.

Why do MQL and SQL definitions need explicit evidence?

Explicit evidence prevents teams from changing the meaning of qualification to meet a target. A label should summarise an assessment that another person can understand and check.

HubSpot's lifecycle documentation, updated in July 2026, describes MQL and SQL in terms of marketing and sales qualification. It also distinguishes lead status within its lifecycle approach. These are platform definitions; the business still needs to specify its actual criteria.

Google Ads' qualified and converted lead guidance, checked in October 2026, supports measuring stages beyond the initial online interaction using offline qualification information. The marketing implication is that form volume need not be the final success measure. Poorly defined qualification, however, remains poor data when sent back to an advertising platform.

Salesforce's guidance on sales stages allows stages to reflect a business's own process. A tool's flexibility makes governance more necessary, because custom fields cannot decide what evidence the team should require.

How do you build a reliable lead handover?

Design the path from enquiry to outcome, then test it manually before relying on automation. Every stage should have an entry condition, owner and exit condition.

1. Capture the customer's stated need

Ask only for information needed to respond or determine suitability. Explain what happens after submission. A form promising a quotation should not silently enrol the person into an unrelated sequence of sales messages.

Preserve the source page, relevant offer and the person's own description. Sales should not have to ask the customer to reconstruct a context the business already collected. Keep access and retention proportionate to the purpose.

2. Check duplicates and eligibility

Identify whether the enquiry belongs to an existing customer, active opportunity or previous conversation. Route service questions to support rather than counting them as new sales demand.

Check objective eligibility such as service area or product requirements. Avoid using weak proxies to make unsupported judgements about a person's suitability. If a criterion matters commercially, explain it and verify it directly where appropriate.

3. Define MQL evidence

An MQL definition should combine relevant fit with a reason for sales involvement. A direct request for a suitable service may qualify immediately; passive engagement may require more context.

For a hypothetical business software provider, the criteria could include a relevant company need and an explicit request to discuss implementation. This is a process example, not a universal qualification standard. Different offers require different evidence.

Do not allow an arbitrary score to conceal the criteria. A total can be useful for prioritisation, but the salesperson should still see which signals produced it and whether any disqualifying condition exists.

4. Route to an accountable owner

Use rules that reflect territory, language, product and capacity. Record assignment time and acceptance. Define the fallback when a person is absent or the destination queue is unattended.

Test exceptional routes: a missing postcode, an existing account, a duplicate enquiry and a request submitted outside service hours. These cases often reveal gaps hidden by the ideal demonstration record.

5. Qualify the sales conversation

Sales should investigate the need, appropriate stakeholders, timing and conditions for a viable purchase. Record what the customer actually confirmed rather than filling required fields with assumptions.

An SQL should represent a useful conclusion from this work. It need not imply that all commercial uncertainty is resolved. Define separately when a genuine opportunity is created and what supports its stage and estimated value.

6. Record the next action and outcome

Every active record should have a meaningful next action or a documented waiting condition. “Follow up” is incomplete without a reason, owner and appropriate timing.

Use clear outcomes for unsuitable, deferred and unreachable records. A customer who asks to return later should not receive the same process as someone who cannot be served. Where ongoing communication is appropriate, respect the person's preferences and the relevant rules for the channel.

Where does lead management break down?

It breaks down at exceptions and departmental boundaries. The visible form may work while the routing, notification or follow-up behind it fails.

In Indian businesses with regional branches or dealer networks, central marketing must know whether the assigned location received and accepted the enquiry. A spreadsheet sent to a partner is not proof of customer contact. Agree what feedback is realistically available and how it will be returned.

Phone and messaging enquiries require the same basic discipline as website forms. Record enough context to prevent duplication and missed promises, without copying unnecessary personal details into every system.

Account-based sales need careful aggregation. If several contacts belong to one purchase, connect them to the relevant account and opportunity. Otherwise, stage conversion and pipeline totals can look stronger simply because the buying group is larger.

When should qualification rules change?

Change qualification rules when observed outcomes show they are missing suitable buyers or forwarding unsuitable ones. Review them after material changes to the offer, audience or sales capacity.

In week one, trace recent enquiries from capture to outcome. In week two, agree definitions and repair routing. During the first 30 days, review exceptions manually and check whether different team members classify the same examples consistently.

Do not rewrite criteria halfway through a campaign without recording the change. A higher SQL rate after relaxing the definition is not evidence that marketing improved. Preserve enough history to compare like with like.

Who should own the lead management system?

A designated operations owner should maintain the process, while sales and marketing jointly approve qualification definitions. Individual sales owners remain responsible for appropriate action on assigned records.

Marketing owns accurate acquisition context and the promise made before submission. Sales owns qualification evidence and outcomes. Technical owners maintain integrations and monitor failures. Privacy and legal specialists should review relevant data and communication practices.

Leadership should resolve capacity conflicts. If the team cannot handle demand, the answer may be to adjust spending, staffing or service expectations. Relabelling unattended enquiries does not solve the problem.

What should an exception report show?

Show records without an owner, overdue actions, failed integrations and inconsistent stage evidence. Give each exception a responsible person and a route to resolution. Review the oldest unresolved cases as well as the newest arrivals, because fresh demand can otherwise hide a growing backlog. Keep the report focused on action instead of using it to produce another unexamined lead-volume total.

My view

I would start with a small number of stages that people use consistently. The trade-off is less apparent sophistication than an elaborate scoring model, but a clearer account of what actually happened.

I would also review abandoned and unresolved records, not only wins. They reveal where the business loses context, creates confusion or leaves a customer waiting.

Qualification should explain the next action, not merely improve the funnel chart.

Start with the oldest unattended enquiry

Find an enquiry that has no clear next action. Establish what the customer requested, who owns it and what prevented progress. Repair that path, then test the same route with a new enquiry before expanding automation.