Handoff playbook · Operator diary · 2026

MQL-to-SQL handoff when marketing and sales are the same person

Every MQL-to-SQL guide on the open web assumes two teams. Marketing hands a lead to Sales, formal contract, SLAs, dashboards, weekly review. When you are the entire GTM team, the handoff still exists — it just collapses inside your own calendar. The 4:32 PM you that captured the demo request is a different person from the 9:15 AM you that has to decide whether to call the lead back. Without a structured handoff, “Marketing Me” books leads “Sales Me” never gets to.

The 5-step framework

Step 1 — Accept that the handoff does not disappear when the team is one person

Most MQL-to-SQL content assumes Marketing hands a lead to Sales — two teams, formal contract, SLAs, dashboards. When you are the entire GTM team, the handoff still exists; it just collapses inside your own calendar. The 4:32 PM you that captured the demo request is a different person from the 9:15 AM you that has to decide whether to call the lead back. Without a structured handoff, "Marketing Me" books leads "Sales Me" never gets to. The fix is not to skip the handoff — it is to formalize it as a checklist you run against yourself.

Operator tip: The clearest signal you need a structured handoff: you find old demo requests in your inbox that you never followed up on. That gap is the handoff failing. The leads were qualified enough to request; the time-shifted "sales you" did not get the handoff in time.

Step 2 — Write the MQL definition for yourself, the same as for a real team

MQL = Firmographic match AND Behavioral signal. Both required. Firmographic match means ICP Tier 1, 2, or 3 (per your `icp-builder` definition). Behavioral signal means at least one of: demo request submitted, pricing page viewed + 1 other intent action, trial / freemium signup with work email, 3+ content downloads in 30 days from ICP-matched company, inbound meeting booked. The reason you write this down even as a solo operator: it forces you to disqualify before responding. Without the criteria, every inbound feels like a possible deal and you waste 30% of your week on misfits. Sub-tier the definition: MQL-A (Tier 1 + high-intent) → 5-min response; MQL-B (Tier 1-2 + medium-intent) → 1-hour response; MQL-C (Tier 2-3 + low-intent) → 24-hour response OR nurture.

Operator tip: The MQL definition is also your SDR script when you eventually hire. The artifact you write today is what the rep absorbs in week 1. Build it for the future hire, not just for current you.

Step 3 — Run the 5-minute SLA against yourself for MQL-A leads

Buyer intent decays in hours. A prospect who requests a demo at 2:47 PM is in research mode RIGHT NOW. By tomorrow morning they have moved on, gotten distracted, started looking at a competitor, or forgotten why they wanted the demo. The lift from a 5-minute response vs. 24-hour is 60-70% on conversion. As a solo founder, the discipline is to either drop what you are doing for MQL-A leads or accept a lower conversion rate. The pragmatic middle: set up a Slack / email notification that pings you on every demo request, screen for MQL-A in 30 seconds (Tier 1 firmographic + high intent), respond to MQL-A within 15 minutes. MQL-B / MQL-C can wait until your next focused-work break.

Operator tip: Get the notification working before you optimize anything else. The single biggest reason solo founders miss inbound is that they do not see the lead until 2 hours later. Tools that work: HubSpot Free CRM + their notification app on phone; Slack integration on your form tool; or a $20/mo tool like Salesflare that pings on form submit. Spend 30 minutes setting this up — it pays back the first time you book a meeting that would have died waiting for tomorrow.

Step 4 — Run the same qualification call the SDR would run

When the MQL responds and you get them on a call, run discovery as if you were the SDR qualifying for a future AE. 6-question script (see /discovery-call-no-bant-founders), 30-minute structure, MEDDPICC fill, dated next step. The temptation as a solo founder is to skip the discovery and demo immediately because you are excited the lead is real. Resist it. The discovery call is where you decide whether this lead becomes a real opportunity or gets disqualified. Demoing without discovery converts at half the rate of demo-after-discovery — because half the demos are misfit and you wasted both your time and the prospect's.

Operator tip: The "I will skip discovery this once" exception is almost always a misfit lead in disguise. Strong fits welcome the discovery call ("makes sense, let us get on a call first"). Misfit leads push for immediate demo because they want to see if your product matches a need they have not articulated. The push to skip discovery is itself a qualification signal.

Step 5 — Capture disqualification reasons even when "the handoff" is to yourself

When you mark a lead disqualified, capture the reason — even though you are both the disqualifier and the would-be receiver. The reasons: (a) the reason data feeds your ICP refinement (icp-builder skill) — patterns across 10-20 disqualifications surface ICP edge cases you have not addressed; (b) the reason data feeds your source-quality analysis — which lead sources produce real opportunities vs. junk; (c) when you eventually hire the first SDR or AE, the disqualification reason history is the training data. Acceptable reasons: out of ICP, competitor in seat, wrong persona, no real intent, geography out of scope, pricing out of range, bad data. Skip the "Other" option — it produces meaningless data. If you cannot pick a reason from the list, the list needs to grow.

