The Agreed Funnel Model: One Revenue Funnel Both Marketing and Sales Own

Marketing presents their funnel. Sales presents their pipeline. Both look right. Neither matches the other. And at the end of the quarter, nobody agrees where revenue came from.

This is the parallel-funnel trap. Marketing tracks leads through stages they defined: visitor, inquiry, MQL. Sales tracks deals through stages they defined: discovery, proposal, negotiation, closed. The two systems share a CRM but not a shared understanding of what each stage means, who owns it, or how leads are supposed to move from one world to the other.

The handoff between those two funnels, the moment marketing says "here's a qualified lead" and sales says "I'll take it from here," is where accountability disappears. Marketing measures volume. Sales measures conversion. Nobody measures the gap.

The agreed funnel model fixes this by replacing two parallel systems with one shared model that both teams contribute to, both teams can read, and both teams are held to.

Why Two Funnels Exist

Gartner research on sales and marketing alignment identifies separate funnels as the single most common reason revenue teams report misalignment. 47% of companies cite it as the primary structural problem.

The parallel-funnel problem isn't a failure of people. It's a structural outcome of how marketing and sales functions evolved separately.

Marketing adopted automation platforms (Marketo, HubSpot, Pardot) that were designed around a marketing funnel: attract, engage, nurture, qualify. Those platforms define stages in marketing terms and report on marketing metrics (traffic, MQLs, nurture rates).

Sales adopted CRM systems (Salesforce, Pipedrive, HubSpot CRM) designed around a sales pipeline: qualified, discovery, demo, proposal, negotiation, close. Those systems define stages in sales terms and report on sales metrics (pipeline value, stage velocity, win rate).

Both systems report into the same revenue goal. Neither was designed to connect cleanly with the other.

Then comes the goal structure: marketing is measured on leads generated, sales is measured on revenue closed. Different KPIs encourage different behaviors. Marketing wants volume. Sales wants quality. Each defines "good" in terms of their own measurement system.

The result is two teams looking at different dashboards, using different stage names, and operating under different definitions of what "qualified" means. No one deliberately designed this. It just accumulated. The marketing-sales alignment glossary is often the fastest fix, a shared reference for what MQL, SQL, and ICP mean in your company specifically.

Key Facts: Funnel Alignment and Revenue Impact

• Companies with tightly aligned sales and marketing functions achieve 24% faster revenue growth and 27% faster profit growth over a three-year period, according to SiriusDecisions research.
• Organizations that define a formal, shared lead lifecycle see 36% higher customer retention rates and 38% higher sales win rates, per Aberdeen Group.
• Only 46% of B2B companies report having a formally documented lead lifecycle with agreed stage definitions across marketing and sales, according to Demand Gen Report.
• Marketing and sales teams that share a common revenue process generate 208% more revenue from their marketing efforts, per MarketingProfs.
• Companies that use a single CRM as the source of truth for both teams are 3x more likely to report strong alignment than those using separate systems, per Salesforce State of Sales data.

The Agreed Funnel: Stage-by-Stage Definitions

The Unified Revenue Funnel Framework

The Unified Revenue Funnel replaces two parallel systems (marketing funnel + sales pipeline) with one shared model, seven stages, and explicit joint ownership at every transition. Its defining feature is that both teams, marketing and sales, contributed to, signed off on, and are measured against the same stage definitions and conversion benchmarks.

The seven stages: Visitor/Unknown, Inquiry/Raw Lead, MQL, SAL (optional), SQL, Opportunity/Active Deal, Closed Won/Closed Lost

Each stage has three documented elements: what marketing owns, what sales owns, and what both own jointly. Without all three, ownership gaps compound into revenue attribution fights.

The agreed funnel model has seven stages. Each has a single, documented definition both teams accept. Each has a clear owner: marketing, sales, or shared.

The SAL stage is optional. It adds value when there's genuine review complexity at handoff, when the qualification criteria are nuanced and sales needs time to assess before committing. It adds friction when it becomes a buffer for slow follow-up. If your SAL stage routinely ages past 48 hours, remove it.

