Marketing and Sales SLA: A Template That Ends the Lead Quality Argument

Most “bad leads” arguments aren’t about lead quality. They’re about two teams using the same words for different things. A marketing and sales SLA fixes that by writing down what each stage means, what each team commits to when a lead reaches it, and how both teams check the numbers every week.

Why lead quality disputes are really definition disputes

Listen closely to the argument and you’ll hear two definitions. Marketing counts an MQL as anyone who crossed a score threshold. Sales hears “MQL” and expects someone ready to talk budget this quarter. Each side is right by its own definition, and neither definition is written down.

So marketing optimizes for the number it’s measured on, and fit falls. Reps cherry-pick warm-looking leads and let the rest age out. And nobody can prove anything, because the CRM doesn’t record whether a lead was called or why it was rejected.

A written SLA turns the argument into questions the data can answer: Did the lead meet the criteria? Was it contacted in time? Why was it rejected? Then “the leads are bad” becomes something like “most rejections this month were below our minimum company size,” which is a targeting fix, not a feud.

What a marketing and sales SLA should contain

Keep it to one or two pages, in six parts:

1. Stage definitions: what MQL, SAL and SQL mean, with entry and exit rules.
2. Sales commitments: response time, follow-up attempts, disposition deadline. Owned by the head of sales.
3. Marketing commitments: MQL volume range, fit criteria, pipeline contribution. Owned by the head of marketing.
4. CRM mapping: which fields and values record each stage and outcome. Owned by marketing ops or RevOps.
5. Review cadence: who meets, when, and which report they use.
6. Escalation and changes: what happens when a commitment is missed, and how definitions change.

The last part is the one most SLAs skip. Without it, the document gets written, praised and ignored within two months.

Defining MQL, SAL and SQL in terms both teams accept

Every stage needs an entry rule the CRM can check and a named role that moves records through it.

• MQL (marketing-qualified lead): meets fit criteria (ICP attributes such as industry, company size, role and region) and has shown intent: a demo request, repeat pricing visits or a score threshold. Building a lead scoring model in HubSpot covers setting that threshold from closed-won data.
• SAL (sales-accepted lead): a rep has reviewed the MQL and agreed it’s worth working. This stage ends most arguments, because acceptance is a recorded decision, not a complaint after the fact.
• SQL (sales-qualified lead): a rep has confirmed a real need, a buyer or a path to one, and a plausible timeline. This is usually where an opportunity gets created.

Write criteria as fields, not adjectives. “Decision-maker” is an opinion. “Seniority is Director or above” is a rule a workflow can check.

The windows are examples; set yours from your sales cycle. If you also run a product-led motion, define PQLs alongside MQLs, as covered in product-qualified leads.

Sales commitments: response time, follow-up attempts and disposition reasons

Sales signs up for three things.

Response time by lead type. Hand-raisers (demo, contact and pricing requests) typically get a same-day response, often within the hour during business hours. Score-based MQLs can have a longer window, such as one business day. Pick numbers your team can hit consistently.

A minimum follow-up sequence. Define how many attempts a lead gets before it can be closed as “no response,” for example six touches over ten business days across phone, email and LinkedIn. Without this rule, “no response” often means “one email.”

Disposition reasons from a fixed list. Every MQL is accepted or rejected within the window, and every rejection carries a reason from a picklist, not free text:

• Not ICP: company too small, wrong industry or wrong region
• Wrong contact: no authority and no path to the buyer
• Student, job seeker, vendor or competitor
• Duplicate, existing customer or already in an open deal
• No response after the full follow-up sequence
• Not ready: timing or budget (recycle, don’t disqualify)

The picklist is how marketing learns. Rising “Not ICP” says targeting is off. Rising “No response” with low attempt counts says the follow-up rule is being skipped.

Marketing commitments: volume, fit criteria and pipeline targets

Marketing signs up for three things too.

Volume as a range sales can work. A worked example with round numbers: two SDRs who can each run about 120 new MQLs a month through the full sequence give you a ceiling of 240. Promising 400 means 160 leads go stale, and stale leads look like bad leads. Commit to a range, such as 180 to 240.

Fit. MQLs meet the agreed ICP rules, and “Not ICP” rejections stay below an agreed share. Unlike “better leads,” that’s measurable.

