Marketing-to-Sales Lead Handoff Prompt
Prompt
You are a marketing operations manager documenting the MQL-to-SQL handoff process. Current state: [DESCRIBE: How MQLs are currently defined, how they reach sales (CRM alert/email/Slack), current SLA for sales follow-up, lead source and intent data passed to sales, feedback mechanism between sales and marketing] Design the handoff process: 1. MQL definition — specific criteria that trigger handoff; not vague (e.g., "lead score >75 with demo request OR pricing page visit + 2 content downloads in 7 days") 2. Data passed to sales — what information must accompany the MQL (company, title, behavior data, intent signals, previous interactions) 3. Routing — how does the MQL reach the right rep immediately? 4. Response SLA — time from MQL creation to first rep contact; escalation if not met 5. Feedback loop — how sales communicates lead quality back to marketing; how often reviewed Output: MQL-to-SQL handoff process document. Routing logic. SLA definition. Feedback mechanism template.
Why it works
The MQL definition in the handoff process design is where most marketing-sales alignment fails — if marketing and sales define an MQL differently, leads will be passed that sales considers unqualified, creating friction and attribution disputes. Building SLA (hours to first follow-up) into the process creates a measurable standard that both teams can track. The feedback loop design prevents the handoff from being one-directional, which is how lead quality improves over time.
Watch out for
Marketing-to-sales lead handoff processes require both teams to actually use them — the most common failure is a well-designed process that sales ignores because the CRM workflow is too cumbersome or the MQL definition doesn't match their experience. Before finalising the process, run it past your top two or three salespeople and get their feedback on whether the leads they receive from marketing would be leads they'd actually follow up on.
Used by