Marketing-Sales Alignment: How to Write a Lead Handoff SLA

A lead handoff SLA (Service Level Agreement) is a mutual commitment that puts in writing how many leads, and of what quality, marketing will deliver to sales, and how quickly and with how many touches sales will follow up on them. A good SLA clarifies five things: lead definitions, acceptance criteria, response times, follow-up cadence and the recycling rule for rejected leads. Unless these five elements are tied to measurable fields in your CRM, the SLA remains a statement of intent.

In B2B SaaS companies, the tension between marketing and sales usually starts with the same lines. Marketing says, "We delivered 400 leads this month and nobody called them." Sales replies, "Half of those leads are students and the other half are competitors." Both sides are partly right, because there is no shared definition and no shared clock. In this article, we walk you step by step through how to write a lead handoff SLA from scratch, which numbers to start with, how to automate it in your CRM and how to roll it out in the first 90 days.

Why do you need a lead handoff SLA?

The lead handoff is the moment the marketing funnel meets the sales funnel, and it is where the most revenue is lost. A decision-maker's interest in your product cools within hours. They watch a competitor's demo, their internal priorities shift, or they simply forget they filled out the form. Every delay at the point of handoff wastes the budget marketing spent on that lead.

In an organization without an SLA, you typically see the following:

• Leads go unowned. A form was submitted but never assigned to anyone, or it landed with more than one rep.
• Quality debates can't be measured. Sales says "the leads are bad," but there is no data showing which criterion they fall short on.
• The feedback loop is broken. The reasons leads are rejected never reach marketing, so marketing keeps spending the same budget on the same channel.
• Cost calculations become misleading. Because leads that aren't followed up don't convert, channel performance looks worse than it really is. Calculating cost per lead (CPL) accurately in B2B only produces meaningful results in an environment where sales works leads consistently.

An SLA takes these issues out of the realm of personal arguments and turns them into process discussions. Instead of asking "who's right," you ask "which clause was breached."

Which definitions need to be settled before you write the SLA?

Definitions are where SLAs most often break down. If "qualified lead" means different things to the two teams, every response time you write loses its meaning. Start by defining the following stages in writing.

Lead stages

1. Raw lead (Inquiry): Anyone who fills out a form, downloads content or registers for an event. They haven't passed through any filter yet.
2. MQL (Marketing Qualified Lead): A lead that fits your ideal customer profile and crosses a defined engagement threshold. For example, a person at a company with 50–500 employees, in the target department, at manager level or above, who has had at least two meaningful interactions in the last 30 days.
3. SAL (Sales Accepted Lead): An MQL that sales has reviewed and accepted as "worth talking to." This stage is the heart of the SLA, because this is where responsibility changes hands.
4. SQL (Sales Qualified Lead): A lead with whom sales has held a first conversation and validated need, budget, timing and decision process. An opportunity is opened at this point.

How do you set the MQL threshold?

The MQL definition should be based on a scoring model, not intuition. Demographic fit (industry, company size, job title) and behavioral signals (pricing page visits, demo requests, webinar attendance) are evaluated together. We covered how to build this model in detail in our guide on building a B2B lead scoring model step by step. What goes into the SLA is not the model itself but its output, for example: "Leads scoring 100 points or more are considered MQLs."

High-intent actions such as demo requests and "talk to sales" forms should go straight to sales without waiting for scoring. Define these as a separate category in the SLA.

How do you write a lead handoff SLA step by step?

1. Define the scope and the parties

The first paragraph of the SLA states who the parties are and which leads it covers. Example:

"This agreement covers the handoff of all inbound and event-sourced leads between the marketing team and the SDR and AE teams. Outbound-sourced leads and expansion requests from existing customers are out of scope."

Also assign an SLA owner on each side. Typically, the demand generation manager takes this role on the marketing side and the SDR manager on the sales side. That way, when a breach occurs, it's clear who calls whom.

2. Write the acceptance criteria

Under what conditions is sales obligated to accept an MQL? Answer this question with a clear list:

• Corporate email address (excluding free email providers)
• Company located in a target country or region
• Falls within the ICP's industry and employee range
• A valid phone number or LinkedIn profile
• Not an existing customer or open opportunity