The key to making this table work isn't the definitions themselves. It's the joint agreement on them. Both teams need to have reviewed and signed off. When a lead is stuck at MQL for three weeks, both teams can look at the same table and diagnose why. The MQL definition framework specifies exactly what signals a lead needs before it enters that stage.

Agreement Points at Each Stage

Defining stages is the easy part. Defining who owns what at each stage is where the real work happens.

For each stage, you need three things documented: what marketing is responsible for, what sales is responsible for, and what both teams are jointly responsible for.

Inquiry / Raw Lead:

• Marketing owns: capturing contact info, enriching basic data, initial scoring
• Sales owns: nothing yet (this is a pre-sales stage)
• Shared: SLA for when a raw lead should be scored (typically 24 hours of capture)

MQL:

• Marketing owns: nurture sequence, scoring maintenance, passing to SQL when threshold is met
• Sales owns: nothing yet (but should have visibility for strategic accounts)
• Shared: Agreement on MQL definition; quarterly review of whether the definition is calibrated

SQL:

• Marketing owns: clear handoff documentation, context passed with the lead
• Sales owns: first touch within SLA, disposition within defined window, structured feedback on rejections
• Shared: Review of SQL-to-opportunity conversion rates monthly; threshold adjustment if conversion drops

Opportunity:

• Marketing owns: supporting materials, case studies, competitive intel on request
• Sales owns: advancing or closing the deal
• Shared: Closed-loop reporting (sales updates CRM with outcome and source attribution)

Closed Won / Closed Lost:

• Marketing owns: analyzing win/loss patterns by source, channel, ICP segment
• Sales owns: loss reason documentation, source attribution verification
• Shared: Quarterly win/loss review meeting with data from both systems

The CRM as single source of truth is what makes joint ownership possible. If both teams are looking at different systems, shared accountability at each stage breaks down.

Quotable: B2B companies with tightly aligned marketing and sales functions achieve 24% faster revenue growth and 27% faster profit growth over three years, according to SiriusDecisions research. The structural mechanism is a shared funnel model, not just better communication.

Conversion Rate Benchmarks by Stage

Conversion benchmarks give you a baseline to measure against. Without them, you can't tell whether a 30% MQL-to-SQL rate is good, bad, or typical for your motion.

These are industry ranges for B2B SMB and mid-market. Your actual numbers will vary by channel mix, ICP quality, and product complexity.

These benchmarks are ranges, not targets. The goal isn't to hit industry average. It's to measure your current rates, understand why they're where they are, and improve them deliberately. McKinsey's full-funnel marketing research shows that teams who optimize across the full funnel, not just top or bottom, achieve 15-20% higher marketing ROI than those who treat each stage in isolation. For the SQL-to-opportunity part of the table, the lead-to-opportunity conversion benchmarks give you additional context from the pipeline side.

To calculate your own baseline, pull three months of clean data from CRM. Count leads at each stage by entry date (not current status). Divide downstream counts by upstream counts. Do this for each source and channel separately, because aggregate numbers often hide serious problems in specific channels. A joint pipeline review cadence is the operational rhythm that keeps both teams aligned on these numbers.

The Funnel as a Shared Dashboard

The agreed funnel only drives alignment if both teams are looking at the same data at the same time.

A shared dashboard should show:

• Current count at each stage (by week or month)
• Stage-to-stage conversion rates for the current period vs. prior period
• Average time in stage (velocity metric)
• Volume by source or channel

Both teams review this dashboard in the same weekly meeting. Not separate reviews. Not marketing's report followed by sales' report. One view, one conversation.

The weekly rhythm matters. A quarterly review catches problems months after they've compounded. A weekly review catches stage bottlenecks while they're still correctable.

When stage counts or conversion rates move, the shared dashboard makes the conversation productive: "MQL-to-SQL dropped from 45% to 28% this month. Is that a quality change, a definition change, or an SLA problem?" Both teams look at the same number and diagnose together.

The closed-loop reporting process feeds the downstream half of this dashboard: win/loss data, source attribution, deal progression velocity.

Quotable: Marketing and sales teams that share a common revenue process generate 208% more revenue from marketing efforts than teams operating with separate funnels, per MarketingProfs research on cross-functional alignment.

