Free Bottleneck Finder
Business bottleneck finder
Find your biggest operating constraint and a first action.
From inquiry to cash
Find the delay worth testing.
Bottleneck analysis identifies a step that limits flow. Start with the longest observed wait, then check capacity separately before calling it a throughput constraint.
First action: confirm the cause with this step’s owner, then run one measured 14-day wait-reduction test.
19 days from inquiry to cash; 16.5 waiting · 2.5 active · 86.84% of the journey spent waiting.
Longest wait: Approval. This is a delay candidate, not proof of limited capacity.
Get your constraint-removal plan.
Email unlocks the PDF and quote-approval automation recipe here. Your private plan is generated in this browser, not emailed or uploaded. Download it before leaving this tab.
- Your leading constraint
- Constraint-removal plan
- Owner and review checkpoints
Preview the result or example included in this kit
Lead-to-cash: 19 calendar days; active 2.5, waiting 16.5 (86.84%). Longest wait: Approval. What-if: cut Approval wait by 50%; save 5.5 days, giving 13.5 days end to end (28.95% shorter). Delay is not capacity. No throughput increase is assumed.
| Stage number | Waiting days |
|---|---|
| 1 | 0.25 days |
| 2 | 0.5 days |
| 3 | 11 days |
| 4 | 1 days |
| 5 | 1 days |
| 6 | 0.25 days |
| 7 | 2.5 days |
| Stage | Active days | Wait days | Share of total wait |
|---|---|---|---|
| 1. Inquiry | 0.25 | 0.25 | 1.52% |
| 2. Quote | 0.5 | 0.5 | 3.03% |
| 3. Approval (longest wait) | 0.25 | 11 | 66.67% |
| 4. Scheduling | 0.25 | 1 | 6.06% |
| 5. Work | 1 | 1 | 6.06% |
| 6. Invoice | 0.25 | 0.25 | 1.52% |
| 7. Payment | 0 | 2.5 | 15.15% |
Delay is not capacity.
Capacity is unknown. Add measured orders/week under each stage only if you want to compare throughput. Waiting for customer approval can take days without using days of staff capacity.
The capacity screen assumes dedicated resources and comparable orders, with no shared staffing, yield loss, or rework. Even a complete set is a planning limit, not guaranteed output.
Your first 14-day test
Approval: 11 days waiting
Fix: Confirm the quote arrived, ask what blocks the decision, and agree on the next contact. Stop after a reply, decline, or opt-out.
Proposed owner: Sales lead. Confirm before starting.
Tool: Quote Follow-Up Builder plus human-approved draft reminders.
14-day test and guardrails
Days 1–3: Sales lead records entry, work-start, work-end, and exit for comparable orders at Approval. Days 4–10: test the proposed fix on a small owner-approved batch. Days 11–14: compare median wait and end-to-end time with the baseline, plus completion volume, rework, complaints, and staff load. Keep only an improvement that does not shift harm downstream.
Payment: 2.5 days waiting
Fix: Confirm invoice receipt, terms, and any dispute. Resolve discrepancies before sending an approved reminder.
Proposed owner: Accounts receivable lead. Confirm before starting.
Tool: Receivables aging view and human-reviewed payment reminders.
14-day test and guardrails
Days 1–3: Accounts receivable lead records entry, work-start, work-end, and exit for comparable orders at Payment. Days 4–10: test the proposed fix on a small owner-approved batch. Days 11–14: compare median wait and end-to-end time with the baseline, plus completion volume, rework, complaints, and staff load. Keep only an improvement that does not shift harm downstream.
Scheduling: 1 days waiting
Fix: Offer only verified slots after checking staff, materials, access, and dependencies. Give exceptions a named owner.
Proposed owner: Scheduler. Confirm before starting.
Tool: Shared scheduling board with a ready-to-start checklist.
14-day test and guardrails
Days 1–3: Scheduler records entry, work-start, work-end, and exit for comparable orders at Scheduling. Days 4–10: test the proposed fix on a small owner-approved batch. Days 11–14: compare median wait and end-to-end time with the baseline, plus completion volume, rework, complaints, and staff load. Keep only an improvement that does not shift harm downstream.
Start with one priority, not three simultaneous changes. These suggestions are hypotheses to test, not promises or installed automations.
How bottleneck analysis works
Map one order through sequential stages. Lead time = all active days + all waiting days. The what-if subtracts only the selected wait × reduction percentage. A wait share is descriptive, not a risk score. Overlapping stages, parallel teams, and person-hours need a different model.
Definitions follow the distinction between processing time and end-to-end lead time in Lean Enterprise Institute’s value-stream mapping guide. Our examples and fixes are illustrative. Method reviewed 2026-08-30.
When quote approval is the delay, the Quote Follow-Up Builder can help draft the next contact. Document any tested change before expanding it to the whole team.
How this tool works
Trace one order, find the longest wait, and test the change before you automate it.
- Pick an example and edit your stages.
- Compare waits and test a what-if.
- Get the PDF and approval recipe.
A useful first experiment
Fix the handoff before adding more work.
A business bottleneck can hide between tasks: a quote awaiting approval, a job waiting for materials, or an invoice nobody has sent. Measure one representative order end to end before deciding which tool to buy.
Rank waits, choose one fix, name the owner, and test it for 14 days. Compare lead time and actual completed orders, then check rework, complaints, and the next queue. A smaller queue in one place is not a win if it creates a larger problem elsewhere.
Questions owners ask
Bottleneck analysis FAQ
What is bottleneck analysis?
It is the process of finding the step that limits flow. This diagnostic first ranks elapsed waiting time in your lead-to-cash process. To assess a throughput constraint, enter separate capacity measurements and validate them against real order volumes.
How do I find a bottleneck in a small business?
Follow a representative order through inquiry, quote, approval, scheduling, work, invoice, and payment. Record active and waiting time separately on one calendar clock. Start with the largest wait, observe its cause, then test one change with a named owner.
Does cutting a wait in half double throughput?
No. Halving an 11-day wait saves 5.5 elapsed days, assuming all other stages stay unchanged. It does not prove that staff can complete more orders. Capacity, demand, shared resources, quality, and rework must be measured separately.
What are some business bottleneck examples?
A service company may wait for quote approval, a project firm may queue for a kickoff slot, and a consultancy may wait for payment. The built-in examples illustrate those cases; they are not industry benchmarks.
What does the PDF include, and is it emailed?
The PDF includes your stage details, what-if, prioritized fixes, proposed owners, 14-day tests, and a draft-only quote approval recipe. Email unlocks a download in this tab. Your personalized plan is not sent to Nerd Out or emailed, and reloading clears your inputs.