Sales cannot reject a lead that meets these criteria simply because they "don't like it." Conversely, marketing should not send sales a lead that doesn't meet them. Some of these criteria come from the form. You can find guidance on balancing which fields to ask on your form and which to leave to enrichment tools in our article on how many fields a B2B lead form should have.

3. Put marketing's commitment in numbers

Marketing's commitment can't simply be "send leads." Volume and quality must be specified together. A sample set of commitments:

• Monthly MQL target: Set according to sales capacity. For example, in a team of 3 SDRs, if you assume each SDR can properly work 25 new MQLs per week, the monthly target comes to roughly 300 MQLs.
• Quality threshold: At least 70% of MQLs delivered convert to SAL. If this rate drops, marketing is responsible for reviewing its channel mix and scoring settings.
• Data completeness: Every MQL record must include complete source, campaign, engagement history and company information.
• Context note: Information such as which content the lead downloaded and which pages they visited should be visible in the CRM record so sales can personalize its first message.

Working backward from sales capacity to set the volume target is critical. Sending more leads than sales can handle is just as harmful as sending too few. Leads that can't be worked sit idle, go cold and get labeled "bad leads."

4. Put sales' commitment in numbers

Sales' commitment has three components: accept/reject time, time to first touch and follow-up cadence.

• Accept or reject time: Once an MQL is assigned, it must be marked as SAL or "rejected" within 1 business day at the latest.
• Time to first touch: Varies by lead type (see the table below).
• Follow-up cadence: If there's no response to the first touch, at least 6 touches (a mix of phone, email and LinkedIn) should be made within, for example, 10 business days.
• Outcome logging: At the end of the cadence, an outcome status must be recorded for every lead: meeting booked, not interested, wrong person, unreachable, returned to nurturing.

5. Define rejection and recycling rules

Sales can reject a lead, but it must choose the reason from a standard list. Don't use a free-text field, because it can't be analyzed. Sample rejection reasons:

• Outside ICP (company size/industry)
• Wrong person (not a decision-maker or influencer)
• Competitor or student/researcher
• Duplicate record
• Bad timing (6+ months out)
• Invalid contact information

"Bad timing" and "unreachable" outcomes shouldn't send the lead to the trash; they should automatically route it back into a nurturing flow. You can find ideas for designing this recycling setup in our article on an integrated lead nurturing approach.

6. Write the escalation rule

If it's unclear what happens when the SLA is breached, the SLA will eventually be ignored. A simple escalation chain is enough:

1. When the first-touch deadline is missed, the lead owner receives an automatic reminder.
2. When twice the deadline has passed, the SDR manager is notified and the lead can be reassigned.
3. If the weekly breach rate exceeds the set threshold (for example, 10%), the issue becomes the first agenda item in the weekly marketing-sales meeting.

What should the response time be?

No single response time fits every lead. The higher the intent level, the shorter the window should be. The table below contains sample values that many B2B SaaS teams can use as a starting point. Adapt them to your own sales capacity and working hours.

| Lead type | Example source | Time to first touch | Channel | |---|---|---|---| | Hot request | Demo request, quote request form, "talk to sales" | 15 minutes – 1 hour during business hours | Phone + personal email | | High-scoring MQL | Pricing page + case study visit, score threshold crossed | Same business day (within 4 hours at most) | Email + LinkedIn | | Event lead | Trade show, webinar attendee | 24–48 hours | Email + phone | | Content lead (below MQL threshold) | E-book, report download | Not sent to sales; enters nurturing | Automated email |

With hot requests, minutes matter, because the lead is very likely checking out your competitor in another tab at that very moment. For hot requests that come in after hours, write a separate rule, such as "by 10:00 a.m. the next business day." For these requests, also set up an instant automated reply that includes a calendar link.

If you don't have a separate plan for event leads, business cards collected after a trade show can sit on a desk for weeks. For this scenario, our first-48-hours plan for post-trade-show lead follow-up offers a framework you can add directly to your SLA.

What does a sample lead handoff SLA look like?

You can create a one-page SLA document by filling in the template below with your own numbers. Long documents don't get read. Keeping the SLA to a single page increases the likelihood that it will be followed.

