Built for sales teams designing funnels

Twelve sales funnel examples that actually ship, with the pipeline template behind each one.

When buyers search for sales funnel examples, most results give the same AIDA diagram and a Canva template that nobody actually runs. This page documents twelve working pipeline shapes we see on Strkr accounts right now, with the stage counts, the conversion ranges, and the automation that keeps each one honest. Copy the template that fits your motion, or clone it on the Strkr free trial and start logging deals.

Start free trial See pricing
What this audience is actually dealing with

The pains that bring buyers here.

Funnel design is one of those topics where every blog post sounds authoritative and almost none of them hand you something you can run on Monday. The AIDA model (awareness, interest, desire, action) is a 1898 copywriting framework, not a pipeline configuration. The TOFU/MOFU/MOFU inversion of marketing funnel vocabulary onto sales is a content-marketing artifact. What a sales team actually needs is a stage sequence that matches how buyers decide, with exit criteria that the rep can defend in a pipeline review and conversion math that lets the forecast land. Below are the six places most funnel examples go wrong, with what we see on real customer accounts instead.

The AIDA diagram problem

The template every blog post ships is a copywriting model.

AIDA (awareness, interest, desire, action) was E. St. Elmo Lewis's 1898 ad-copy heuristic. Mapping it onto a modern sales pipeline collapses discovery, validation, decision, and procurement into one stage called "desire," which is where most pipelines leak the most money. The useful funnel examples below start from decision-journey research, not from Victorian ad copy.

Stage count sprawl

Eleven-stage funnels nobody updates past stage 3.

Teams that borrow a Pipedrive or HubSpot template with 10+ stages end up with reps who update through "Qualified" and then skip to "Closed Won," which breaks every forecast rolled up from the pipeline. The working funnels below sit at 5 to 7 stages with exit criteria written in plain English, and the reporting runs off time-in-stage because that is the leak signal.

Marketing funnel borrow

TOFU, MOFU, BOFU is a content taxonomy.

Top-of-funnel, middle-of-funnel, bottom-of-funnel labels came from inbound-marketing playbooks and describe content assets, not sales motions. A sales funnel describes the deal journey from first qualified conversation to signature, which has its own stages (discovery, demo, technical validation, procurement, security review, sign) that do not map cleanly to the content buckets.

Weighted pipeline fiction

Multiply the deal value by the stage probability.

The classic weighted-pipeline math (stage probability times deal value) is a historical artifact from Siebel. Modern forecasting uses rep commit plus time-in-stage decay plus deal-health signals, which is why the strongest funnel examples below separate the pipeline-health view (deal aging, no-activity-in-7-days flag, stakeholder gaps) from the forecast view entirely.

Exit-criteria vagueness

When exactly does a deal move from stage 2 to stage 3.

A stage without exit criteria is a kanban column with a label. The best funnels we see list 3 to 5 explicit exit criteria per stage (identified economic buyer, confirmed budget range, written success criteria) that the rep checks off and the pipeline review can audit. The examples below carry the full exit-criteria list for each stage.

No conversion benchmarks

The template never says what good looks like.

Shipping a 7-stage funnel without stage-to-stage conversion ranges tells the sales leader nothing about where to invest coaching. Each example below lists the typical conversion range we see on healthy Strkr accounts for that motion, so a new team can calibrate against something real instead of trusting a benchmark report from a vendor selling consulting.

The twelve working funnel shapes

Templates grouped by motion.

Across roughly 2,100 B2B accounts we see twelve recurring funnel shapes. Each one has stage counts that stay stable (we track changes), exit criteria that reps actually use, and a conversion profile that benchmarks hold against. The cards below give the short version. The playbooks section further down walks through three in operational detail.

B2B SaaS mid-market

Six-stage demo-led motion.

Qualified lead, discovery call, demo, technical validation, procurement, closed won/lost. Typical lead-to-close conversion runs 8 to 14 percent at the mid-market end. Time-in-stage averages 11 days in discovery, 18 days in demo, 24 days in technical validation, and 32 days in procurement. The leak is almost always technical validation to procurement when a security review surfaces late.

B2B SaaS enterprise

Eight-stage multi-threaded motion.

Opportunity, discovery, multi-threaded qualification, demo cycle, business case, procurement, security review, legal, closed. Lead-to-close runs 4 to 7 percent at enterprise. Deal cycle 180 to 330 days. The two reliable leaks are discovery-to-multi-threaded (champion never introduces finance) and legal review when the MSA has aggressive liability terms.

