Value stream mapping
Funnel flow efficiency calculator
Funnel flow efficiency calculator is licensed CC BY 4.0. Attribution: Katafacts (katafacts.com).
Customise with AISkill file ↓1 · What it is
What it is
Process cycle efficiency (PCE), also called flow efficiency, is the share of total time a deal is actually being worked versus sitting idle: process time divided by total lead time (process time plus wait time), across every stage. It's the single most useful number in a funnel value stream map (see the sales funnel value stream map), pulled out on its own for the case where a full documented map is more than you need right now. Most funnels come back under 10% — the finding almost every revenue team is missing is not which stage is slow, it's how little of the pipeline's total duration is spent on active work at all.
2 · When to use it
When to use it — and when not to
Use it when
- You want the headline flow-efficiency number fast — a sanity check before deciding whether a full funnel value stream map is worth the time.
- You already have per-stage process and wait time from your customer relationship management (CRM) system and just want it turned into a defensible percentage with the arithmetic shown.
- You're building a case for why pipeline velocity work matters and need one number a leadership team will immediately understand is too low.
Not when
- You need to know *which* stage to fix, not just the overall number — that's the sales funnel value stream map or the bottleneck analysis, both of which compute this same number as part of a fuller picture.
- You want waste findings, a Pareto ranking, or countermeasures — this calculator deliberately doesn't ask for the observation notes those are drawn from.
- You only have a single blended total-cycle-time figure with no per-stage breakdown — flow efficiency needs at least process time and wait time distinguished per stage, not just a start and end date.
3 · How to fill it in
How to fill it in
- Scope
- Just the one-line description at the top — what pipeline segment this is. There's no separate scope field here; keep it as tight as you would for a full funnel map (one deal source or segment, not the whole blended pipeline).
- Customer demand and takt
- Optional — add the deals needed per week or month if you also want each stage checked against the pace the business needs.
- Process steps
- List each stage in order with its process time and the wait time after it before the next stage starts. This is the only real intake this calculator asks for — paste rows straight from a CRM export if you have them.
- The map
- Drawn from your stages, so the share of time spent waiting is visible at a glance next to the number.
- Lead time · Flow efficiency · Constraint
- Flow efficiency, lead time, and the stage capping throughput are computed for you the moment you submit — this is the whole point of the calculator, not a step you fill in.
- Waste — the eight wastes
- Not part of this calculator's output — it only computes flow efficiency and the constraint. Use the sales funnel value stream map for the full eight-wastes breakdown.
- Where the wait concentrates
- Not part of this calculator's output. The full sales funnel value stream map ranks every stage by wait-time contribution; this tool only surfaces the single largest one.
- Future state
- Optional — once you have the number, sketch the faster funnel in the same editor and see the flow efficiency it would reach.
- Countermeasures
- Not part of this calculator's output — there's no observation-notes field feeding a countermeasure narrative here. Once you know the number's worth acting on, the sales funnel value stream map is where you'd work through what to do about it.
4 · What good looks like
What good looks like
The example below is the same six-stage outbound funnel as the full sales funnel value stream map — because the flow-efficiency number this calculator produces is exactly the same number that map computes as part of its fuller analysis, not a different calculation. What's different is the path to get here: this page only asked for stage names, process time, and wait time.
Same example, as a downloadable xlsx workbook.
Value stream map — current state
Mid-market outbound pipeline — current-state analysis
Jordan Ellis, Sales Manager · 2026-03-16
Team: Priya Anand, Revenue Operations, Sam Cole, Sales Enablement · Sponsor: Renee Okafor, Vice President of Sales
Scope
Scope runs from a lead being accepted as sales-qualified to closed-won or closed-lost, for outbound-sourced mid-market deals only. Excludes marketing nurture before a lead is sales-qualified and post-close onboarding — those are separate value streams with their own owners.
Customer demand and takt
No customer demand recorded, so takt isn't checked.
Process steps
| Step | Process time | Wait after | Operators | Uptime | Defect % | Units waiting after |
|---|---|---|---|---|---|---|
| Lead qualification | 2 h | 24 h | 1 | — | 40% | — |
| Discovery call | 3 h | 96 h | 1 | — | 35% | — |
| Solution demo | 4 h | 120 h | 1 | — | 25% | 22 |
| Proposal & pricing | 6 h | 168 h | 2 | — | 30% | — |
| Negotiation | 5 h | 72 h | 1 | — | 15% | — |
| Contract signed | 2 h | 0 h | 1 | — | — | — |
The map
Drag to move around · Ctrl or ⌘ + scroll, pinch, or + and − to zoom · 0 to fit
Lead time · Flow efficiency · Constraint
Lead time
502 h
Process time
22 h
Flow efficiency
4.38%
Takt
—
2 + 3 + 4 + 6 + 5 + 2 (process time) + 24 + 96 + 120 + 168 + 72 + 0 (wait time) = 502 hours
22 / 502 × 100 = 4.38%
Takt: add customer demand to check each step against the pace the customer needs.
Capacity constraint
Negotiation
5 hours process time (no downtime recorded); the least capacity in the stream — add customer demand to check it against takt.
Longest wait
Proposal & pricing
168 h · 33.47% of lead time
Where work waits
- Discovery call — Work waits 96 hours after this step — 19.12% of total lead time, above the 15% flag threshold.
- Solution demo — Work waits 120 hours after this step — 23.90% of total lead time, above the 15% flag threshold.
- Proposal & pricing — Work waits 168 hours after this step — 33.47% of total lead time, above the 15% flag threshold.
Where work piles up
- Solution demo — 22 of the 22 units counted waiting in queues (100.00%) sit after this step, above the 25% flag threshold.
Waste — the eight wastes
- Defects82.6 %
Rolled throughput yield across the 5 steps with a recorded defect rate is 17.40% — about 82.60% of units need rework or scrap somewhere in the stream, so first-pass output is lower than any single step suggests.
(1 - 40/100) × (1 - 35/100) × (1 - 25/100) × (1 - 30/100) × (1 - 15/100) × 100 = 17.40% yield — from Lead qualification (40%), Discovery call (35%), Solution demo (25%), Proposal & pricing (30%), Negotiation (15%); defects = 100 − 17.40 = 82.60%
- OverproductionQualitative
Not quantified from step timings. On the next walk, look for producing more than the next process pulls, or running ahead of takt — batches built early, reports nobody reads.
- Waiting480 hours
Work sits idle for 480 hours in total across this value stream, queued after 5 of 6 steps.
24 + 96 + 120 + 168 + 72 + 0 = 480 hours
- Non-utilized talentQualitative
Not quantified from step timings. Look for operators' process knowledge or improvement ideas going unused — people closest to the work with no route to change it.
- TransportationQualitative
Not quantified from step timings. Look for unnecessary movement of material or information between steps — handoffs, re-keying, files shuttled between systems.
- Inventory22 units
22 units of work in progress sit in queues after 1 of 6 steps — every one of them is finished effort not yet paid for.
Solution demo (22) = 22 units
- MotionQualitative
Not quantified from step timings. Look for unnecessary operator movement within a step — reaching, searching, walking to fetch what the work needs.
- Extra-processingQualitative
Not quantified from step timings. Look for doing more to the product or information than the customer actually values — extra approvals, duplicate checks, unused detail.
Where the wait concentrates
Ranked by wait time after each step
- Proposal & pricing168 h
- Solution demo120 h
- Discovery call96 h
- Negotiation72 h
- Lead qualification24 h
- Contract signed0 h
Future state
No future state designed yet.
Countermeasures
Pre-approve standard pricing tiers for deals under a set contract-value threshold so they skip the two-approver review entirely; keep the full review only for genuinely custom terms.
Linked finding: Proposal & pricing — largest wait contributor at 33.47% of lead time
Impact: high · Effort: medium · Owner: Priya Anand · Due: 2026-04-06
Cap the number of deals allowed to sit between Solution demo and Proposal at any time, pulling the next demo only when a proposal slot frees up, instead of running demos as fast as reps can book them.
Linked finding: Solution demo — 22 deals stalled in the queue, wait time 23.90% of lead time
Impact: medium · Effort: medium · Owner: Jordan Ellis · Due: 2026-04-13
Tighten the criteria marketing uses to hand over sales-qualified leads so fewer poorly-fit leads enter the pipeline only to drop out at qualification — add one firmographic checkpoint before a lead is marked sales-qualified.
Linked finding: Defects — 17.40% rolled throughput yield across 5 stages; Lead qualification is the single largest contributor at 40% drop-off
Impact: medium · Effort: low · Owner: Sam Cole · Due: 2026-04-06
5 · Common mistakes
Common mistakes
Treating a low flow-efficiency number as the finding itself, with no next step.
A single percentage tells you the pipeline is mostly waiting, not why or where. Once the number is low enough to act on, move to the full funnel value stream map to find the specific stage worth fixing.
Mixing deal segments with genuinely different natural cycles to get one 'overall' number.
A blended self-serve-plus-enterprise flow efficiency describes neither segment — same scope discipline as every other value-stream kata in this catalogue.
Estimating stage timing from memory instead of pulling actual CRM stage-entry and stage-exit timestamps.
Flow efficiency is only as trustworthy as the timing data behind it — a guessed number that looks precise is worse than an honest 'we don't have this data yet.'
6 · What it connects to
What it connects to
upstream
downstream
Once the flow-efficiency number is low enough to warrant real attention, this is where you find which specific stage to act on and what to do about it.
If the question is specifically 'which stage is capping throughput' rather than 'what's my overall efficiency,' this is the more direct next step.
Part of these playbooks
- Sales Funnel Management Katas — 13 katas in the order they are used
7 · Where AI helps
Where AI helps
Judgement — stays yours
- Deciding whether the number is low enough to justify a full funnel value stream map
- Drawing the pipeline segment's scope boundary
Analysis — AI helps
- Nothing here — flow efficiency is a deterministic calculation, not an analysis judgement call
Drudgery — automated
- Computing lead time and flow efficiency, with the arithmetic shown
- Identifying the single largest wait contributor
- Exporting to xlsx in the house format
9 · Rate this kata