Purpose: Increase conversion from Inquiry to SQL and prevent lead leakage.

Parties and owners: Marketing (Demand Gen Manager), Sales (SDR Manager).

Definitions:

• MQL: ICP fit + lead score ≥ 100, or a high-intent form.
• SAL: An MQL accepted by an SDR within 1 business day.
• SQL: A lead whose need, authority and timing have been validated in a discovery call.

Marketing commitment:

• 300 MQLs per month (updated according to the quarterly capacity plan).
• MQL → SAL rate ≥ 70%.
• Source, campaign and last 3 interactions on every record.

Sales commitment:

• Hot request: first touch within 1 hour during business hours.
• Other MQLs: first touch within 4 business hours.
• At least 6 touches within 10 business days.
• A standard outcome code for every lead.

Rejection and recycling:

• One of the standard rejection reasons is mandatory.
• "Timing" and "unreachable" outcomes are automatically returned to nurturing.
• Leads that cross the score threshold again from nurturing are flagged as "returning MQLs."

Escalation: Reminder at 1x deadline overrun; manager notification and reassignment at 2x overrun.

Review: Weekly 30-minute operations meeting, quarterly SLA revision.

How do you automate the SLA in your CRM?

An SLA tracked in Excel is followed enthusiastically in the first month and forgotten by the third. You need to embed the SLA inside your CRM. Whether you use HubSpot, Salesforce, Pipedrive or another CRM, the structure you need is similar.

Required fields

• Lead stage (Inquiry, MQL, SAL, SQL, Rejected, Nurturing)
• MQL date and time (automatic timestamp)
• Assignment date and time
• First touch date and time (first logged call, email or task completion)
• Response time (difference between first touch and assignment, calculated field)
• SLA status (On time / Breached)
• Rejection reason (dropdown)
• Cadence outcome (dropdown)

Required automations

1. Automatic assignment: A lead that becomes an MQL is instantly assigned to an SDR based on region, segment or round-robin rules. Manual assignment is an SLA's first enemy.
2. Instant notification: When a hot request comes in, the assigned rep receives a CRM notification and a message is posted to the team chat channel.
3. Task creation: Along with the assignment, a "first touch" task is created with a due date appropriate to the lead type.
4. Timer and escalation: A reminder is triggered when the due date passes, and a manager notification when it's exceeded twofold.
5. Nurturing recycle: Certain rejection reasons and cadence outcomes automatically enroll the lead in the relevant email flow.

By setting up these automations, you also reduce your sales team's repetitive work. If you'd like to look at the topic in a broader context, check out our article on how sales automation speeds up business at SaaS companies. For teams that need to design their process and automation architecture at the group level, Corner Group's strategy and automation approach is also a good starting point.

Which metrics show whether the SLA is working?

You can't manage an SLA without measuring it. But trying to measure everything turns meetings into report-reading sessions. The following seven metrics are enough for most teams:

1. MQL volume (vs. target): Is marketing meeting its volume commitment?
2. MQL → SAL rate: Is the quality of delivered leads acceptable?
3. Median first response time: Use the median, not the average. A few outliers skew the average.
4. SLA compliance rate: The percentage of leads for which the time target was met.
5. Cadence completion rate: The percentage of leads that reached the committed number of touches.
6. SAL → SQL rate: How many of the leads sales accepted turn into real opportunities?
7. Rejection reason distribution: Which leads are rejected, from which channel, and for what reason?

When you track these metrics broken down by channel, powerful insights emerge. For example, if webinar leads have a high SAL rate but a low SQL rate, the problem lies less in lead quality and more in how sales structures its first conversation with webinar attendees. If "wrong person" keeps rising among rejection reasons, your targeting or form design needs to be revised.

What are the most common mistakes?

Writing an SLA without sales' involvement. A document that marketing writes alone and sends to sales saying "sign this" won't be followed. Draft it in a joint workshop with both sides at the table.

Ignoring capacity. Setting a volume target without knowing the sales team's weekly capacity leads to breaches in the very first week. Measure the number of new leads each SDR can handle per week using real data.

