Sales and Marketing Alignment: Governing the Definition of a Lead
Written by LeadScale
Ask a board whether sales and marketing are aligned and most will say yes. Ask the people running the handoffs and you get a different answer. Forrester, the analyst firm, found the gap directly: in its 2024 Priorities Survey, 82% of C-level executives said their product, sales and marketing teams were aligned, with 41% calling them highly aligned. In Forrester’s separate Q2 2024 survey of sales and marketing professionals, 65% said the leaders of those two functions were not aligned at all. The gap is not subtle: leadership reports an alignment the front line does not experience.
Sales and marketing alignment is usually treated as a relationship problem: the state in which both functions get on and pull together. The standard advice for the gap above follows from that framing, an off-site, shared targets, a joint dashboard, more empathy. Those things are fine, but they do not fix the thing that actually breaks. What breaks is the definition. Marketing calls a record qualified and hands it over; sales looks at it and disagrees; both sides walk away convinced the other is the problem. That is not a personality clash. It is a dispute about what the word “qualified” means, and you cannot resolve a definition dispute with a better relationship.
This article treats alignment as a definitions and governance problem. It covers what alignment actually means as an operating fact, why the MQL-to-SQL boundary is where the disagreement lives, what a service-level agreement between the two functions should contain, who owns the definition when it changes, and how to price the cost of getting it wrong without quoting numbers you cannot defend.
What Sales and Marketing Alignment Actually Means
Alignment is not a feeling that the two teams get on. It is a working state: sales and marketing operate to one shared definition of a qualified lead, with agreed handoffs and shared targets, and they can both see whether the handoff is holding. When that shared definition exists and is enforced, the teams can disagree about plenty of other things and still be aligned in the sense that matters. When it does not, no amount of goodwill closes the gap.
The Forrester perception gap is the tell. When leadership reports alignment and the front line reports its absence, the leaders are describing an intention and the operators are describing the daily experience of leads that get rejected or quietly ignored. The board is looking at the org chart and the shared OKR, while the SDR is looking at a lead that fits nothing they would actually work. Both are being honest, and they are describing different layers of the same organisation.
For the reader already running a lifecycle, the useful move is to stop treating alignment as a cultural target and start treating it as an operating contract with a measurable boundary. The boundary is the point where marketing hands a record to sales. Everything upstream of it is marketing’s assertion that the record is worth working. Everything downstream depends on sales agreeing. The health of the alignment is how often those two things match.
Why Alignment Is a Definitions Problem, Not a Relationship Problem
Here is the distinction the relationship framing misses. A marketing qualified lead is a claim. It says: by our criteria, this record qualifies. A sales qualified lead is an acceptance. It says: sales has looked at this record and agreed to work it. The two are not the same event, and the space between them is where misalignment lives.
The definitions themselves show this. First Page Sage, a B2B demand-generation agency, publishes an MQL-to-SQL benchmark drawn from its client data, and its own SQL definition bakes acceptance in. An SQL, in that definition, is a lead that has been “vetted by a salesperson and determined to be a good fit” and has “met with or booked a meeting with a salesperson.” Read that carefully. An SQL does not exist until sales acts. Marketing cannot create one. Marketing can only assert an MQL and offer it; sales decides whether it becomes an SQL. The definition encodes the handoff as an act of acceptance, not a transfer of ownership.
That makes the misalignment measurable. The share of marketing qualified leads that sales actually accepts is the MQL-to-SQL acceptance rate, and it is the cleanest single read on whether the two functions share a working definition. First Page Sage puts the figure at around 13% for B2B SaaS, with a cross-industry band running from roughly 10% in sectors like legal services and real estate to around 26% in business insurance. Treat that as one agency’s client data rather than an industry constant, and refresh it against your own funnel. The number that matters is yours. But the shape holds: in most B2B funnels, the large majority of what marketing asserts as qualified is not accepted as qualified by sales. That is the alignment problem, stated as a rate.
A low acceptance rate is not automatically marketing’s fault, and this is where the relationship framing does real damage. It reads the rejected leads as marketing sending rubbish, or sales being lazy, and turns an operating question into a blame question. The honest reading is that the two functions are working to two different definitions of the same word, and nobody has reconciled them. The acceptance rate only shifts once those definitions are reconciled, which is a governance task rather than a morale one.
What a Sales and Marketing SLA Should Contain
The instrument that carries a shared definition is a service-level agreement between the two functions. Most articles on alignment recommend one and stop there. The useful part is what goes in it.
A working SLA contains the shared definition first: the ideal customer profile and buyer personas, and then the explicit criteria for an MQL and for an SQL, written so that both sides would sort the same record the same way. It sets out what each function owes. Marketing commits to a volume and a quality standard for the leads it passes. Sales commits to a response time and to actually working what it accepts. It defines the handoff mechanics, including something most teams skip: reporting not only the leads sales accepts but the leads sales rejects, and why. Recording rejections turns them into data that sharpens the definition over time, whereas the ones that go unrecorded are simply leads that disappear without anyone learning from them. And it sets the metrics both sides watch, with the acceptance rate among them.
HubSpot, which sells marketing and sales software and so has an interest in the category, laid out this structure in its guidance some years ago, and the skeleton has held up even as the surrounding numbers have aged. Its own 2015 data claimed that companies with an active SLA were markedly more likely to report better year-on-year returns, but that figure is a decade old now and should be read as evidence that the SLA-performance link has been observed for a long time, not as a current benchmark. The durable contribution is the checklist, not the statistic. For the lifecycle thresholds that sit inside the SLA, the minimum viable lead work covers what should cross each stage.
Governing the Definition: Who Owns It When It Changes
A shared definition is not a one-time agreement. It drifts. Marketing loosens a scoring threshold to hit an MQL target at quarter end. Sales quietly stops accepting a segment it used to work. A new product launches and nobody updates the criteria. Each change is small and reasonable on its own, and none of them is written down, so six months later the two functions are back to working from different definitions without anyone having decided to change anything.
The fix is to treat the lead definition the way engineering treats a specification. It has a named owner, usually in revenue operations, who is accountable for the current version. It has a changelog, so that when the MQL criteria move, the change is recorded with a date and a reason. It has a review cadence, and here the old HubSpot guidance is useful again: it suggested reviewing the SLA roughly every six months, or quarterly for fast-growing teams, which is a sensible starting rhythm. And it has a dispute path, so that when sales rejects a batch of leads, there is a defined route for that disagreement to update the definition rather than curdle into resentment.
This is the definition-governance work that decides whether alignment holds. The governance cadence that keeps a demand engine honest is the natural home for the definition review, and the routing and ownership rules decide who receives a lead once it clears the definition. A definition with an owner and a change process survives quarter-end pressure. One that lives in a slide from last year quietly stops matching what either side actually does, and the drift goes unnoticed until the acceptance rate falls.
What Sales and Marketing Misalignment Actually Costs
The cost of misalignment is where this topic goes wrong most often, because two numbers dominate it and neither survives scrutiny. The “one trillion dollars lost annually” figure is a vendor aggregate built on top of an older analyst estimate; use it, if at all, as a rough aggregate and not as a hard finding. The “Forrester says 38% of revenue is lost to misalignment” figure is repeated everywhere and attributed to Forrester everywhere, but it does not appear on any Forrester page anyone can produce. It appears to have picked up the Forrester name somewhere in the retelling, with no primary source behind it, so leave it out.
The defensible figure is IDC’s long-standing estimate that a company’s inability to align sales and marketing around the right processes and technologies costs it 10% or more of revenue a year. That is per-company and actionable, and it has circulated as the analyst estimate for over a decade, so present it as an established estimate rather than a fresh result. Better still, build the cost from your own funnel. An acceptance rate near 13% means most of what marketing paid to generate is never worked. As a rough worked example, 1,000 MQLs at a 13% acceptance rate leaves around 870 that sales never takes on; multiply those by your fully loaded cost per MQL and the annual waste is a single line on a page. Slow handoffs make it worse, because a lead that is accepted but reached hours or days late is often no longer reachable, a decay effect documented as far back as the 2011 Harvard Business Review study of online lead response and repeated ever since. The lead routing work covers that speed problem in full. Expressed as the True Cost of a Demand, the waste is the fully loaded cost of every demand you paid for that dies in the gap between assertion and acceptance, and closing that gap is what Zero Waste means in practice.
Some of that gap is a definition problem, which governance fixes. Some of it is a data problem: a record that is wrong on arrival gets rejected no matter how good the definition is. Validating at the point of capture, so that a record is checked for compliance, truth and value before it ever reaches the CRM, means sales has less to reject in the first place. That upstream work is covered in the data truth material; here it is enough to note that a cleaner record on arrival makes the acceptance rate easier to move.
Making Alignment an Operating Discipline
Treat sales and marketing alignment as an operating discipline. It is a shared definition of a qualified lead, carried in an SLA, owned by someone, reviewed on a cadence, and measured by how often the leads marketing asserts are the leads sales accepts. Get those in place and the perception gap between the board and the floor starts to close, because the two are finally describing the same thing.
Most of the residual gap traces to two causes: a definition nobody governs, and records that were wrong before anyone applied the definition. The first is a governance fix. The second is an upstream one, which is the job an engine like the LeadScale Engine does when it validates a record at capture, before it reaches the point where sales would otherwise reject it. Clean records and a governed definition are what let the acceptance rate rise.
If you want a concrete next step, write the definition down. Draft the shared MQL and SQL criteria on one page, put a name against it as owner, agree a review date, and start recording every rejected lead and its reason. Within a quarter the rejection log alone will tell you whether your alignment problem is a definition that needs fixing, a handoff that is too slow, or data that was broken before it arrived.
Frequently Asked Questions
Sales and marketing alignment is a working state in which both functions operate to one shared definition of a qualified lead, with agreed handoffs and shared targets, and can both see whether the handoff is holding. It is an operating fact rather than a feeling: two teams that get on well are not aligned if they disagree about what counts as a qualified lead, and two teams that share and enforce a definition are aligned even when they argue about other things. The clearest sign of alignment is that the leads marketing passes are the leads sales accepts and works.
A marketing qualified lead (MQL) is marketing’s claim that a record qualifies by its criteria. A sales qualified lead (SQL) is a lead that sales has looked at, agreed is a good fit, and taken on, usually including a booked meeting. The difference is who acts. Marketing can assert an MQL, but only sales can create an SQL by accepting it. The space between the assertion and the acceptance is where most misalignment lives, and the share of MQLs that become SQLs is a direct measure of how well the two functions share a definition.
A service-level agreement between sales and marketing should contain the shared definition first: the ideal customer profile, buyer personas, and explicit MQL and SQL criteria written so both sides sort a record the same way. It should state what each function owes, marketing on lead volume and quality, sales on response time and on working what it accepts. It should define handoff mechanics, including reporting both accepted and rejected leads with reasons. And it should set the metrics both watch, including the acceptance rate, plus a review cadence for keeping the definition current.
The lead definition should have a single named owner, usually in revenue operations, who is accountable for the current version. Treat the definition like a specification under change control: a changelog that records when and why the criteria move, a review cadence (roughly six-monthly, or quarterly for fast-growing teams), and a defined dispute path so that when sales rejects a batch of leads, that disagreement updates the definition rather than festering. Without an owner, the definition drifts as thresholds are quietly loosened and acceptance criteria quietly change, and the two functions end up working to different definitions again.
The single most useful measure is the MQL-to-SQL acceptance rate: the share of marketing qualified leads that sales accepts and works. One agency benchmark puts it around 13% for B2B SaaS, with a band from roughly 10% to 26% across industries, but treat that as directional and measure your own. A rate far below your target says the two functions are working to different definitions. Pair it with a rejection log that records why sales declined each lead, because the reasons show whether the gap is a definition problem, a data problem, or a handoff that is too slow.
Be careful with the popular numbers. The “one trillion dollars a year” figure is a vendor aggregate, and the widely repeated “Forrester says 38% of revenue” figure does not trace to any Forrester source, so it should not be used. The defensible estimate is IDC’s long-standing figure that misalignment costs a company 10% or more of revenue per year. The more useful cost is one you build from your own funnel: a low acceptance rate means most of what marketing paid to generate is never worked, and slow handoffs mean some accepted leads go cold before they are reached.
