Skip to content
Vanthis

ResourcesInbound

Lead Lifecycle & MQL to SQL

Agree when a lead is ready for sales, hand it over on time, and get every lead accepted or recycled with a reason.

Use in Vanthis

14 steps2 decisions

HubSpotClaudeHubSpotClaudeHubSpotHubSpotHubSpotHubSpotClaude
Shown with

This playbook agrees with sales when a marketing lead is ready, hands each ready lead to one owner on time, and gets every lead accepted or recycled with a reason. Fit and engagement are scored separately, nurture runs only where the market allows it, and a regular review tunes the versioned rules.

Who does what

  • GTM Lead sponsors the reset, decides when marketing and sales disagree, signs the agreement and approves threshold changes.
  • Marketing Ops defines the stages, builds the scores and the routing, recycles every no and prepares the review.
  • Sales Manager reviews the stage definitions, signs the agreement and decides changes in the review.
  • SDR accepts or rejects each MQL in time, works the cadence and proposes the SQL.
  • Account Executive owns dream and tier 1 accounts, confirms the SQL and creates the opportunity.
  • CRM Admin reviews the stage definitions and the field values behind them.
  • Privacy Lead checks the basis for scoring and owns the consent gate before nurture.
  • Agent Claude or ChatGPT, drafts the agreement, backtests the threshold and prepares the review.

What you need

  • Lead and stage history from the last two to four quarters.
  • The ICP map with its tiers, from ICP & TAM Mapping.
  • A CRM, HubSpot or Salesforce with Account Engagement, for stages, scores and routing.
  • A knowledge base for the agreement and the reviews, and an agent for the drafts.

Some answers are yours to set in the agreement:

  • The times to accept and to first touch for each fit tier.
  • The short list of rejection reasons, each marked recyclable or not.
  • How many MQLs per week the SDR team can work.
  • Which markets are in scope, and the consent basis for nurture in each.

1Agree the rules

  • Start a lead handoff reset
  • Define every lead stage
  • Write the handoff agreement

The reset starts with one GTM Lead who decides when marketing and sales disagree, a fixed scope of markets, lead sources and teams, and a baseline: lead counts per stage, time in stage and conversion for the last two to four quarters. It also counts the gaps, such as leads with no owner, leads stuck in a stage beyond a month and MQLs with no recorded outcome.

Marketing Ops then writes one meaning, entry rule, exit rule and owner for every stage:

  • Two fields: the lifecycle stage for where the person is, and a lead status for what sales does now.
  • The core stages: subscriber, lead, MQL, SAL, SQL, opportunity and customer, plus recycled and disqualified off the path.
  • One owner per stage, so no lead sits between teams, and the exact field value for every stage in the tools.
  • SQL in sales words: criteria such as need, authority, budget and timing.

The agent drafts the handoff agreement from these definitions. It writes both sides, what marketing owes sales and what sales owes marketing, sets the times to accept and to first touch per fit tier, and keeps the reason list to about six entries, each marked recyclable or not. A wrong owner means reassign, never reject. Both leaders sign and date it.

2Score the leads

  • Score fit and engagement separately
  • Set the sales-ready threshold

Marketing Ops builds two scores instead of one blended number:

  • Fit from the account's tier in the ICP map plus role, seniority and department.
  • Engagement from meaningful actions, with most points for event attendance and contact or pricing pages and few for email clicks.
  • Negative points and decay for careers pages, competitors or students, and caps so one repeated action can never make a lead sales-ready.
  • One label such as A1, with fit from A to C and engagement from 1 to 3.

The agent backtests the threshold on past leads and compares the opportunity rate above and below it. Fit is the gate and engagement the trigger, no single action crosses the threshold, and the expected MQLs per week must fit the SDR hours in the agreement. Customers and accounts with an open opportunity go to the account owner instead of becoming MQLs. A vendor example is no threshold; without enough history for a backtest, the threshold is marked as a hypothesis and reviewed after four weeks.

3Hand over to sales

  • Hand each ready lead to sales
  • Does sales accept the lead?
  • Qualify the accepted lead
  • Is there a real opportunity?
  • Create the opportunity
  • Opportunity created

When a lead becomes an MQL, the CRM checks it for duplicates and existing customers or deals, gives it one owner and starts the acceptance clock in business hours. Dream and tier 1 accounts go to the named Account Executive, the rest to the SDR pool, and the owner gets the top score reasons, recent actions and account context. A breach is escalated as the agreement says.

The owner then decides inside the agreed time:

  • Accept when the company is right, the persona plausible, the contact data works and the lead is not already engaged.
  • Reject with one listed reason and a short note.
  • Reassign instead of rejecting when there is no time, so rejection data stays about quality.

An accepted lead gets its first touch inside the agreed time, every attempt is logged, and the SDR asks the agreed SQL questions on permitted channels only. When the written criteria are met, the Account Executive confirms the SQL and converts it onto the existing account, carrying the lead source, MQL type, score label and campaign onto the opportunity.

4Recycle and learn

  • Recycle or close with reason
  • Review rejections and conversions
  • Handoff rules reviewed

Every rejected or unqualified lead ends with a stage and a reason. Timing reasons such as bad timing, no budget yet or unreachable are recycled with a return date and an engagement reset; fit and data reasons are closed. Before any nurture email, the Privacy Lead's gate applies:

  • Germany and Austria need double opt-in consent or the existing-customer exception.
  • The US needs an opt-out that has not been used.
  • An objection stops all marketing, including profiling, and goes onto the suppression list.

The agent prepares the review: conversion and median time from MQL to SAL, SQL and opportunity, the top rejection reasons with examples, and the share of MQLs accepted and first-touched on time per owner. Stale leads are disposed of or reassigned, weights, threshold or agreement change only through a new dated version, and long-inactive leads are deleted or anonymized while consent proof and suppression entries stay. The review runs weekly for the first four weeks, then as agreed.

Compliance checks

The playbook carries checks for the EU, Germany, Austria and the US. Four examples:

  • In Germany, detailed advertising scores built with external data usually need consent, so the Privacy Lead checks the basis for scoring.
  • Nurture email to German and Austrian leads needs double opt-in consent or the existing-customer exception.
  • Under Art. 21 GDPR an objection ends direct marketing and the profiling behind it.
  • Under Art. 5 GDPR long-inactive leads are deleted or anonymized, while consent proof and suppression entries stay.

They are checks for whoever owns privacy on your team and no legal advice.

Run it in Vanthis

Pick your CRM and agent above the Canvas, and the steps and guides on this page follow your choice. In Vanthis the playbook becomes your own Motion with that stack. Your agent, Claude or ChatGPT, asks which tools your team uses, then works through it step by step, and the GTM Lead approves every change to the rules. To run it somewhere else, download it as Markdown or as an agent skill.

Use in Vanthis