Pipeline, not just MQLs. Tie marketing’s main target to SQLs and pipeline from marketing-sourced leads, and work backward using your own trailing conversion rates. Hypothetically: a $600,000 quarterly pipeline target at a $30,000 average opportunity needs 20 SQLs. At a 40% SAL-to-SQL rate that’s 50 SALs, and at a 70% MQL-to-SAL rate, about 72 MQLs. MQL volume becomes the leading indicator, not the goal.

I set this funnel math up in the first month of most fractional CMO engagements, because every later budget and channel decision depends on numbers both teams have agreed to.

Putting the definitions into the CRM: lifecycle stages vs lead status

An SLA that lives in a document but not in the CRM is a wish. Reports have to use the same definitions, or the weekly review slides back into arguing over whose spreadsheet is right. Use two fields with different jobs:

• Lifecycle stage records how far a record has progressed: Lead, MQL, SQL, Opportunity, Customer. It moves forward, except for a deliberate reset when a lead is recycled. HubSpot is designed to move it forward only, so recycling needs a deliberate reset, usually handled by a workflow.
• Lead status records what sales is doing right now: New, Attempting, Connected, Recycled, Disqualified. It’s the working field and can move back and forth.

Salesforce follows a similar pattern: a status picklist on the lead while it’s worked, then conversion into a contact, account and opportunity at SQL.

Three build rules make the reports trustworthy:

1. Require the reason whenever status is set to Disqualified or Recycled.
2. Stamp every transition. HubSpot records when a record enters each lifecycle stage; for any transition your CRM doesn’t stamp, add date fields and set them with workflows.
3. Log activity automatically. Response time is the first logged call or email minus the MQL timestamp. If reps log activity by hand, you’re measuring data entry, not follow-up.

The weekly review that keeps the SLA honest

Thirty minutes, same day each week, with the heads of marketing and sales, marketing ops and the SDR lead. One CRM report, no side spreadsheets: MQLs vs the committed range, share dispositioned on time, median time to first touch, attempts before “No response,” rejections by reason, stage conversion rates, and marketing-sourced SQLs and pipeline vs target.

Run it in four blocks:

1. Compliance (5 minutes). Which commitments were missed. Numbers, not blame.
2. Rejections (10 minutes). Open five rejected leads and read them together. Either sales agrees a lead met the criteria and works it, or marketing agrees the criteria need tightening.
3. Conversion (10 minutes). Stage rates against the 4-week average, noting campaigns that explain a swing.
4. Actions (5 minutes). One change per team, with an owner and a date.

The SLA template

Copy this, fill in the brackets with both teams in the room, and have both leaders sign it.

• Scope: marketing-sourced leads for [segments, regions]; reviewed quarterly
• MQL: [fit rule] AND [intent rule]
• SAL: accepted or rejected by [role] within [X] business hours
• SQL: [qualification criteria]; opportunity created at entry
• Recycled and Disqualified: [rules]; reason required from picklist
• Sales response: hand-raisers within [X]; score-based MQLs within [X]
• Follow-up: [N] attempts over [N] business days before “No response”
• Marketing volume and fit: [X to Y] MQLs per month; “Not ICP” rejections below [X]%
• Pipeline: [N] SQLs and $[X] marketing-sourced pipeline per quarter
• CRM mapping: stage fields, status values, required fields, report link
• Review: weekly on [day] with [roles]
• Escalation: two missed weeks in a row go to [sponsor]; definition changes apply at quarter start

Common mistakes: vanity MQL targets and unenforced rules

• Paying on MQL count. A bonus tied to MQL volume gets you MQL volume. Keep MQLs as a leading indicator and put the real target on SQLs and pipeline.
• Rules nobody can see. If a commitment doesn’t appear in the weekly report, it isn’t enforced. Every line in the SLA needs a field, a timestamp or a metric behind it.
• Score-only MQLs. A high engagement score from a student or a competitor is still not a lead. Gate on fit first, then intent.
• Marketing writing it alone. If the head of sales didn’t co-write it, sales will treat it as a marketing document.

Get it built

If your pipeline meeting is still an argument about lead quality, I can write the SLA with both teams, build it into your CRM and run the first reviews until the habit sticks. Start with a Growth Audit, $1,500 fixed and credited if we continue. See pricing or get in touch.