Where the Funnel Breaks Down in Practice

Even with agreed definitions, three execution problems consistently undermine the model.

Stage-skipping. Sales creates opportunities directly from contacts without marking them as SQL first. Forrester's research on merging the marketing and sales funnel identified stage-skipping as one of the most persistent structural breakdowns. When teams don't share a single lifecycle model, each team defaults to their own stage definitions. Marketing creates SQLs for contacts who never went through an MQL stage. When stages get skipped, conversion data is meaningless. You can't calculate MQL-to-SQL rate if half the SQLs never had an MQL stage.

Fix: Enforce required field completion before stage advancement. In Salesforce, you can gate stage transitions on minimum required fields. In HubSpot, lifecycle stage automation can enforce sequencing.

Status lag. A lead is SQL in reality but still shows as MQL in the CRM because nobody updated it. Or a deal closed weeks ago but the opportunity is still "negotiation" in the pipeline.

Fix: Stage advancement SLAs. SQL disposition within 10 business days (advance or return). Opportunity close date must be updated within 1 business day of actual close. When status lag is audited monthly, it self-corrects.

Deal stages that don't map to lead stages. Sales pipeline stages (Discovery, Demo, Proposal, Negotiation) are granular sub-stages within the "Opportunity" funnel stage. They're useful for pipeline management but don't correspond to funnel stages in a way that connects cleanly to marketing's lead lifecycle.

Fix: Keep the two stage sets separate but connected. Funnel stages (Visitor through Closed Won) are the shared model both teams use. Deal sub-stages are internal to sales for pipeline management. Report on funnel stages for alignment conversations; use deal sub-stages for sales coaching.

Marketing Funnel vs. Sales Pipeline vs. Unified Revenue Funnel

Most revenue teams didn't choose to have two separate systems. They accumulated. Understanding what each model optimizes for helps explain why the unified approach produces better outcomes.

The unified model doesn't eliminate either system's tooling. It aligns the definitions, handoffs, and reporting layer that sits on top of both.

Rework Analysis: Teams that consolidate to a single agreed funnel consistently report two early gains: fewer "lead quality" arguments in weekly meetings (because both teams are looking at the same conversion data), and faster identification of funnel bottlenecks (because stage-skipping and status lag become visible in a shared dashboard). The harder work is the governance: quarterly calibration meetings and version-controlled stage definitions. Most teams skip the governance and then wonder why the funnel model drifts after six months.

SMB vs. Mid-Market Funnel Shapes

The same seven-stage model applies at both SMB and mid-market, but the shape and velocity look very different.

SMB funnel characteristics:

• Shorter cycle: Visitor to Closed Won in 2-8 weeks
• Fewer stages matter in practice: MQL → SQL → Closed often skips extended opportunity stages
• Higher velocity: More leads, faster dispositions, lower ACV
• SAL stage usually unnecessary: decision cycle is short enough that full SQL commitment makes sense
• Conversion rates tend to be higher at later stages (simpler decisions, fewer stakeholders)

Mid-market funnel characteristics:

• Longer cycle: 3-9 months from first touch to close
• More gates matter: SAL stage can add genuine value when qualification is complex
• Multi-stakeholder: A single opportunity may involve 3-7 decision-makers, each at different funnel stages
• Lower volume, higher ACV: Each lead deserves more marketing support and sales attention
• Intent signals need more context: Mid-market buyers research longer before showing hand

If your company sells to both segments, consider separate funnel models with different conversion benchmarks and SLAs. Measuring SMB and mid-market against the same thresholds produces misleading data. The alignment for SMB vs. enterprise article covers how to adapt the funnel model for each motion. And the lead lifecycle stages from the lead management side help clarify how pre-funnel nurture feeds the agreed model at the top of the funnel.

Maintaining the Model

The agreed funnel is not a one-time document. Markets change. Channels change. Product changes. Your ICP might shift. Any of those can make your stage definitions or conversion benchmarks stale.

Quarterly calibration meeting:

• Review conversion rates at each stage against prior quarter and prior year
• Identify any stage where conversion has moved more than 10 percentage points
• Check whether stage definitions still reflect how the team actually behaves
• Update thresholds if data supports it, with both teams' sign-off

