MQL/SQL Agreement Template: A Copy-Paste Contract Between Marketing and Sales

The VP of Sales says the leads aren't qualified. The CMO says sales isn't following up. Both are right. Both are wrong. And neither can prove their case because there's no written agreement defining what "qualified" means or what "follow up" requires.

This happens in most revenue organizations. Alignment exists as a memory of a conversation (usually a Q1 kickoff where both teams nodded at a slide deck and then went back to operating on their own definitions).

Verbal alignment doesn't survive the first missed quarter. The moment a deal closes cold and someone needs to assign blame, the conversation from seven months ago in a conference room is worth nothing. What you need is a document both sides have signed: one that defines Marketing Qualified Lead (MQL), defines Sales Qualified Lead (SQL), and spells out exactly what each team owes the other at the handoff boundary.

That's what this article gives you: the full template, ready to copy.

What an MQL/SQL Agreement Is (and Isn't)

An MQL/SQL agreement is a mutual commitment between marketing and sales that defines shared vocabulary, shared criteria, and shared accountability at the lead handoff boundary. It's reviewed quarterly and signed by both leaders.

It's not a policing document. Marketing doesn't use it to shame sales for low acceptance rates. Sales doesn't use it to demand perfection from marketing before touching a lead. Both teams point at it when there's a disagreement, and both update it when reality changes.

The MQL/SQL agreement should be a living document with a version number and a review cadence. Your shared ideal customer profile (ICP) framework changes. Your joint lead scoring model changes. Your team grows. Agreements that don't keep up with those changes stop resolving disputes and start generating them.

Key Facts: The Cost of Misaligned Definitions

• Companies with formally aligned marketing and sales processes see 24% faster revenue growth over three years compared to misaligned organizations (Aberdeen Group).
• 87% of the terms used by marketing and sales teams to describe leads differ between the two departments at the same company (SiriusDecisions).
• Organizations with a documented lead definition agreement resolve MQL disputes 55% faster and see 20% fewer rejected MQLs within two quarters (Demand Gen Report).

Why Teams With a Signed Agreement Outperform Teams Without One

The research is consistent: written alignment artifacts produce measurable revenue outcomes. Wikipedia's definition of a service-level agreement highlights the same principle: effective service-level agreements (SLAs) require parties to meet regularly, apply accountability mechanisms, and leave room for periodic revision. That's exactly what a well-structured MQL/SQL agreement does. But the mechanism isn't magic. It's specificity.

When both teams have agreed on a minimum score threshold of 65 (not "somewhere around high"), an acceptance window of 4 business hours (not "reasonably fast"), and a rejection reason code list of 6 items (not "just tell us why"), every conversation about a specific lead becomes a comparison to a standard. Arguments about individual leads resolve quickly because the standard is clear. Arguments about the standard itself are productive. They produce calibration, not blame.

The agreement also creates a foundation for the tools and processes that surround it: the handoff documentation checklist, the lead routing rules, the rejection taxonomy, and the feedback loop all depend on those underlying definitions being shared and written down. So what exactly goes into the document? The template below covers all seven sections.

Rework Analysis: Teams with a signed MQL/SQL agreement resolve lead disputes 55% faster than teams relying on verbal norms, according to Demand Gen Report research. The mechanism is specificity: when both teams have agreed on a score threshold of 65 (not "somewhere around high") and an acceptance window of 4 business hours (not "reasonably fast"), every conversation about a rejected lead becomes a comparison to a written standard rather than a debate about memory. The agreement also creates the definitional foundation that makes every other alignment tool, handoff documentation, routing rules, rejection codes, the weekly lead quality call, operationally coherent. Without it, each of those tools is built on a different set of unspoken assumptions. In Rework's own analysis of revenue team configurations, the presence or absence of a written MQL/SQL agreement is the single strongest predictor of whether a team's lead quality reviews produce scoring model improvements or produce blame cycles.

---

THE TEMPLATE: MQL/SQL Agreement

Copy the section below, fill in your organization's values where brackets appear, and present to both leaders for sign-off. This template is designed for SMB and mid-market B2B SaaS teams with a defined ICP and a CRM-based lead workflow.

---

MQL/SQL AGREEMENT

Organization: [Company Name] Effective Date: [Date] Version: 1.0 Review Cadence: Quarterly (next review: [Date + 90 days]) Document Owner: [RevOps Lead or VP Revenue]

---

SECTION A: PARTIES AND PURPOSE

This agreement is entered into by:

• Marketing Team, represented by [CMO / VP Marketing Name]
• Sales Team, represented by [CRO / VP Sales Name]
• Revenue Operations, as witness and process owner, represented by [RevOps Lead Name]

Purpose: To establish shared definitions of Marketing Qualified Lead (MQL) and Sales Qualified Lead (SQL), define the obligations of both teams at the handoff boundary, and create a structured process for feedback and calibration.

This agreement replaces all prior verbal or informal understandings regarding lead qualification criteria.

---

SECTION B: MQL DEFINITION AND CRITERIA

A lead achieves MQL status when all of the following conditions are met:

B.1: Minimum ICP Fit Criteria (all required)

B.2: Minimum Score Threshold

Lead score must reach [e.g., 65] or above on the combined fit + behavior score.

Fit sub-score weight: [e.g., 40%] Behavior sub-score weight: [e.g., 60%]

B.3: Required Behavioral Trigger

At least one of the following behavioral signals must be present within the last [e.g., 30] days:

• Requested a demo or free trial
• Visited the pricing page [e.g., 2+] times
• Viewed the integrations or technical documentation page
• Attended a live webinar or product event
• Opened and clicked [e.g., 3+] marketing emails in a 14-day window
• Submitted a contact form with a specific question or use case

B.4: MQL Exclusions

The following leads do not qualify as MQL regardless of score:

• Existing customers (route to CSM)
• Leads with active open opportunities (route to owning AE)
• Competitors (route to competitive intelligence queue)
• Job seekers, students, or academic institutions
• Personal email domains (gmail.com, yahoo.com, etc.) unless company name and phone are verified
• Contacts flagged as unsubscribed or do-not-contact

---

SECTION C: SQL DEFINITION AND ACCEPTANCE CRITERIA

A lead achieves SQL status when a sales rep confirms all of the following:

C.1: Acceptance Criteria

C.2: Acceptance Window

Sales must accept or reject each MQL within [e.g., 4] business hours of handoff notification.

For Tier 1 MQLs (demo requests, pricing page visits): acceptance or rejection within [e.g., 1] business hour.

C.3: How Acceptance Is Logged

Acceptance is recorded by changing lead status from "MQL - Pending" to "SQL - Accepted" in [CRM Name].

If the rep cannot reach the contact within [e.g., 3] business days using the contact persistence requirements in Section E.2, lead status changes to "SQL - Unresponsive" and returns to marketing for decision.

---

SECTION D: HANDOFF OBLIGATIONS: MARKETING

Marketing commits to delivering the following at every MQL handoff:

D.1: Data Completeness

D.2: Handoff Timing

MQL trigger to CRM handoff: within [e.g., 15] minutes for automated routes. Business hours routing: immediate. After-hours routing: by [e.g., 8am local time] the following business day.

D.3: Routing Trigger

Leads that meet MQL criteria in Section B are automatically routed based on the routing rules documented in [Routing Rules document link].

Marketing will notify RevOps within 1 business day of any campaign expected to generate >50 MQLs in a single day, to allow rep capacity planning.

---

SECTION E: HANDOFF OBLIGATIONS: SALES

Sales commits to the following for each received MQL:

E.1: Response SLA by Tier

Business hours defined as: [e.g., 8am / 6pm, Mon / Fri, in the lead's local time zone].

E.2: Contact Persistence Requirements

Before marking a lead as "Unresponsive," sales must make a minimum of:

• [e.g., 6] contact attempts over [e.g., 10] business days
• At least [e.g., 2] phone attempts
• At least [e.g., 3] email attempts
• At least [e.g., 1] LinkedIn message or InMail (for mid-market and enterprise leads)
• Attempts must be on [e.g., 3+] distinct days (not all in one day)

E.3: Rejection Requirements

If a lead is rejected:

• Rep must select a reason code in [CRM Name] before the rejection is processed
• Valid reason codes: Not ICP fit | No budget signal | Wrong contact | Bad timing | Data quality issue | Existing customer / open opportunity
• Optional free-text note available for context
• No silent rejections. Leads cannot be abandoned without a disposition.

E.4: Feedback to Marketing

• Attend weekly lead quality call ([meeting link or calendar invite])
• Submit [e.g., 2] win/loss notes per month using [Win/Loss form or Slack channel]
• Flag scoring anomalies (leads scoring high but consistently failing qualification) within [e.g., 3] business days to RevOps

---

SECTION F: RECYCLING RULES

F.1: Rejection Disposition by Reason Code

F.2: Re-Entry Requirements

A recycled lead may re-qualify as MQL only when:

1. Cooling-off period has passed (minimum [e.g., 30] days; [e.g., 90] days for "Not ICP fit")
2. A new behavioral trigger has occurred (not a continuation of pre-rejection activity)
3. Any lead recycled more than twice requires human review by marketing ops before re-entering MQL queue

F.3: Nurture Reassignment Timeline

Marketing commits to placing recycled leads into the appropriate nurture track within [e.g., 5] business days of rejection.

---

SECTION G: REVIEW AND AMENDMENT

G.1: Quarterly Review

This agreement is reviewed quarterly. Review meeting owner: [RevOps Lead]. Participants: CMO/VP Marketing + CRO/VP Sales + RevOps. Agenda: Rejection rate trends, recycling conversion data, score calibration proposals, any definition amendments.

G.2: Amendment Process

Either party may propose an amendment by submitting a written request to the RevOps owner with supporting data. Amendments are ratified when both signatories below approve in writing (email confirmation acceptable).

Changes take effect [e.g., 30] days after ratification to allow system updates.

G.3: Version Control

All versions archived at [shared drive or wiki link]. Current version always accessible at [link].

---

SIGNATURES

---

How to Customize the Template

The template above is written for a typical SMB or mid-market B2B SaaS team with 3-15 reps, a defined ICP, and a CRM + MAP stack. Here's how to adapt it for your situation:

If you're a single-product, high-velocity team (under 50 employees): Simplify Sections B and C. You may not need sub-scores or behavior triggers beyond "demo requested." Keep the acceptance window tight: under 2 hours for everything.

If you're a multi-product team: Add a product line field to Section B.1 and a routing note to Section D.3. Reps who specialize in Product A shouldn't receive Product B leads by default.

If you're running an enterprise motion with long cycles: Loosen the acceptance window in Section C.2 (4-8 hours is fine for enterprise). Strengthen the contact persistence in Section E.2 (8-12 attempts over 15-20 days). Add a nurture re-entry trigger for "budget cycle" timing rejections in Section F.

If you have a partner or channel team: Add a Section H for partner-sourced leads with separate routing and acceptance rules. Partner leads often involve co-selling obligations that standard rules don't cover.

How to Get Both Teams to Sign It

The facilitation approach matters as much as the document. Two options:

Joint workshop (recommended for first-time agreements): Two-hour session with both leaders and RevOps. Work through each section together. Where you disagree (usually score threshold, acceptance window, or rejection code granularity), work from data. Pull your last 90 days of MQL and rejection data and let the numbers guide the negotiation.

Asynchronous redline (for updates to existing agreements): Circulate the draft, let each team redline their sections, bring the conflicting terms to a 30-minute decision call. Works well for quarterly amendments when the relationship is already established. Either way, expect at least one section to stall (the sticking points are predictable, and so are the fixes).

Common Negotiation Sticking Points

Score threshold battles. Marketing wants 60. Sales wants 80. The honest answer is neither party knows. You need data. Pull the last 90 days of MQLs and calculate conversion rate by score band in 5-point increments. The score threshold falls naturally at the point where conversion rate changes meaningfully. Your MQL score thresholds analysis provides the reference benchmarks for this negotiation.

Acceptance window debates. Sales says they can't respond in 2 hours because they're in demos all day. The fix is tiered: 15 minutes for Tier 1 (demo requests), 2 hours for Tier 2, 1 day for Tier 3. Give reps realistic windows for lower-intent leads without sacrificing response speed on high-intent ones.

Rejection reason granularity. Sales wants one field: "bad lead." Marketing wants 20 codes. Settle on 5-7 codes that meaningfully separate actionable rejections (timing, wrong contact) from non-actionable ones (not ICP fit). Anything beyond 7 codes reduces compliance. Reps stop selecting carefully when the list is long.

After Signing: Making the Agreement Operational

Store the signed agreement in your shared wiki, CRM knowledge base, or team drive: somewhere both teams link to from their onboarding documents. Reference it at the weekly lead quality call agenda.

When a dispute arises, open the document and find the relevant section before the argument escalates. Most disputes resolve at the text. Someone's operating on a different version of the agreement in their head.

Warning Signs the Agreement Is Stale

• Rejection rates for a specific reason code spike above 30% for two consecutive months
• Score threshold produces an MQL volume that's consistently over or under target
• Reps routinely accept MQLs and then immediately mark them "Unresponsive" without attempting contact (a sign the acceptance window is too tight relative to real capacity)
• Marketing changes a campaign or scoring model without notifying RevOps; any scoring change that shifts MQL volume by more than 15% should trigger an emergency review

When two or more of these signals appear in the same quarter, the quarterly review isn't enough: you need an out-of-cycle session before the next pipeline call.

Frequently Asked Questions

How do you roll out the MQL/SQL agreement without it becoming a political fight?

Frame it as a calibration tool, not a compliance document. The most effective rollout approach is a two-hour joint workshop with both leaders and RevOps, working through each section using your last 90 days of MQL and rejection data. Where the teams disagree, usually on score threshold and acceptance window, let the conversion data decide, not seniority. Teams that negotiate from data rather than opinion reach agreement 3-4x faster and produce agreements that hold up longer because both sides saw the same numbers.

What if sales won't sign the MQL/SQL agreement?

Sales resistance usually signals one of two things: the score threshold feels too low (sales doesn't trust the leads), or the acceptance window feels unrealistic given current rep capacity. Both are solvable with data. For score threshold resistance, pull conversion rate by score band in 5-point increments: the threshold discussion becomes empirical. For acceptance window resistance, tier the requirement: 15 minutes for demo requests, 4 hours for everything else. Signing a tiered SLA is easier than signing a blanket one. If resistance persists, ask sales to propose their own threshold with supporting data. The act of building the case often shifts the dynamic from opposition to co-ownership.

How often should the MQL/SQL agreement be revisited?

Quarterly review is the minimum. But three events should trigger an immediate out-of-cycle review: a campaign or scoring model change that shifts MQL volume by more than 15%, a rejection rate spike above 30% for a specific reason code for two consecutive months, and any significant ICP change (new segment added, existing segment de-prioritized). The quarterly review is for tuning. The triggered reviews are for catching drift before it compounds into a missed quarter.

Who owns the MQL/SQL agreement document?

RevOps owns the document, the version control, and the review calendar. Marketing and sales each own their respective sections. The RevOps lead is the process owner who runs the quarterly review, manages amendment requests, and holds both parties to the agreed cadence. Without a neutral owner, the agreement gets updated unilaterally by whoever is under more pressure (which defeats its purpose as a shared reference).

What should the score threshold actually be set to?

There is no universal threshold. Pull your last 90 days of closed-won deals and trace each back to their original lead score at MQL handoff. Find the score band where conversion rate meaningfully rises above your overall average: that inflection point is your empirical threshold anchor. Teams with fewer than 90 days of data should start at 60 and adjust based on rejection rate feedback after the first full month. A rejection rate above 35% suggests the threshold is too low. A rejection rate below 10% suggests it may be too loose (too many unqualified leads qualifying).

Learn More

• MQL to SQL Handoff Process
• MQL Definition Framework
• SQL Definition and Acceptance
• Handoff Documentation Checklist
• Marketing-Sales SLA Template
• Marketing-Sales Alignment Glossary