Setting a single response time. Holding a demo request and an e-book download to the same rule either overwhelms sales or lets hot leads slip away.

Leaving the rejection reason as free text. Hundreds of variations like "not a fit," "no go" and "not interested" can't be analyzed.

Measuring marketing on volume alone. If marketing is rewarded on MQL count, the threshold loosens over time. Basing part of the targets on SAL and SQL aligns the incentives of both teams.

Writing the SLA once and forgetting it. Products, markets and teams change. If you don't update the numbers and definitions once a quarter, the SLA drifts away from reality.

Failing to build the feedback loop. The insights sales gathers in the field (objections, messages that resonate, common traits of won deals) should flow back to marketing. This information is also the most valuable raw material for content creation. For example, stories from won customers can be turned into B2B SaaS case studies and fed back into the funnel.

How do you roll out the SLA in the first 90 days?

First 30 days: Foundation and measurement

• Measure your current state: MQL volume over the last 3 months, average and median response time, and the share of leads never followed up.
• Hold a 2-hour definitions workshop with one representative each from marketing and sales. Put the MQL, SAL and SQL definitions in writing.
• Create the required fields and timestamps in your CRM.
• Start measuring only, without enforcing anything yet. The first month is a "trial period."

Days 31–60: Automation and first revision

• Activate the automatic assignment, notification and task creation rules.
• Turn on the escalation flow.
• Launch the weekly 30-minute operations meeting. Keep only three items on the agenda: SLA compliance, rejection reasons and stuck leads.
• Make realistic adjustments to response times and the volume target based on the first month's data.

Days 61–90: Optimization

• Compare MQL → SAL → SQL rates by channel and lower the scoring weight of weak channels.
• Make form, targeting and content changes based on rejection reasons.
• Tie part of the marketing and sales targets to shared metrics (SQLs or pipeline value).
• Publish version two of the SLA at the end of the quarter.

If your internal resources aren't enough to carry this entire setup, supporting the lead generation and first-touch stages with a specialist team can be an option. Sales Corner's data-driven B2B sales and lead generation services offer an alternative for companies that want to scale SDR capacity quickly.

Frequently asked questions

What is the difference between a lead handoff SLA and lead scoring?

Lead scoring is the model that measures how qualified a lead is using points. The SLA is the agreement that defines what marketing and sales will do once that score crosses a certain threshold. Scoring answers the question "who should go to sales," while the SLA answers "what happens after they do."

Does a small SaaS team need a written SLA too?

Yes, but the document can be much shorter. Even in a team made up of one marketer and two salespeople, leads get lost if the MQL definition, time to first touch and rejection reasons aren't written down. A half-page SLA and a few timestamp fields in the CRM are a sufficient starting point for small teams.

What should you do if the sales team isn't following the SLA?

Check capacity first. Most breaches stem from sending more leads than the team can handle or from manual assignment delays. If capacity is sufficient, activate the escalation rules, add the SLA compliance rate to the sales manager's performance indicators, and discuss breaches in the weekly meeting using data, without making it personal.

How often should the SLA be updated?

Numbers and definitions should be reviewed once a quarter. However, when a new product, a new market segment, team growth or a new lead channel comes into play, an interim revision should be made without waiting for the end of the quarter.

Conclusion

A lead handoff SLA turns the "who's right" debate between marketing and sales into a measurable operation. Start with shared definitions: put in writing what MQL, SAL and SQL mean. Then express both sides' commitments in numbers. For marketing, specify volume, quality and data completeness; for sales, specify acceptance time, time to first touch and follow-up cadence. Standardize rejection reasons, route rejected leads back to nurturing and support all of these rules with CRM automations. Most importantly, treat the SLA as a living document and update it every quarter based on the data.

If you want to build marketing-sales alignment, automate your lead handoff process in your CRM or scale your SDR operation, the SAAS Corner team is ready to help. Reach out to us through our contact page to assess your current situation together.

Related Posts

• What Is a B2B Lead Magnet? 7 SaaS Examples & How to Choose
• How to Measure Brand Awareness in B2B Companies
• How to Build a Target Account List in B2B
• How to Calculate Cost per Lead (CPL) in B2B