Outbound SDR to AE

Four-stage prospect handoff.

Prospected account, booked meeting, qualified opportunity, closed. SDR owns stages 1 and 2; AE picks up at stage 3 after a formal handoff with 5 required discovery fields filled. Prospected-to-meeting runs 1.5 to 4 percent on cold outbound at 2026 reply rates. Meeting-to-qualified runs 55 to 70 percent on a good SDR team.

Product-led growth

Signup-to-paid five-stage.

Signup, activated (hit the aha event), expanded (added seats or usage), qualified for sales touch, closed expansion. The funnel runs in-product most of the way, with sales entering at the qualified stage when usage crosses a threshold. Signup-to-paid runs 2 to 6 percent across most PLG SaaS. Sales touches lift expansion conversion 40 to 90 percent.

Agency new business

Five-stage pitch pipeline.

Inquiry, qualification call, scope and proposal, pitch meeting, signed statement of work. Inquiry-to-signed runs 10 to 25 percent at the inbound end, lower on outbound. Average cycle 42 days. The leak concentrates between proposal and pitch meeting when the agency sends a scope that goes past the prospect's mental budget without a conversation first.

Field sales territory

Seven-stage account-based.

Target account, meeting booked, discovery, business case, pilot or POC, procurement, closed. The POC stage is where the funnel differentiates: adding a defined pilot (30-day scoped engagement with success criteria) lifts POC-to-closed conversion from roughly 45 percent on open-ended trials to 72 percent on scoped pilots. Average cycle 120 to 180 days.

Transactional SMB

Three-stage self-serve plus call.

Trial started, trial-to-paid conversation, closed. The trial-to-paid conversation runs 20 to 30 minutes, happens inside the trial window (days 7 to 12), and converts at 20 to 35 percent. The funnel works when the trial has a defined activation path and the sales touch lands at a specific usage moment, not at a time-based reminder.

Partner-sourced

Six-stage with partner handoff.

Partner-sourced lead, qualification, co-selling discovery, demo, partner-approved procurement, closed. The partner-sourced funnel outperforms direct-outbound at the mid-market by 2.3x on close rate because of the trust transfer. The main design decision is whether the partner stays in the deal through close (recommended) or hands off at qualification (common but weaker).

Expansion / renewal

Four-stage inside the customer base.

Expansion opportunity identified, usage review, expansion proposal, closed expansion. Separate from the new-business pipeline because the metrics (gross retention, net retention, expansion win rate) and the ownership (customer success plus account manager) differ. Expansion pipelines convert at 50 to 75 percent, 3 to 10x new-business rates.

The pipeline primitives that make funnels run

What Strkr builds in to every pipeline template.

Picking the right funnel shape is step one. Keeping the pipeline healthy is where most teams drop the thread. The cards below are the specific pipeline primitives Strkr ships that keep each of the funnel examples above running without the Monday morning sync being a wall of stale deals.

Stage exit criteria

Checklist gates the rep works through.

Each stage carries 3 to 5 exit criteria written in plain English (identified economic buyer, confirmed budget range above 25k, written success criteria shared) that render as a checklist on the deal record. A deal cannot auto-advance past a stage with unchecked criteria without a reason code. The pipeline review opens with the aging + unchecked-criteria report.

Time-in-stage decay

Aging deals surface before the forecast lies.

Every deal carries a per-stage time-in-stage timer. When a deal exceeds the stage's 90th-percentile duration (calculated from the account's own history, not vendor benchmarks), it flags as aging and drops to the bottom of the kanban. Reps see the aging stack first thing Monday. Managers run the Monday pipeline review from the aging report.

Deal-health signals

No activity in 7 days triggers the flag.

A deal with no activity (no logged call, meeting, or email) in 7 days surfaces as a health risk. Deals with activity but no stakeholder engagement (contact replies, meeting bookings, document opens) for 14 days flag as single-threaded risk. The signal fires on the deal record and summarizes on the Monday pipeline review.

Weighted + commit forecast

The sum of commit and the stage-weighted roll.

The forecast view shows rep commit (explicit "I will close this quarter"), best case (commit plus likely), and the stage-weighted roll separately. Finance planning runs on commit. Sales leader coaching runs on the delta between commit and stage-weighted (large delta means the pipeline is light; the rep is sandbagging; or the stages are miscalibrated).

Multi-threaded stakeholder map

The deal record shows who is actually in.

