Hit 100% of your MQL goal and you can still land around 30% of your pipeline target, because MQLs convert to SQLs at roughly 13% (The Digital Bloom, 2025). That single gap is why "should marketing and sales share pipeline targets" is the wrong place to start.

The question usually gets asked as if it were about willingness. Will marketing agree to carry a pipeline number? Will sales trust the one marketing reports? But a shared target is a measurement problem before it is a cultural one. You cannot share a number the two teams count differently, and most teams count it differently without knowing it.

The pattern we keep seeing in enterprise audits: leadership announces a shared pipeline target, and two quarters later marketing is still reporting leads while sales reports pipeline. One slogan, two scorecards. The target is shared on the slide and split in the systems underneath it.

So the honest answer is yes, marketing and sales should share pipeline targets. Just not first. First you agree on what pipeline means and where both teams read it. Get the math right and the shared number becomes obvious. Skip it and the shared number becomes one more thing to argue about.

Should marketing and sales share pipeline targets?

Yes, but not as the first move. A shared pipeline target only holds when both teams define pipeline the same way and read it from the same system. Bolt the number onto MQL-era plumbing and marketing keeps reporting leads while sales reports pipeline, so the target is shared in name only. Fix the definition, then share the target.

The instinct to share a target is right. When two teams own the same number, the handoff arguments get smaller, because both sides win or lose together. The problem is sequencing. A shared target is the output of alignment, not the mechanism that creates it. Teams that lead with the number, before the definition and the source of truth exist, end up formalizing the disagreement instead of resolving it.

The tell is simple. Ask marketing what it reported to leadership last quarter, then ask sales the same question. If one answer is a lead count and the other is pipeline dollars, there is no shared target yet, whatever the plan says. The two teams are measuring different objects and calling them by the same name. A kickoff meeting will not close that, because the gap is in the definitions, not the relationship. Those definitions live in the CRM, which is where the fix has to happen and where enterprise audits keep finding the problem under otherwise clean reports (see why B2B marketing attribution is broken).

A shared number you cannot both see is not shared. So start with why it breaks.

Why do shared pipeline targets fail when teams still run on MQLs?

MQLs convert to SQLs at about 13%, so hitting 100% of the MQL number can deliver roughly 30% of the pipeline target (The Digital Bloom, 2025). An MQL goal and a pipeline goal are not the same currency, which is why marketing can win its own scorecard in the same quarter the shared pipeline comes up short.

The MQL was built as a volume metric. It rewards the top of the funnel: forms filled out, content downloaded, the occasional hand raised at a webinar. Pipeline is a value metric. It rewards qualified opportunities that sales agrees to work. When a team keeps the MQL as its operating metric and pins a pipeline target on top, it is running two systems that point in different directions. Marketing optimizes for lead volume, because that is what its dashboard shows, and the pipeline number drifts because nobody's daily work is actually aimed at it.

Dave Gross, co-founder of Moving Parade, frames the shift plainly: the old way of thinking about B2B is leads and CRM, and the new way is signal, capturing it, resolving who it belongs to, and using it downstream. Leads are a bottom-funnel event dressed up as a top-funnel one. A team that still counts leads as its primary output is measuring the wrong end of the process, then wondering why the shared pipeline number never arrives. For what high-performing teams track instead, see is the MQL dead.

The fix is not a better lead score. It is agreeing on what pipeline even means.

How do you align sales and marketing around pipeline goals?

Average targeting overlap between sales and marketing is just 16% (LinkedIn B2B Institute, 2024), so the two teams are often not even working the same accounts. Align on the definition and the source of truth first, not the number: one shared definition of pipeline, one system both teams read, then the goal set against them.

Misalignment gets treated as a behavior problem: get the teams to meet more, talk more, hand off more carefully. The evidence points the other way. When targeting overlap sits at 16%, marketing and sales are not misaligned because they dislike each other. They are misaligned because they are pointed at different accounts, scored on different metrics, and reading different systems. That is structural, and no amount of cross-functional goodwill fixes a structure.

Alignment around pipeline starts with three agreements, in order. First, a single definition of a qualified opportunity and each stage after it, written down and signed by both leaders. Second, one system of record both teams read, so the pipeline number is the same number no matter who pulls it. Third, the shared target, set against that definition and that source. The order is the point. Teams that reverse it, target first and definitions later, spend the next two quarters arguing about whose number is right.

Alignment on the definition is upstream of the KPI. Now the KPI.

How do you create shared KPIs for sales and marketing teams?

