Marketing and sales misalignment is reliably diagnosed and rarely fixed. The usual interventions, shared OKRs, joint meetings, a new attribution tool, treat symptoms. The root cause is almost always definitional: both teams are measuring different things and calling them the same thing. Fixing that requires a shared language protocol.
Step 1: Audit Your Current Definitions in Writing
Before any alignment conversation, put the current definitions in writing from each team's perspective, separately. Ask marketing: what is an MQL? Ask sales: what makes a lead worth calling? Do this without both teams in the same room.
The gap between those two written answers is your alignment problem. It is usually larger than either team expects. Common gaps include:
- Marketing defines MQL by engagement score; sales defines qualification by company fit - Marketing counts demo requests as qualified; sales finds that half of them are non-ICP - Sales marks leads "no opportunity" without logging a reason; marketing treats those as accepted
Document every gap before proposing any solution. The gaps tell you which definitions to prioritize.
Step 2: Agree on the Lead Progression Definitions
Write a single shared definition document covering these four terms, with explicit criteria for each:
| Stage | What It Means | Who Owns the Decision |
|---|---|---|
| MQL (Marketing Qualified Lead) | Meets fit threshold AND engagement threshold | Marketing |
| SAL (Sales Accepted Lead) | Sales has reviewed and accepted within SLA | Sales |
| SQL (Sales Qualified Lead) | Discovery completed; BANT or equivalent confirmed | Sales |
| Opportunity | Formal buying process confirmed; deal created in CRM | Sales |
- Time from MQL to SAL review (typically one to two business days) - Required disposition when sales rejects an MQL (a reject reason logged in the CRM, not a bare status change) - Recycle criteria: what happens to a rejected lead and who is responsible for re-engagement
Step 3: Build a Pipeline Contribution Agreement
The definition document handles lead quality. The pipeline contribution agreement handles volume. It answers: how much pipeline is marketing responsible for sourcing, by when, and how will we measure it?
A pipeline contribution agreement should specify:
Pipeline sourced target. A dollar amount of pipeline marketing agrees to source per quarter, broken down by segment if needed. This is not leads or MQLs. It is pipeline: deals that have been created and accepted by sales. Attribution rules. Define "marketing sourced" precisely. A common approach is first-touch attribution for sourced (marketing generated the first contact) and multi-touch for influenced (marketing engaged the contact during the sales cycle). The rules need to be set before the quarter, not debated after close. Contribution by channel. Break the sourced pipeline target down by channel so both teams know which channels are expected to produce what volume. This prevents marketing from over-indexing on easy-to-count channels that do not produce qualified pipeline.For more on how pipeline generation targets are set and tracked, see pipeline generation.
Step 4: Agree on the Single Joint Metric
Most alignment failures persist because marketing and sales each have their own primary metric. Marketing optimizes for MQL volume; sales optimizes for quota attainment. These metrics can both be green while pipeline remains broken.
The single joint metric that ends most attribution arguments is sourced pipeline per rep. It is calculated as:
Total marketing-sourced pipeline created in the quarter divided by the number of quota-carrying reps.
This metric forces both teams to care about the same thing. Marketing needs to source enough pipeline. Sales needs to work it. If sourced pipeline per rep is high but win rates are low, the problem is in sales execution. If sourced pipeline per rep is low, the problem is in demand generation. The metric makes the accountability clear without assigning blame.
Review this metric together in a joint pipeline review monthly. Both teams in the same meeting, looking at the same number.
Step 5: Set a Formal Review Cadence
Definitions and agreements degrade without a review cadence. Build two recurring reviews:
Weekly joint pipeline review. Both marketing and sales leadership review new pipeline created that week, sourced by channel, against the quarterly target. This is a 30-minute working session, not a status meeting. Quarterly definition review. After each quarter closes, review the MQL-to-SQL conversion rate, the reject rate, and the win rate by lead source. Adjust the lead scoring model or the handoff criteria based on what the data shows, not what either team believes.This cadence is the operational infrastructure of RevOps alignment. Without it, definitions drift, and the same alignment conversation happens again next year.
Common Mistakes
Writing definitions without both teams. Definitions written by marketing alone get ignored by sales. Definitions written in a joint session with sales leadership present get adopted. Involve the people who will be held accountable. Tracking MQL volume as the marketing primary metric. MQL volume incentivizes marketing to lower the qualification bar. Sourced pipeline incentivizes marketing to generate leads that actually convert. Change the primary metric before changing anything else. Skipping the reject reason requirement. If sales can reject an MQL without logging a reason, marketing has no feedback loop. The reject reason field in your CRM is not optional if you want alignment to hold. Revisiting definitions every quarter. Definitions should be stable for at least two quarters before revision. Changing them quarterly prevents either team from learning what actually works.Frequently Asked Questions
Why do marketing and sales always disagree on pipeline?
The disagreement is almost always definitional, not factual. Marketing counts leads by one set of criteria; sales qualifies them by another. Without a shared written definition of what constitutes a qualified lead and what counts as pipeline, every pipeline review becomes an attribution argument. The fix is a written service-level agreement on definitions before any metric is tracked.
What is the best joint metric for marketing and sales?
Sourced pipeline per rep is the most durable joint metric because it requires both teams to agree on what counts as sourced pipeline and it ties directly to the sales team's quota. Marketing is accountable for generating it; sales is accountable for working it. Attribution arguments collapse when both teams are measured on the same number.
How do you write an MQL definition that sales will accept?
Involve sales in drafting it. Start from the deals that closed last year and work backward to identify what signals were present before sales accepted those leads. Score for fit (company size, industry, title) separately from intent (behavior, engagement). Sales will only accept an MQL definition that matches their lived experience of what converts.
Frequently Asked Questions
Why do marketing and sales always disagree on pipeline?
The disagreement is almost always definitional, not factual. Marketing counts leads by one set of criteria; sales qualifies them by another. Without a shared written definition of what constitutes a qualified lead and what counts as pipeline, every pipeline review becomes an attribution argument. The fix is a written service-level agreement on definitions before any metric is tracked.
What is the best joint metric for marketing and sales?
Sourced pipeline per rep is the most durable joint metric because it requires both teams to agree on what counts as sourced pipeline and it ties directly to the sales team's quota. Marketing is accountable for generating it; sales is accountable for working it. Attribution arguments collapse when both teams are measured on the same number.
How do you write an MQL definition that sales will accept?
Involve sales in drafting it. Start from the deals that closed last year and work backward to identify what signals were present before sales accepted those leads. Score for fit (company size, industry, title) separately from intent (behavior, engagement). Sales will only accept an MQL definition that matches their lived experience of what converts.
See how ORM turns these insights into action
ORM builds custom revenue forecast models for B2B SaaS companies. Not dashboards. Prescriptive analytics that tell you what to do next.
Schedule a Demo