Each deal carries a stakeholder map with roles (economic buyer, champion, technical evaluator, procurement, security). A role left unfilled past a stage threshold flags as a stakeholder gap. The map renders on the deal record and on the Monday pipeline review so coaching conversations surface the actual gap instead of generic "multi-thread it" advice.

Loss-reason capture

Closed lost deals carry structured reasons.

A closed-lost deal requires a structured loss reason from a maintained list (lost to competitor X, no decision, lost to internal build, lost on price, lost on timing) plus a free-text annotation. The loss-reason report runs quarterly and feeds the funnel-redesign conversation. "No decision" is almost always the largest bucket and the one worth attacking first.

Pipeline coverage ratio

The 3x rule, measured against commit.

Pipeline coverage shows the ratio of open-pipeline value to quota commit for the current quarter. 3x is the common rule of thumb, though mature teams land closer to 2.2x and inexperienced teams need 4x+ because their qualification is weaker. The coverage view breaks out by stage so leadership sees whether coverage is sitting in late stages (closable) or early stages (optimistic).

Playbook attachment

Templates fire on stage entry.

When a deal enters a stage, Strkr can fire an attached playbook: tasks assigned, email templates queued, meeting-prep documents generated. The playbook library sits per pipeline so the enterprise motion runs different playbooks than the SMB motion. New reps ramp faster because the stage transition tells them what to do next.

Stage conversion reporting

Every stage transition tracks a rate.

The pipeline reporting shows stage-to-stage conversion rates with 30/60/90-day trends and per-rep variance. Where one rep converts 40 percent at discovery-to-demo and the team averages 65 percent, the coaching conversation has evidence. Where the team conversion drops versus prior quarter, the funnel-redesign conversation has evidence.

The design decisions behind each funnel

What drives the shape beyond the stage count.

Beyond "how many stages," six design decisions determine whether a funnel actually runs. The cards below walk through each with the typical answer and the trade-off.

Single vs multi-pipeline

One funnel per motion, not one for everything.

A team running new business, expansion, and partner-sourced motions needs three pipelines, not three stages inside one pipeline. Each pipeline carries its own stages, exit criteria, and reporting. Strkr supports unlimited pipelines on every tier so the design decision is not a cost decision; it is a reporting-clarity decision.

Opportunity vs account record

What the forecast actually rolls up to.

Enterprise motions roll multiple opportunities under one account (expansion, cross-sell, renewal). SMB motions often have one opportunity per account. The forecasting primitive differs: enterprise rolls from the account; SMB rolls from the opportunity. Strkr's pipeline template picks the right primitive on the discovery call so the reporting lands correctly from day one.

Deal source attribution

Where does the credit go when a deal has multiple touches.

A deal that started with an outbound email, got reactivated by a webinar, and closed through a partner introduction has three legitimate sources. Strkr tracks first-touch, last-touch, and multi-touch attribution separately. The sales ops conversation about marketing-sourced vs sales-sourced quota is a reporting toggle, not a database refactor.

Rep ownership transitions

SDR, AE, CSM, account manager handoffs.

Handoff moments break more pipelines than any other category of design error. A clean handoff requires 5 to 8 required fields (confirmed budget range, timeline, decision process, written success criteria) plus a handoff meeting with both reps present. Strkr enforces the fields at the stage transition and generates the handoff meeting invite automatically.

Approval gates

When does leadership have to touch the deal.

Discounts above a threshold, deals above a value, pilots with custom scope, MSAs with legal redlines all trigger approval gates. Strkr's approval workflow routes the request to the right approver with the deal context attached, logs the decision, and advances the deal when approved. The CRO stops being the bottleneck without losing the oversight.

Pipeline review cadence

Monday or Friday, deal review or forecast call.

Monday pipeline reviews surface aging deals and set the week's focus. Friday forecast calls update commit for the leader's roll-up. Quarterly pipeline reviews redesign the funnel if conversion rates have shifted. Strkr's pipeline-review workspace carries a saved layout per cadence so the review opens to the right view every time.

Head-to-head

Strkr pipeline templates vs the typical HubSpot or Pipedrive setup.

HubSpot and Pipedrive both ship with default sales pipelines and some template options. The difference shows up in how the stages carry exit criteria, how aging surfaces, and how multi-pipeline teams keep clean. Here is the direct comparison for a team evaluating pipeline tooling.