Operator tip: The disqualification reason field is also a forcing function. It is uncomfortable to mark a lead "no real intent" when you wanted them to be real. Marking it anyway is the discipline. Three weeks of honest disqualification data tells you more about your motion than three months of pipeline-padding optimism.

Three approaches considered

ApproachStructurePro caseWhy it loses
Structured solo handoff (MQL definition + 5-min SLA + disqualification capture)
Chose this
Written MQL definition (firmographic AND behavioral) with A/B/C tiers, 5-min response SLA on MQL-A, full discovery call before demo, captured disqualification reasons on every lead that does not convert.Treats the handoff as a real process even with no second person. Builds the artifact that becomes the SDR/AE training material when you hire. Disqualification data feeds ICP refinement and source-quality analysis. Conversion rate matches what a structured team produces (because the structure is what produces it, not the team).Requires discipline. The 5-min SLA on MQL-A means dropping work for inbound. The disqualification capture feels like overhead at low lead volume. Both pay off long-term but cost short-term focus.
Skip the handoff because "I am one person"Respond to leads when you have time. No MQL definition. No SLA. Memory-based qualification.Zero structural overhead. Maximum flexibility.Misses 60-70% of conversion potential on high-intent leads (the SLA decay math). Wastes 30% of your week on misfit leads because there is no qualification screen. When you hire the first SDR, you have no artifact to hand them and they re-build from scratch — which means re-learning the same lessons you already learned but did not document.
Outsource handoff to a fractional SDRHire a fractional / part-time SDR for $2-4K/mo to handle inbound qualification.Offloads the response-time SLA from the founder. SDR can hit 5-min response during business hours. Fractional setup is cheaper than full-time.At pre-revenue, $2-4K/mo is real burn for a function the founder can do in 2-3 hours/week with structured handoff. Fractional SDRs also do not know your product or ICP at the depth the founder does, so qualification quality drops. Better at $1M+ ARR when inbound volume justifies the cost.

Common mistakes

Related operator reading

FAQ

Three reasons: (1) it forces qualification screening before you respond to a lead — without the criteria, every inbound feels like a possible deal and you waste 30% of your week on misfits; (2) the artifact becomes the SDR/AE training material when you hire — building it now means not re-learning the same lessons later; (3) it forces honesty about which leads are real vs. wishful. The MQL definition is not just for the handoff to a future team — it is the screen between Marketing You and Sales You today.

Two adjustments: (a) define "business hours" honestly — if you only sell during 9 AM - 12 PM and 7 PM - 9 PM, set those as your SLA window and run after-hours auto-responders for everything else; (b) tier your leads — MQL-A (Tier 1 + high-intent) gets the 5-min SLA, MQL-B / MQL-C can wait. The realistic constraint at pre-revenue is that your inbound volume is low enough that MQL-A leads might be 1-2 per week, which is feasible to respond to in 15 minutes during your active sales window.

Demo request submitted (top signal), pricing page viewed + 1 other intent action in last 7 days, trial / freemium signup with a work email (not gmail.com), inbound meeting booked via calendar link, 3+ content downloads in last 30 days from same ICP-matched company. Single page-views or one ebook download from anonymous traffic do not count. The bar is "this person took an action that took deliberate effort to opt into a sales conversation."

When you hire your first SDR or AE. At that point, the MQL definition + disqualification reason picklist + SLA timing all carry over verbatim — they become the contract between the new person and you. The artifact you built for yourself becomes the artifact you hand them in week 1. Most solo handoffs that fail to graduate fail because the founder built no artifact, then has to re-build it under pressure when the SDR starts and they have nothing to hand them.

No, but it helps. The Notion pipeline (see /pipeline-review-pre-revenue-no-crm) is enough for the first 15 leads. Add a "Source" field and a "Disqualified reason" field to capture the data you would otherwise need a CRM for. Migrate to HubSpot Free or Pipedrive at deal 15 or first hire, whichever comes first. The handoff structure does not change when you migrate — only the storage medium.

Yes, but with a nurture flow rather than a 1:1 response. MQL-C = Tier 2-3 ICP + low-intent action (single content download, anonymous page view that converted on form). Auto-enroll them in a 5-touch educational email sequence. The conversion rate on MQL-C → SQL is 1-3%, so any time you spend on a 1:1 response is poorly invested. The nurture flow does it at scale.

HubSpot / Marketo lead scoring is a points-based heuristic — assign points for actions, score crosses a threshold = MQL. At your scale, points-based scoring is overengineered. The MQL definition (firmographic AND behavioral with explicit signals) is more accurate at low volume because it does not rely on calibrating point weights. Use the definition until you have 100+ inbound MQLs / month and the points-based system starts paying back.

The full mql-to-sql-handoff skill in the Playbook covers the 8-component framework: MQL definition with sub-tiers, SQL acceptance criteria, lead scoring rubric, routing rules (round-robin / territory / skill / hybrid), SLAs with after-hours policy, disqualification flow with reason picklist, Marketing-Sales feedback loop, and gap-closure rules. The solo-operator version above is the pre-revenue cut. Graduate to the full framework when you hire your first SDR or AE.

Canonical URL: https://stackswap.ai/mql-to-sql-handoff-solo-founder