A funnel report answers one question that no other dashboard answers as cleanly: of everyone who walked in the door, where did the ones who did not buy actually fall out?
A funnel report is a visualization that shows how many prospects enter each stage of a sales or marketing funnel and what percentage advance to the next stage. It plots counts at every step (visitor, lead, MQL, SQL, opportunity, closed won) alongside the conversion rate between stages, exposing exactly where deals leak out. Teams use it to find the single stage that is quietly destroying throughput so the fix can be targeted instead of guessed.
Six things to know about a funnel report before using it to find a leak or make a staffing argument.
A funnel report pairs two numbers at every stage: the raw count of prospects currently or historically in that stage, and the conversion rate from the previous stage. The count tells you volume. The rate tells you quality. Both have to be read together because a stage can look healthy on volume while quietly bleeding on rate, or the reverse.
Most funnel reports render as a stacked funnel chart (bars narrowing from wide top to narrow bottom) or as a stage-by-stage table. The chart is better for a glance read. The table is better for the operations work because it exposes counts, rates, and absolute drops side by side, which is what the team actually argues about on a Monday pipeline review.
The job of a funnel report is to point at the stage where the business is losing the most progress and ask why. It does not fix the leak. A collapse at MQL to SQL points at lead quality. A collapse at demo to proposal points at discovery. A collapse at proposal to signed points at pricing or procurement. The report names the room. The team finds the door.
A pipeline report shows the current open deals and their forecast value right now. A funnel report shows conversion across a historical cohort of leads, including the ones that did not convert. Pipeline reports answer what is in the pipe today. Funnel reports answer what fraction of what entered the pipe is still moving through it.
A cohort report groups users or deals by the time period they entered and tracks each cohort forward. A funnel report groups by stage and tracks how a single cohort collapses from top to bottom. Both use cohort math under the hood, but the shape of the question is different. Funnel is vertical. Cohort is horizontal.
A healthy revenue team puts the funnel report on screen at every weekly pipeline review. The counts move. The rates move. The team argues about why a specific rate dropped this week and names a specific fix. The report is the backbone of the conversation because every stage number has a human reason behind it.
A funnel report is a disciplined visualization, not a bar chart. Every well-built one has the same bones: labeled stages in canonical order, counts at each stage, conversion rates between stages, absolute drop figures, and a cohort window the whole thing is measured against. Below are the pieces that must be present for the report to be trusted on a pipeline review.
The stages run from widest at the top to narrowest at the bottom in the order prospects actually move through them: visitor, lead, MQL, SQL, opportunity, qualified opportunity, proposal, closed won. The order has to match the real sales process. A report with stages out of order will mislead the reader no matter how pretty the chart renders.
Every stage shows the raw count of records that reached it in the cohort window. One hundred twenty leads, fifty MQLs, thirty SQLs, twelve opportunities, four closed won. Without the counts, a healthy-looking rate on a tiny volume is indistinguishable from a healthy rate on real volume. Both numbers have to be visible.
Between each pair of stages the report shows the conversion rate from the upper stage to the lower one. Fifty MQLs becoming thirty SQLs is a sixty percent MQL-to-SQL conversion rate. The rate is the number the team acts on, because a drop in rate is the signal that something has broken in that transition.
A good funnel report also shows the raw count of records lost between stages. Twenty leads disqualified between MQL and SQL. Eighteen opportunities closed-lost between discovery and demo. The absolute drop figure matters because a one-percent conversion rate change at the top of a one-hundred-thousand-visitor funnel is a very different problem than the same change at the bottom.
The report has to label the window it is measured over, usually a trailing thirty, sixty, or ninety days. Without the window the counts and rates are undefined. A funnel report that does not say which cohort it is measuring is a funnel report that cannot be trusted, because the numbers depend entirely on how long you let the cohort resolve.
A funnel report earns real diagnostic power when it can be sliced. Filter by source and the paid versus organic funnels split cleanly. Filter by segment and SMB versus enterprise show up as different shapes. Filter by rep and the top performer's funnel versus the team average becomes a coachable artifact. Overall funnels hide the segment-level truth.
A funnel report looks simple and reads deep. Every classic funnel-report pattern has a repeatable diagnosis. Teams that have run them for a few quarters stop guessing because the shapes repeat. Below are the common patterns and what they almost always mean when they show up on a Monday review.
A funnel that stays wide for the first two or three stages and then collapses at MQL-to-SQL or SQL-to-opportunity is a lead-quality story. Marketing is generating volume. Sales is rejecting it. The fix is upstream: tighter ideal customer profile, stricter MQL definition, better lead scoring. More leads will not help. Better fit will.
A funnel that stays healthy through SQL and then collapses between discovery and demo almost always points to weak qualification. Reps are advancing deals that never had real pain attached. The fix is a serious discovery stage with written exit criteria. The pipeline will shrink in volume. The conversion rate at every downstream stage will rise.
A funnel that stays strong through proposal and then collapses at proposal-to-signed is a late-stage story. Pricing surprises, procurement blockers, legal terms, late-arriving stakeholders. The fix is late-stage discipline: a shared deal room, a signed procurement checklist, pricing conversations earlier in the cycle, and executive sponsorship on deals above a threshold.
A funnel that bulges in the middle, with deals accumulating in a specific stage but not advancing or losing, is a stall. The cycle has stretched. Deals are not being disqualified when they should be, and they are not being closed when they could be. The fix is stage dwell-time rules and a loss reason on every deal that cannot be moved forward in a defined window.
A funnel that shows healthy counts and rates for everything except closed won usually points at a data problem, not a sales problem. Closed won is being written in a system the funnel does not read, or the stage definitions do not match actual deal flow. Audit the stage transitions and the data source before changing anything about the sales process.
A funnel with steady conversion at every stage and no obvious collapse is a healthy funnel. The constraint is volume, not conversion. The fix moves upstream to demand generation: more well-fit leads at the top, more SDR capacity, more content for the long-tail intent queries. The funnel is working. It just needs more fuel.
Teams often ask for a funnel report when they really want a pipeline report, a cohort report, or a forecast. The three answer different questions and are built on different math. Confusing them is the single most common reason a dashboard argument stalls out. Below are the clean distinctions.
A pipeline report shows the open deals in the system today, with amounts and stage weighting, used for forecast and coverage. A funnel report shows a historical cohort of all records (open, won, and lost) and how they converted stage to stage. Pipeline is what is in the pipe now. Funnel is what fraction of what entered is still moving.
A cohort report groups records by the week or month they entered and watches each cohort forward over time to measure retention, revenue, or conversion. A funnel report groups one cohort by stage and watches it collapse from top to bottom. Cohort reports are horizontal in time. Funnel reports are vertical through stages.
A forecast predicts how much revenue will close in a future period based on current pipeline, stage probability, and rep commits. A funnel report diagnoses where deals have historically leaked out. Forecasts answer what we will book. Funnels answer why we booked that much and not more. Both are needed. Neither replaces the other.
Win rate is a single number: the percentage of opportunities that reach closed won. A funnel report shows the full chain of conversion rates that produce that single number. Win rate is the summary. The funnel is the breakdown. A win rate that drops without an explanation is a funnel report waiting to be built.
An activity report measures reps' inputs: calls made, emails sent, meetings booked. A funnel report measures outcomes: records that advanced or did not. Activity reports tell you whether the team is doing the work. Funnel reports tell you whether the work is producing results. One without the other hides either effort or effectiveness.
A source report groups revenue or pipeline by where it came from (paid, organic, referral, outbound). A funnel report shows the shape of the journey independent of source. The two combine powerfully: a funnel report filtered by source exposes which channels produce the funnel shape the business actually wants.
Strkr builds the funnel report from the same cohort data the forecast runs on. Filter by source, segment, product, or rep and the shape of the funnel changes to match. Strkr AI watches the rates week over week and flags the stage that just slipped, so the pipeline review opens on the leak, not on a hunt for it.
A funnel report in sales is a visualization that shows how many prospects reached each stage of the sales process and what percentage converted to the next stage. Stages usually run from lead to MQL to SQL to opportunity to closed won. The report pairs raw counts with stage-to-stage conversion rates, so a revenue team can see both volume and quality at every step and identify exactly where deals are leaking out of the pipeline.
A pipeline report shows open deals in the system today, with amounts and stage weighting, used for forecasts and coverage calculations. A funnel report shows a historical cohort of all records (open, won, and lost) and how they converted from stage to stage. Pipeline reports answer what is in the pipe right now. Funnel reports answer what fraction of everything that entered the pipe is still moving through it, which is a different question with different math.
A cohort report groups records by the time period they entered (week, month, quarter) and watches each cohort forward over time to track retention, revenue, or conversion. A funnel report groups a single cohort by stage and watches it collapse from top to bottom. Cohort reports are horizontal through time. Funnel reports are vertical through stages. Both can share underlying cohort math, but the shape of the question each answers is different.
Start by looking at the shape of the funnel bars from top to bottom. The widest-to-narrowest step is where the biggest absolute drop happens, which is usually the first stage worth investigating. Then look at the stage conversion rates between bars for the rate drops that stand out. A collapse at MQL to SQL points to lead quality. A collapse at discovery to demo points to qualification. A collapse at proposal to signed points to pricing or procurement.
Most B2B sales funnel reports use some version of visitor, lead, MQL, SQL, opportunity, qualified opportunity, proposal, and closed won. The exact stages have to match the real sales process in use, not a generic template. Marketing funnels extend further up with visitor and engaged-visitor stages. Enterprise motions often add stages like security review or procurement review near the bottom. The order has to run from widest at the top to narrowest at the bottom.
A stacked funnel chart is the common visualization for a funnel report: horizontal bars narrowing from a wide top to a narrow bottom, each labeled with a stage name and its count. Some stacked funnel charts color-code the bars by segment, source, or product line, so the segmentation stacks visually inside each stage. The chart is good for a glance read of overall shape. A stage-by-stage table is usually better for the operations work.
A marketing funnel report shows how many visitors became leads, how many leads became MQLs, and how many MQLs were accepted by sales as SQLs. The transitions upstream of SQL are the ones marketing can influence directly. A funnel report that collapses between visitor and lead points to landing-page or offer quality. A collapse between MQL and SQL points to lead definition and scoring, which usually requires marketing and sales to realign on what qualified means.
A healthy revenue team reviews the funnel report weekly during the standard pipeline review and in more depth monthly or quarterly. The weekly review watches for rate changes that signal a new leak. The monthly or quarterly review segments the funnel by source, size, product, and rep to find patterns that only emerge at larger sample sizes. Daily review is almost never useful because stage transitions do not generate enough signal day over day to warrant it.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