Feature Strkr HubSpot default pipeline
Pipeline count on paid tiers Unlimited on every paid tier 2 on Starter, 15 on Professional, 100 on Enterprise
Stage exit criteria Required-field checklist with reason-code override Required properties, no checklist render
Time-in-stage aging Per-stage 90th-percentile from account history Days in stage field, no auto-flagging
Deal health signals 7-day no-activity flag plus stakeholder-gap flag Deal insights on Enterprise tier
Multi-pipeline reporting Per-pipeline conversion with trend overlay Per-pipeline reports with limits
Playbook attachment Stage-entry trigger with task + template + meeting fire Playbooks product on Enterprise tier
Weighted + commit split Rep commit, best case, stage-weighted shown separately Deal forecast categories on Sales Hub Pro+
Loss reason structure Required picklist + free-text with quarterly rollup Closed lost reason property, custom report
Pipeline coverage view Open pipe vs commit by stage, with coaching flags Forecast tool on Sales Hub Pro+
Template library Twelve pipeline shapes with motion-tagged exit criteria Default pipeline, templates via marketplace
How teams use Strkr

Three funnel templates in operational detail.

The cards above summarize twelve funnel shapes. The three below are the ones most new Strkr customers clone first, with the stage-by-stage breakdown that lets a sales ops lead rebuild the funnel on Strkr in an afternoon.

B2B SaaS mid-market, six stages

Qualified lead to closed won, 90-day cycle.

Stage 1 Qualified Lead: identified contact at target-profile company, inbound or outbound sourced, no exit criteria beyond identification. Stage 2 Discovery Call: 30-minute call booked and held, five discovery fields complete (role, pain, timeline, budget band, current state), next steps scheduled. Stage 3 Demo: tailored demo delivered to the discovery contact plus one, demo recording shared, three technical questions answered in writing. Stage 4 Technical Validation: security review initiated, two integration questions scoped, success criteria written. Stage 5 Procurement: MSA sent, pricing confirmed, legal contact identified, close date within 30 days. Stage 6 Closed Won: countersigned MSA, kickoff booked. Conversion ranges across healthy accounts: 70 percent qualified-to-discovery, 55 percent discovery-to-demo, 50 percent demo-to-validation, 45 percent validation-to-procurement, 72 percent procurement-to-close.

Outbound SDR to AE, four stages

Prospected account to closed, with handoff gate.

Stage 1 Prospected: account in territory, three stakeholder contacts enriched, outbound sequence started. Stage 2 Meeting Booked: 30-minute discovery meeting on the calendar with the right persona (not an admin), confirmation email received. Stage 3 Qualified Opportunity: discovery meeting held, five handoff fields filled by SDR, AE assigned, SDR drops off except for the paid-SPIFF trailing credit. Stage 4 Closed Won: AE-owned, standard new-business motion to close. The SDR handoff gate is the critical design: meeting-held without the five fields filled bounces back to the SDR, not forward to the AE. Strkr enforces the fields at the handoff transition. Benchmark conversions: 2 percent prospected-to-meeting (cold), 62 percent meeting-held-to-qualified, 32 percent qualified-to-closed.

Agency new business, five stages

Inquiry to signed statement of work.

Stage 1 Inquiry: form fill, referral, or inbound contact, assigned to a new-business lead. Stage 2 Qualification Call: 20-minute call, budget band confirmed (within our minimum), timeline inside next quarter, scope roughly scoped. Stage 3 Scope and Proposal: discovery deepened, scope written, proposal document drafted with case-study attachments. Stage 4 Pitch Meeting: 60-minute meeting with the economic buyer plus the day-to-day owner, proposal walked through, questions handled, next steps agreed. Stage 5 Signed SOW: countersigned statement of work with 30/50/20 payment schedule. The agency pattern leaks most at Scope and Proposal to Pitch Meeting (prospect ghosts after reading proposal) which is almost always because the scope went past their mental budget. The playbook moves the budget conversation one stage earlier.

Product-led growth, five stages

Signup to expansion revenue.

Stage 1 Signup: product-created account, activation path begins. Stage 2 Activated: hit the aha event (first automation shipped, first team invited, first integration connected, varies by product). Stage 3 Expanded: added a second seat, hit a usage threshold, or added a workspace. Stage 4 Qualified for Sales Touch: usage above threshold, team size above 10, in a target-fit segment. AE assigned, discovery scheduled. Stage 5 Closed Expansion: contracted on an annual plan with multi-seat commitment. The specific design decision is where sales enters: too early and PLG economics break; too late and expansion revenue leaks. Benchmark is to engage at stage 4 with the team at 10+ seats and usage above the activation threshold.

Field sales territory, seven stages

Target account to closed with POC gate.

