Sales and marketing alignment for SaaS

Alignment workshops do not fix alignment. What fixes it is a document with numbers in it that both leaders sign, and a weekly meeting where those numbers get read aloud in front of people.

Below is the contract. Copy the structure, change the numbers, and get it signed before the next quarter starts.

Why do most alignment efforts fail?

Because they treat a definitional problem as a relationship problem. Marketing says it delivered 420 qualified leads. Sales says it got maybe 90 worth calling. Both are telling the truth, and no amount of shared offsites resolves it, because the word qualified is doing different work in each sentence.

The second reason is one sided accountability. Nearly every SLA I have read commits marketing to a lead number and commits sales to nothing. Then leads sit untouched for two days and marketing has no grounds to complain, because the document never said sales owed anything.

What definitions have to be agreed in writing?

Five, and they have to be written as tests a person or a system can apply, not as adjectives.

The sourced and influenced rows cause the most argument, so settle them by writing the SQL query, literally. If two people cannot agree what query returns the sourced number, the definition is not finished. That exercise also exposes gaps in your attribution model that no amount of discussion would surface.

Worth noting: MQL as a term has aged badly, and plenty of teams have retired it. Retiring the acronym without replacing the underlying definition just moves the argument to a new word. Keep the test, rename the label if you want.

What does marketing commit to?

Two numbers and one process obligation.

Volume: a monthly count of qualified leads, expressed as a range rather than a point. “180 to 220 qualified leads per month, measured on the last business day” is defensible. A single number invites a miss by two and an argument about it.

Quality: an accept rate floor. If sales accepts fewer than, say, 70 percent of what marketing sends, marketing is over-delivering on volume at the expense of fit and the volume commitment drops until the rate recovers. This clause is the one that stops the MQL-stuffing behaviour everyone complains about.

Process: complete records. Every routed lead arrives with company, title, source, the triggering action and a timestamp. A lead missing two of those fields does not count toward the volume commitment. That single clause does more for data hygiene than any enrichment tool.

What does sales commit to?

Speed, persistence and feedback. In that order of importance.

Speed to lead is the most replicated finding in B2B inbound. Research from InsideSales and the well known Harvard Business Review study on lead response found contact and qualification rates falling sharply within the first hour, with the steepest fall in the first few minutes. The practical version: a demo request that gets a call in five minutes converts several times better than the same request called in an hour.

Lead type	First response window	Minimum attempts	Channels	Timeout to recycle
Demo request	5 minutes, business hours	6 over 10 business days	Call, email, LinkedIn	10 business days
Pricing page enquiry	15 minutes	6 over 10 business days	Call, email	10 business days
Free trial, target account	1 business hour	4 over 14 days	Email, call	14 days
Content download, target account	1 business day	3 over 21 days	Email, LinkedIn	21 days
Event scan	2 business days	4 over 14 days	Email, call	14 days

Six attempts over ten business days sounds aggressive until you look at your own connect data. Most reps stop at two. The gap between two attempts and six is usually larger than any improvement marketing can make to lead quality in the same quarter.

Feedback is the third commitment. Every rejected lead gets a code. No code, no rejection.

How should routing and recycling work?

Routing is mechanical and should be invisible when it works. The rules that matter are the edge cases.

Round robin within territory, with capacity caps so one rep does not receive 40 leads on a Monday. Instant scheduling for demo requests, through Chili Piper or an equivalent, because handing the prospect a calendar removes the response time problem entirely for the highest intent segment. Holiday and PTO coverage written into the rules rather than handled by someone noticing.

The genuinely important part is what happens to the leads sales says no to. Use a fixed list of reason codes, six or seven maximum:

• Wrong company size
• Wrong persona or role
• No budget or authority this cycle
• Timing, revisit in a named month
• Competitor or student or job seeker
• Bad data, could not contact
• Already an open opportunity elsewhere

Each code routes somewhere specific. Timing goes to nurture with a re-entry date and reappears automatically. Wrong persona triggers a look at whether that persona should even be targeted, which is a campaign question rather than a lead question. Bad data goes to operations with a weekly count, and if that count rises above 5 percent something upstream broke.

The mechanics of building this handoff end to end, including the CRM object model, are in the marketing to sales handoff playbook.

How do you set one shared pipeline target?

Start from bookings, work backwards through the funnel, then split the pipeline number by source rather than giving each team a different metric.

Worked example for a company with a $28k average contract value and a $6M new bookings target:

Both teams now look at one table. Marketing’s number is a pipeline number, not a lead number, which means marketing has a reason to care whether the leads convert. Sales has a sourced target of its own, which removes the standing complaint that outbound gets no credit.

Keep an eye on pipeline velocity alongside the coverage number. Coverage can look healthy while deals age out, and velocity is the metric that catches it early.

What goes in the weekly review?

Twenty five minutes, four numbers, same order every week. If it takes longer, you have turned it into a pipeline review, which is a different meeting.

The monthly version adds cohort quality: of the leads routed 60 days ago, how many became opportunities. That lag makes it useless weekly and valuable monthly, and it is the number that tells you whether the accept rate is measuring anything real.

The parts nobody writes down

Three clauses that prevent the most common breakdowns.

Name the arbitrator. One person, named in the document, with authority to decide a dispute inside 48 hours, binding until the quarterly review. Usually revenue operations. Without this, disputes escalate to whoever has the CEO’s ear, which corrodes trust faster than any bad lead.

Set a change window. Definitions and thresholds change quarterly, on a date, not whenever somebody has a bad month. Mid-quarter changes make every trend line unreadable.

Write the exception path. There will be a lead that breaks the rules and deserves to. A named process for exceptions, with a log, stops people routing around the SLA quietly. Undocumented exceptions become the norm within two quarters.

What this costs and where it fails

The honest cost is meeting time and operational overhead. Reason codes require someone to enforce them, and enforcement is unglamorous. The first six weeks after launch, compliance will be poor and somebody has to chase it. If no leader is prepared to do that chasing, do not launch the SLA, because a document everyone ignores is worse than no document.

The most common failure mode is a five minute response window promised with no capacity to deliver it. Four reps cannot cover a five minute SLA across three time zones. Either fund the coverage, narrow the window to your core hours and say so, or use instant scheduling so the prospect books themselves. Promising the window and missing it teaches both teams that the document is fiction.

And a tradeoff worth stating: a strict accept rate floor will reduce marketing’s lead volume, sometimes by a third. That is the point, but somebody needs to warn the board before the number drops, or the SLA gets blamed for a decline it deliberately caused.

Get it signed this month

Draft the five definitions, write both sides of the commitment, pick your seven rejection codes, calculate the shared pipeline target from your own bookings number, and name the arbitrator. Two hours of work with the sales leader in a room will produce a better document than six weeks of circulated drafts.

Pre-built versions live in the sales and marketing SLA template, with a longer editable variant in this SLA template and a demand-gen specific cut in the SLA generation template. Fold the resulting numbers into your demand generation plan template so the annual plan and the weekly meeting reference the same targets, and keep the broader demand generation programme pointed at the pipeline number rather than the lead number.