Online tool

Find my bottleneck

Name the steps of your service and how many cases each can handle per week. The tool shows the step that limits everything, the queue growing in front of it and the waiting time.

AI Mapping · Find my bottleneck

The steps of your service, in order

1Step name 1Capacity per week
2Step name 2Capacity per week
3Step name 3Capacity per week
4Step name 4Capacity per week
5Step name 5Capacity per week

Capacity : per week

Incoming requests

How many new requests come in each week, on average.

Requests already waiting

In front of your bottleneck, today. Leave 0 if you don’t know.

Nothing is sent. Your data stays in this browser.

What your numbers show

Your bottleneck

Writing

Actual service throughput

requests per week

The queue grows by

requests per week

Request12
Qualification9
Writing4
Review6
Sending8

Incoming requests : 5 / per week

Your service cannot handle more than 4 requests per week, however fast the other steps go.

5 requests come in each week and the bottleneck handles 4: the queue grows by 1 every week. Lead times will keep growing until something changes at the bottleneck.

Little’s law: 16 requests waiting ÷ 4 per week = about 4 weeks of waiting.

What if you sped up a step?

Change a step’s capacity and watch throughput. It only moves if you touch the bottleneck.

+50 %

Actual service throughput : 4 → 5 requests per week

This is where an hour saved counts for the whole service.

What next?

Check the bottleneck figure with the flow log for one week. Capacities estimated from memory are often wrong.
Ask whether the bottleneck is a rule: a complete form required, a signature, a habit.
Run every AI idea through the five criteria before buying anything.
If your steps are waiting for work, the bottleneck is demand. Look at marketing too.

A simple model: it assumes a stable flow and a single queue. It opens the conversation; it does not replace measurement.

A family of free tools