Trigger for out-of-cycle review:

• New channel launched that generates a materially different lead type
• Sales or marketing leadership change
• Product launch that changes ICP or buying process
• Significant conversion rate movement that doesn't have a clear seasonal explanation

What to do when stage definitions drift: Stage definitions drift when individual contributors use them inconsistently over time. The definition says "MQL requires 2 fit signals and 1 intent signal" but reps have been accepting MQLs based on job title alone for six months.

When you detect drift, run an audit: pull the last 90 days of leads that hit each stage and check them against the documented criteria. Count the percentage that wouldn't have qualified under the actual definition. If drift is above 20%, you need either a re-training session or a definition update that reflects how the team actually works. The alignment maturity diagnostic can help you spot systemic drift before it compounds. The common alignment failures guide covers the most frequent root causes and the fixes that actually stick.

The SQL definition and acceptance document is the downstream companion to the funnel model. It defines what the SQL stage specifically requires and what acceptance commits to.

The Bottom Line

Two funnels that never connect are the root cause of most revenue attribution fights, lead quality debates, and quarter-end finger-pointing.

A single agreed model doesn't eliminate disagreement. But it changes the disagreement from "your leads are bad" vs. "your follow-up is slow" to "our MQL-to-SQL conversion dropped 12 points. Let's find the cause."

The difference between those two conversations is the difference between teams that protect their territory and teams that fix their process.

Build the model together. Review it in the same room. Hold both teams to the same dashboard. When numbers move, look at the system, not the other team.

Frequently Asked Questions

What is an agreed funnel model?

An agreed funnel model is a single, jointly owned revenue funnel that replaces separate marketing and sales tracking systems. Both teams define each stage together, share conversion benchmarks, and review the same dashboard in the same meeting. The key word is "agreed." Both VP Marketing and VP Sales sign off on stage definitions, ownership rules, and acceptance SLAs.

How is the agreed funnel different from a marketing funnel or a sales pipeline?

A marketing funnel tracks leads through marketing-owned stages (visitor, inquiry, MQL) and optimizes for lead volume. A sales pipeline tracks deals through sales-owned stages (discovery, proposal, close) and optimizes for revenue. An agreed funnel model bridges both by creating shared stage definitions at the handoff point, where marketing passes qualified leads to sales, and a single dashboard both teams read from.

What is a good MQL-to-SQL conversion rate?

For B2B SMB, a healthy MQL-to-SQL rate runs 30-60%. For mid-market, the range is 25-50%. Below 25% in either segment typically signals that the MQL definition is too loose. Marketing is passing leads that don't meet the SQL criteria sales needs to advance them. The goal isn't the industry average; it's to understand why your rate sits where it does, then improve it deliberately.

How often should we review the funnel model?

At minimum, quarterly. The quarterly calibration meeting should review conversion rates at each stage against the prior quarter, check whether stage definitions still reflect how the team actually behaves, and update thresholds if data supports it. Out-of-cycle reviews are triggered by: new channel launch, leadership change, product launch, or significant unexplained conversion rate movement.

What causes funnel stage drift?

Stage drift happens when individual contributors use stages inconsistently over time, often because the original definitions aren't documented clearly, managers stop enforcing them in reviews, or the team grows and new hires aren't trained on the agreed model. Detect drift by auditing the last 90 days of leads against the documented criteria. If more than 20% wouldn't qualify under the actual definition, you have drift and need either retraining or a definition update.

Should SMB and mid-market use the same funnel model?

The seven-stage structure applies to both, but the conversion benchmarks, SLAs, and SAL-stage need should be calibrated separately. SMB funnels move faster (2-8 weeks end to end) and have fewer stakeholders; mid-market funnels run 3-9 months with multi-stakeholder decisions. Measuring both against the same thresholds produces misleading data that obscures real problems in one segment.

Learn More

• MQL Definition Framework
• SQL Definition and Acceptance
• Joint Pipeline Review Cadence
• Closed-Loop Reporting Explained
• CRM as Single Source of Truth
• Lead Lifecycle Stages
• Marketing-Sales Alignment Glossary