Finding the constraint: where should you deploy AI first?
Every business has one step that limits how much work it can finish. Not the step that annoys people most, and not the one with the flashiest AI demo. The step everything else waits on. Speed up anything upstream of it and work just piles up there. Speed up anything downstream and that step sits idle, waiting for input. Fix the constraint and the whole business moves faster.
In a service company it is often the callback. In a clinic it might be intake paperwork. In a contractor's office it is frequently the estimate: leads come in fine, jobs get done fine, but quotes sit for days because one person writes them all. That is where your first AI project belongs, because that is the step setting your clockspeed.
How to spot it
- Look for the pile. Where does work queue up? An inbox, a voicemail box, a stack of unsigned forms.
- Look for the name. Which step stops when one specific person is out?
- Look for the gap. Where is the distance between work time and elapsed time widest? Ten minutes of effort that takes three days is a strong signal.
Score the candidates
Once you have a short list, score each workflow on six plain factors. No spreadsheet math needed. High, medium or low is enough.
- Volume: how often it happens. Daily beats quarterly.
- Elapsed-time gap: how much waiting surrounds the actual work.
- Handoffs: how many people or systems touch it before it is done.
- Predictability: how often it follows the same rules. This is what makes it suitable for AI.
- Risk: what a mistake would cost, in money, compliance or trust.
- Impact: how directly it affects revenue or the customer's experience.
| Workflow | Volume | Time gap | Handoffs | Predictability | Risk | Impact |
|---|---|---|---|---|---|---|
| Inbound calls and callbacks | High | High | Med | High | Low | High |
| Appointment scheduling | High | Med | Med | High | Low | Med |
| Quote preparation | Med | High | High | Med | Med | High |
| Past-due invoice follow-up | Med | High | Low | High | Low | Med |
| Contract negotiation | Low | Med | Med | Low | High | High |
Start where impact meets predictability and risk is low
In this example, inbound calls win: high impact, highly predictable, low risk. Invoice follow-up is a solid second. Quote preparation is valuable but needs its rules written down first. Contract negotiation scores high on impact and still belongs with a person, because it runs on judgment and relationships. A high-impact score alone does not make something a good first project.
Two cautions. First, a workflow that scores well but is not your constraint will save effort without making the business faster. Check it against the pile, the name and the gap. Second, once you fix the constraint, it moves. Something else becomes the step everything waits on. That is expected. You measure again and pick the next one, which is the loop at the center of our Clockspeed Method.
If you would rather have someone run this exercise with real numbers from your own operation, that is what the AI Audit does: map the workflows, measure the gaps, and rank where to start.