When Armorblox switched from MQL scoring to cost per opportunity, its cost per opportunity fell from about $40K to $800 (Metadata.io, 2024). Shared KPIs work the same way: measure one object at different stages, with the opportunity as the unit, not marketing's leads reported next to sales' revenue.

A shared KPI is not two teams reporting their own metric in the same deck. It is one metric both teams move, measured at the stages each is responsible for. Marketing owns pipeline created and pipeline accepted by sales. Sales owns pipeline converted to revenue. Both read from the same opportunity records, so there is no reconciliation step where the numbers quietly stop matching. The moment the unit becomes the opportunity instead of the lead, the two scorecards collapse into one.

The Armorblox case shows what changes when the unit changes. Scoring against cost per opportunity instead of cost per MQL, the team watched cost per lead fall from about $1,000 to $50 and lead-to-opportunity conversion climb from around 2% to over 30%. The spend did not get smarter overnight. The metric did. Marketing stopped optimizing for cheap leads and started optimizing for opportunities sales would actually work, which is the only version of a shared KPI that survives a quarterly review, and the number you can then take to the CFO (see how to prove marketing ROI to the CFO).

Shared KPIs assume the inputs feeding them are stable. For most teams they are not, which is the real transition.

How do you transition from MQLs to pipeline metrics?

You do not swap the metric, you rebuild the inputs under it. The transition is a plumbing project: lock stage definitions, assign opportunity ownership by rule, require a source field, capture activity on every meeting type. Change the dashboard before the inputs are fixed and the new pipeline number drifts exactly like the old one did.

The common mistake is treating the move to pipeline metrics as a reporting change. Teams rename the dashboard, retire the MQL, and declare the transition done, then find the pipeline number is as unreliable as the lead number was. The reason is that the same four inputs were broken underneath both. Stage definitions drift by rep, so a Stage 3 opportunity means one thing to one seller and something else to another. Opportunity ownership flips mid-quarter, so sourced and influenced pipeline never reconcile. The self-reported source field is blank on a large share of records. Activity capture misses most meeting types, so influenced pipeline reads low.

Fixing those inputs is the transition, and it is unglamorous work no dashboard vendor sells. This is what Moving Parade's Foundations engagement produces before any pipeline target is set or any media plan ships: the definitions, ownership, source capture, and activity tracking in place first. It is also why that measurement work holds up under CFO scrutiny two quarters later, when sales leadership rotates and the definitions would otherwise get renamed again. For the full mechanics of measuring the number once the inputs are stable, see how to measure pipeline contribution from marketing.

One move: Pull the two numbers marketing and sales each reported to leadership last quarter. If one is a lead count and the other is pipeline dollars, you do not have a shared target, you have two scorecards. Before you set a shared number, write one pipeline definition both leaders sign and name one system both teams read. Every other alignment conversation is downstream of that.

Which shared-target model fits which team?

The right model depends on how mature your pipeline data is, not on which team has more leverage. Teams without clean origin capture cannot run a sourced target yet. Enterprise teams reporting to a CFO who asks both what marketing started and what marketing touched need sourced and influenced pipeline side by side, on the same stage logic.

Frequently asked questions

Who should own the pipeline number, sales or marketing?

Both, at different stages of the same number. Marketing owns pipeline created and pipeline accepted by sales; sales owns pipeline converted to revenue. Because both read from the same opportunity records, the number reconciles instead of splitting into two competing versions at the quarterly review.

What percentage of pipeline should marketing be responsible for?

There is no universal benchmark that survives a CFO's follow-up questions. Set the share from your own conversion math, MQL to SQL to closed-won, across the last four quarters, not a number pulled from a blog. Your funnel's actual conversion rates decide what marketing can realistically carry.

Should marketing carry a revenue target?

Marketing should carry a pipeline target it can directly influence. A pure revenue target sits too far downstream to guide weekly decisions and invites the reconciliation fight, because revenue depends on sales execution marketing does not control. Pipeline created and accepted is the number marketing can own honestly.

How long does the transition from MQLs to pipeline metrics take?

It is a plumbing project, not a dashboard change. Budget one to two quarters to lock stage definitions, assign opportunity ownership, require source capture, and turn on activity tracking. The pipeline number is not trustworthy until those four inputs are fixed, no matter how fast you rename the report.

What is a shared pipeline target?

One pipeline number both teams commit to, defined the same way and read from the same system, measured at the stages each team owns. It is not marketing's lead count reported next to sales' revenue in the same deck. If the two teams cannot pull the same number from the same place, the target is not yet shared.