The branch manager wants faster onboarding. Finance wants complete job records before invoicing. The operating president wants fewer exceptions in an executive inbox. Each could support useful software, but they should not automatically become simultaneous projects.
Your first investment needs a decision rule. For a multi-site service business, I would start with the recurring handoff that has a measurable consequence, an accountable owner and a realistic path into the daily work of the team. The framework below is an operating recommendation, not a claim about results already achieved for a particular client.
Start With The Consequence
Describe the event that makes the workflow worth changing. A completed service visit waits for a document; a new branch cannot obtain the right access; a disputed classification passes between departments. Name what happens next when that event remains unresolved, including which person spends time recovering the situation.
The distinction matters because adoption is a broad measure. In the collection period ending May 3, 2026, reported AI use among firms with 100 to 249 employees reached 32% (Census Bureau, 2026). That does not establish whether a particular workflow inside those firms improved, or whether another business should copy the same investment.
Write the candidate down in one sentence: when this event occurs, this person needs this evidence to make this decision. Then record what the consequence of waiting would be. A sentence that ends with “use AI” still needs more work done on it.
A useful first workflow has an owner who feels the delay and can change what happens next.
Compare Candidates Without False Precision
Use the same questions for every candidate on the list. The table that follows is a decision aid, not a validated scoring model; a strong answer on volume cannot compensate for missing permission to access the system. Write the supporting evidence beside each answer so that the loudest stakeholder does not silently end up as the winner.
| Question | Evidence to request | Reason to wait |
|---|---|---|
| What repeats? | Sampled records and exceptions | Occasional or poorly defined |
| What does delay change? | Rework, waits, disputes, lost capacity | The effect is only an impression |
| Who can change it? | A process owner and access owner | No owner across departments |
| Will people use it? | A place in the daily routine | A second queue nobody maintains |
| Can failure be contained? | Review, rollback and a manual path | Errors are hard to detect or reverse |
Keep the comparison legible enough to discuss during a working meeting. If two workflows remain close, prefer the one in which a small release can teach you something about real operations. A narrower system with an observable result creates better evidence for the next decision than an ambitious platform whose adoption is unclear.
Separate Capacity From Cash
Suppose, purely as a worked example, a process handles 800 records in a month and a measured change removes six minutes of avoidable handling from each. That represents 80 hours of potential capacity before accounting for review, exceptions and maintenance. It does not mean payroll falls by 80 hours or that revenue increases by an equivalent amount.
Ask what the team would actually do with that freed capacity. It might absorb additional volume, reduce overtime, improve response times, or simply create breathing room that management values. Each is a different business case and needs a different measure; do not add them all together as if they were independent cash savings.
Research on workflow redesign and self-reported earnings impact supports looking beyond isolated tool use (McKinsey, 2025). It reports an association, not a causal promise for your operation. Your baseline and observed adoption must carry the investment decision.
Inspect The Work Before Automating
Review both routine records and cases that required a supervisor. Watch where people leave the official system to find context, ask permission or reconcile conflicting information. The detour often reveals the requirement that a clean demonstration leaves out.
A model might help interpret a service note or propose a category. A rule can check whether required fields exist, and a person resolves a disputed sign-off. Write each responsibility separately, including what the reviewer sees and what happens next if they disagree with it.
Put uncertainty and responsibility into the workflow design while changes are still cheap.
Make Adoption Observable
Agree what the process owner will review after release. Count eligible records, actual use, exceptions needing intervention, and time from the trigger to the agreed next state. A system can look reliable while staff quietly keep the old spreadsheet beside it.
Missing Ownership Stops The Work
If finance owns the consequence but cannot change the upstream process, software alone cannot settle the disagreement between them. Resolve who sets the completion rule, who approves an exception and who is able to commit the access that is necessary. A funded sponsor must be able to bring those people into the same decision.
The same limit applies if a planned replacement will remove the workflow's foundation. Confirm the migration path before building an integration that may immediately need replacement. Waiting for that answer is a dependency decision, not a lack of ambition.
First Steps
- Collect sample records for the top candidates, including unresolved and rejected ones.
- Walk a single record through the whole handoff with its process owner and with the receiving team, recording the waits and the decisions along the way.
- Choose one measurable release, document its manual fallback in writing, and name the one person who will review whether it deserves to be expanded.
One Workflow, An Explicit Owner
Commission a bounded release around a handoff you can observe. Agree the baseline, access dependencies, acceptance conditions and operating duties before work begins. Keep the first decision small enough that its result can change the next.
This approach creates a working relationship between engineering and operations: each release answers a question about the business and leaves behind a system someone can maintain. When the roadmap needs ongoing engineering alongside the first release, the AI engineering partnership provides a scoped way to build, run and improve that system.
References
- U.S. Census Bureau. Large Firms With at Least 20 Employees Biggest AI Users. 2026.
- Singla, A., et al. The State of AI: How Organizations Are Rewiring to Capture Value. McKinsey, 2025.
