Sales and Marketing Alignment: Governing the Definition of a Lead
Sales and marketing alignment is a definitions problem, not a relationship one.
Ask leaders whether sales and marketing are aligned and the answer can differ from what frontline teams report. In Forrester’s 2024 Priorities Survey, 82% of C-level respondents said their product, sales and marketing teams were aligned, including 41% who described them as highly aligned. The same Forrester post reports that, in its separate Q2 2024 Sales and Marketing Alignment Survey, 65% of sales and marketing professionals reported a lack of alignment between the leaders of those two functions. These were different surveys, not paired responses from the same organisations.
The handoff exposes what breaks: the definition. Marketing calls a record qualified; sales disagrees. Shared dashboards, off-sites and goodwill do not settle what “qualified” means or who can change the criteria.
Alignment is a definitions and governance problem. A shared definition, a service-level agreement (SLA), a named owner and a record of acceptance and rejection make it an operating fact.
What sales and marketing alignment 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. With an enforced shared definition, the teams can disagree about other matters and still be aligned where the handoff happens. Goodwill cannot close a gap in the definition.
Leaders describe what the shared objectives are meant to achieve; operators describe the daily experience of leads being rejected or ignored. Leaders and operators can give honest accounts of different layers of the same organisation. That may account for the gap between the reported views; the two separate Forrester surveys do not establish the cause.
For a team already running a lifecycle, alignment becomes 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 depends on a governed definition
A marketing-qualified lead (MQL) is marketing’s claim that a record qualifies. A sales-qualified lead (SQL) is sales’ acceptance that it has reviewed the record and agreed to work it. The gap between the claim and the acceptance is where misalignment lives.
First Page Sage’s MQL-to-SQL benchmark defines an SQL as a lead “vetted by a salesperson and determined to be a good fit” that has “met with or booked a meeting with a salesperson”. Its 2019 to 2025 client data puts B2B SaaS at around 13%. Across industries, the band runs from roughly 10% in legal services and real estate to around 26% in business insurance. These are one agency’s client results, not a universal target.
In this model, an SQL does not exist until sales acts. Marketing can assert an MQL and offer it, but only sales can decide that it becomes an SQL. The handoff is an act of acceptance, not a transfer of ownership.
The share of marketing-qualified leads that sales actually accepts is the MQL-to-SQL acceptance rate. It is the cleanest single read on whether the two functions share a working definition. Within this agency’s benchmark, the large majority of what marketing calls qualified is not accepted as qualified by sales. The useful comparison is with the team’s own funnel, under the same definitions.
A low acceptance rate is not automatically marketing’s fault. Treating it as marketing’s failure 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. Rejection reasons show whether the definition or its application is failing; resolving disagreement about what qualifies is a governance task rather than a morale one.
What a sales and marketing SLA should contain
A service-level agreement records the shared definition and the commitments on both sides of the handoff.
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’s SLA guidance laid out this structure some years ago. HubSpot sells marketing and sales software, so it has an interest in the category; the structure 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 SLA makes the minimum viable lead thresholds explicit so both functions agree what can cross each gate.
Who owns the definition 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.
Calculate the cost of misalignment from your funnel
Three figures recur, but they deserve different treatment. The “one trillion dollars lost annually” claim is a vendor aggregate built on an older analyst estimate; use it, if at all, as a rough aggregate rather than a hard finding. The “Forrester says 38% of revenue” claim has no traced primary source, so leave it out. The defensible estimate is the long-standing, widely cited figure attributed to IDC: a company’s inability to align sales and marketing around the right processes and technologies costs it 10% or more of revenue per year. It is an established estimate rather than a fresh finding.
Build the cost from the programme’s own funnel. An acceptance rate near 13% means most of what marketing paid to generate is never worked. An illustrative 1,000 MQLs at 13% yields 130 SQLs and leaves 870 that sales never takes on. Multiply those 870 by the fully loaded cost per MQL to calculate the waste for that cohort’s period; it is annual only if the cohort covers a year.
The fully loaded cost of demand paid for but lost between marketing’s claim and sales’ acceptance is the True Cost of a Demand. Closing that gap is what Zero Waste means in practice.
Slow handoffs make this worse by reducing qualification odds. Harvard Business Review’s The Short Life of Online Sales Leads documented the effect in March 2011. A governed lead-routing process puts a response deadline and an accountable owner against the handoff.
Some rejection is a data problem: a record that is wrong on arrival gets rejected no matter how good the definition is. Validating at capture, so a record is checked against the programme’s compliance, truth and value criteria before it reaches the CRM, gives sales less to reject in the first place. That data-truth discipline makes the acceptance rate easier to improve.
Put the agreement into practice
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. When both functions work from that evidence, the perception gap between leadership and the teams starts to close.
Most of the residual gap traces to two causes: ungoverned definitions and records that were wrong before anyone applied them. 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 will tell you whether the main problem is the definition, a slow handoff or faulty input data.
Sources
FAQs
What is sales and marketing alignment?
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. Two teams that get on well are not aligned if they disagree about which leads are qualified. 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.
What is the difference between an MQL and an SQL?
A marketing-qualified lead (MQL) is marketing’s claim that a record meets its qualification 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. Marketing can create an MQL; only sales can create an SQL by accepting it. The MQL-to-SQL acceptance rate measures how often those decisions agree.
What should a sales and marketing SLA contain?
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.
Who owns the definition of a qualified lead?
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.
How do you measure sales and marketing alignment?
The MQL-to-SQL acceptance rate, the share of marketing-qualified leads that sales accepts and works, is the cleanest single read on whether marketing and sales share a working definition. Pair it with a rejection log that records why sales declined each lead. First Page Sage reports around 13% for B2B SaaS and roughly 10% to 26% across industries in its 2019 to 2025 client data. Compare those figures with your programme’s own funnel under the same definitions. A rate far below your target indicates that the two functions are working to different definitions. The rejection log shows whether the problem is the definition, faulty data or a slow handoff.
How much does misalignment actually cost?
The most useful calculation uses the programme’s own funnel and fully loaded cost per MQL: 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. Use the “one trillion dollars a year” vendor figure, built on an older analyst estimate, if at all, as a rough aggregate rather than a hard finding. Leave out the untraced “Forrester says 38% of revenue” claim. The defensible estimate is the long-standing figure attributed to IDC: a company’s inability to align sales and marketing around the right processes and technologies costs it 10% or more of revenue per year.
Where to go next
Demand Generation System Foundations: Quality, Data, Signals, and Governance
The full guide this is part of.
The Demand Generation Framework
A practical guide to demand generation as one framework: creation, influence and capture, and where to go deep on quality, signals and measurement.
Core Data Objects: The CRM Data Model and the Buying Group
The CRM data model treats accounts, contacts and opportunities as first-class objects. Where the buying group fits, and what that costs.
Data Orchestration: Why Coordinating Bad Data Just Moves It Faster
Data orchestration coordinates your stack, but coordinating bad data only moves it faster. Why quality is set at capture, not the pipeline.
Bring the question you could not find answered.
A first call is the place to work through it for your programme.
Or request a free audit of leads from a recent programme.