Stage 1 Target Account: in the territory's named account list, with a defined entry motion (meeting, event, intro). Stage 2 Meeting Booked. Stage 3 Discovery: multi-stakeholder, written pain, written success criteria. Stage 4 Business Case: ROI model built, procurement contact identified, timeline confirmed. Stage 5 Pilot or POC: 30-day scoped pilot with 3 success criteria, defined start, defined evaluation. Stage 6 Procurement: pilot evaluation complete, procurement motion begins, legal engaged. Stage 7 Closed Won. The POC stage is where field sales teams win or lose: open-ended trials convert at 45 percent; scoped pilots with written criteria convert at 72 percent. The template enforces the written criteria at stage entry.

Clone a working sales funnel template today.

Start a 14-day free trial, clone one of the twelve pipeline templates documented above, and begin logging deals against the exit criteria that actually move pipeline. No credit card, no sales-managed onboarding required. The pipeline primitives (aging, deal health, stakeholder-gap flags, weighted-plus-commit forecast) are available on every tier.

Start free trial See pricing
Common questions

What buyers in this bucket ask most.

How many stages should a sales funnel have?

For most B2B motions, 5 to 7 stages. Fewer than 5 and the stages carry too much pipeline weight at any one time, which collapses the reporting granularity. More than 8 and reps stop updating past the fourth stage because the overhead exceeds the perceived value. The right number for your team depends on cycle length (longer cycles support more stages) and the number of discrete gates (handoffs, approvals, pilots) that actually matter to how your deals move. The twelve examples above range from 3 stages (transactional SMB) to 8 stages (enterprise multi-threaded), and each stage count is justified by the motion.

What is the difference between a sales funnel and a sales pipeline?

The two terms are used interchangeably in most of the industry, but strictly speaking the funnel is the shape (the conversion rates between stages that produce the narrowing from top to bottom) and the pipeline is the inventory (the actual deals sitting in each stage right now). You design the funnel when you set up stages and exit criteria. You manage the pipeline when you work the deals that are sitting in those stages. A healthy funnel produces predictable conversion rates; a healthy pipeline is one where enough deals exist at each stage to roll up to the quota commit at the healthy conversion rates.

Can I copy one of these funnel templates into Strkr?

Yes. Each of the twelve funnel shapes in the first section ships as a cloneable pipeline template in the Strkr free trial. Clone the one that matches your motion, rename the stages to your language, adjust the exit criteria to your gates, and start logging deals. Most teams tune the stage names and the exit criteria in the first 2 to 3 weeks and then leave the structure stable for 6 to 12 months before the next redesign. Template cloning does not lock you in; you can delete, duplicate, and modify freely.

How do I know if my sales funnel is leaking?

Three signals: stage-to-stage conversion rates below the benchmark for your motion (compare against the ranges in the first section), time-in-stage averages exceeding 90th-percentile duration for a healthy run, and a loss-reason distribution dominated by "no decision" instead of competitive loss. The leak is almost always at one specific transition rather than spread evenly across the funnel. Finding it is a reporting exercise, which is why the pipeline primitives in the second section exist: without aging flags and stakeholder-gap flags, the leak is invisible until a quarter ends short of quota.

Should marketing and sales share one funnel or run separate ones?

Separate. Marketing runs a demand funnel measured in leads, MQLs, SQLs, and pipeline sourced. Sales runs a deal funnel measured in opportunities and revenue. The handoff is at the MQL-to-SQL boundary where marketing hands a qualified lead to sales, and both sides agree on what qualified means. Trying to run one unified funnel conflates two different measurement systems and typically ends with the sales leader distrusting the marketing-sourced-pipeline number. Strkr runs the two funnels as linked pipelines with the handoff enforced by SLA, which keeps both teams honest without forcing a single-funnel fiction.

How often should I redesign the sales funnel?

The funnel structure (stage count, stage names, exit criteria) should hold stable for 12 to 24 months. Redesign when a specific signal fires: a sustained drop in a specific stage conversion rate, a new motion added (expansion, outbound, partner-sourced) that needs its own pipeline, a major product shift that changes the demo-to-validation dynamics, or a sales-ops leader change that brings a new philosophy. Minor tuning (exit criteria wording, time-in-stage thresholds) runs quarterly. The redesign cost is high: reps have to relearn, reports have to rebuild, dashboards have to redraw. Stability has value.

Also built for

Related audiences.

Sales Funnels AI CRM Software Sales Intelligence B2B Sales Intelligence Platform For Account Executives

Try it free. Bring your team next week.

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.

Start free trial See pricing