How to Write a Marketing to Sales SLA That Reps Actually Follow

Why do marketing and sales keep arguing about lead quality?

They argue because nobody wrote down what a lead is, how fast it must be worked, and what happens when it is not. A service level agreement between marketing and sales fixes that by turning opinions into rules both teams signed. Without one, every bad month becomes a blame meeting.

The same pattern shows up in many B2B teams. Marketing reports a healthy number of leads. Sales says the leads are junk. Both are partly right, and neither can prove it, because the handoff is undefined. The CRM records that a lead arrived, but not whether anyone agreed it deserved a call.

A good SLA is short, boring, and enforced by the system rather than by goodwill. This article is how I write one for a small revenue team, usually with HubSpot or Salesforce as the CRM and a handful of reps who also sell, prospect, and do demos.

What is a marketing to sales SLA, really?

It is a written agreement with two sides. Marketing commits to sending a defined type and volume of lead. Sales commits to working each one within a set time and recording an outcome. The SLA names the fields, the clock, the owner, and the escalation path, so either side can check compliance.

The word "agreement" matters more than the word "service". If sales leadership did not help write it, reps will treat it as a marketing document and ignore it. If marketing did not commit to anything measurable, sales will treat it as a one-sided demand. Both sides need something to lose.

I also separate the SLA from the lead scoring model. Scoring decides which leads qualify. The SLA decides what happens after they qualify. Mixing them creates long documents nobody reads. Keep the scoring rubric in its own place and reference it from the SLA in one sentence.

How should you define the lead the SLA covers?

Define it by observable fields, not by adjectives. "High quality" is not a definition. "Submitted the demo form, company in the target country list, employee count in range, work email" is a definition. If a rep can check every condition in the CRM record without guessing, the definition is good enough to enforce.

Most teams need two or three lead types in the SLA, not ten. A demo request gets the fastest clock. A content download that matches your ideal customer profile gets a slower clock. Everything else goes to nurture and is outside the SLA entirely. Writing down what is excluded prevents more arguments than writing down what is included.

I keep a separate rule for leads that do not fit the profile at all, because they still arrive and still need a decision. I covered that in detail when writing about inbound leads outside your ICP. The SLA should point to that rule so reps are not tempted to quietly ignore anything awkward.

How fast should sales respond under the SLA?

Pick a response time your team can hit on a bad week, then measure it honestly. A promise of five minutes that is broken daily teaches everyone the SLA is fiction. A promise of four business hours that is kept builds trust. Tighten the clock once the team proves it can meet the first one.

Define exactly when the clock starts and stops. I start it when the record meets the lead definition and is assigned to an owner, not when the form is submitted, because enrichment and routing take time. I stop it at the first logged human touch, whether that is a call, a personal email, or a LinkedIn message recorded on the record.

Then decide what counts as a touch. An automated sequence enrollment should not count, because it lets a rep satisfy the SLA without thinking. The point of a fast response is a human reacting to a buyer who raised a hand. I would rather see a slower clock with real touches than a fast clock gamed by automation.

What should marketing promise in return?

Marketing should promise volume, completeness, and honesty. Volume means a target number of qualifying leads per month. Completeness means every lead arrives with the fields sales needs, such as company, role, source, and the page or offer that converted. Honesty means flagging campaigns that will produce lower intent leads before they launch.

The completeness promise is where GTM engineering earns its place. If enrichment from Clay or Apollo runs before assignment, reps open a record that already shows company size and industry. If it runs after, reps either wait or call blind. I make the enrichment step a precondition of assignment, so incomplete records never start the clock.

I also ask marketing to commit to a weekly feedback review. Sales marks leads as accepted or rejected with a reason, and marketing reads those reasons every week. Without that loop, the volume target pushes marketing toward cheap leads, and the SLA quietly rewards the behavior it was meant to stop.

How do you make the CRM enforce the SLA?

Build the SLA into fields, workflows, and a report. Add an acceptance status, a rejection reason, and a timestamp for first touch. Use workflows to assign the owner, start the clock, and alert when time runs out. Then build one report both teams look at every week. If it lives only in a document, it is dead.

In HubSpot or Salesforce, the minimum set is small. A lead status property with values like New, Accepted, Rejected, and Working. A required rejection reason picklist when status becomes Rejected. A date field stamped when the first human activity is logged. Everything else can wait until the basics are used consistently.

For the report, I start with response time by rep and acceptance rate by source. If you have not built a response time view yet, my walkthrough on building a lead response time report in HubSpot covers the fields and filters. The report is what turns the SLA from a promise into a habit.

What happens when someone breaks the SLA?

The SLA must say what happens on a miss, or it is only a wish. I use a simple ladder. First, an alert to the owner. Second, after a further window, an alert to the sales manager. Third, the lead is reassigned. Reassignment is the step reps remember, because losing a hot lead to a colleague stings.

Keep escalation automated and impersonal. A manager chasing reps by hand creates resentment and inconsistency. A workflow that reassigns after a fixed window treats everyone the same. Reps may grumble at first, but they quickly prefer a clear rule over a manager's mood on a given afternoon.

Marketing misses need consequences too. If lead volume falls short for two months, or rejection rates climb for a source, the SLA should trigger a joint review of that channel. That keeps the agreement balanced. When sales sees marketing held to a number, adoption of the whole SLA tends to improve.

What mistakes make an SLA fail in practice?

The common failures are vague definitions, unrealistic clocks, missing rejection reasons, and no weekly review. Another is writing the SLA once and never revisiting it after the ICP or team changes. An SLA that no longer matches how the team sells is worse than none, because it trains people to ignore rules.

A quieter failure is the handoff between people inside sales. If SDRs accept leads and pass them to account executives, the SLA needs a second clock for that internal handoff. I wrote a lead handoff checklist for SDRs and AEs for exactly this gap. Leads often die between two sales roles, not between marketing and sales.

The last mistake is treating the SLA as a weapon. If leadership uses the report only to punish, reps will game the timestamps. Use it first to find system problems, such as routing gaps or missing enrichment, and only then to coach individuals. In my view, most SLA misses come from broken plumbing, not lazy people.

What should you do next?

Book one hour with the heads of marketing and sales and draft the first version together. Agree on two lead types, one clock for each, the fields that prove compliance, and the escalation ladder. Keep it to one page. Then build the fields and the report before anyone announces the SLA to the team.

Run it for a month before changing anything. Look at response times, acceptance rates by source, and the top rejection reasons. Adjust the definitions first, the clocks second. Expect the first month to expose routing and data gaps, and fix those in the system rather than in the document.

If you want help turning your lead handoff into rules your CRM enforces, reach out through pravinkumar.co. I build the websites and the automations behind them for lead generation, and the handoff from form to rep is where most of that work pays off.