Business process automation: where to start

“We want to implement AI” is not yet a business problem. A better starting point is concrete: sales staff copy forms into a CRM, proposals wait three days for approval, only one person knows a case status or the team searches dozens of documents for an answer.

A process suits a first pilot when it is frequent, has an owner, can be followed end to end and produces a measurable change. It should not initially cover the entire company or a critical operation without an emergency procedure.

A workshop should not rely only on how the process is supposed to work. Observe a real form, email, spreadsheet, approval and exception. Workarounds and manual corrections usually determine the actual scope.

Record inputs, owner, decision, output and system at every step. Mark copying, waiting, missing status and repeated checks. Only then is it clear what should be simplified before automation.

When a decision is deterministic, a standard rule is cheaper and more predictable than a generative model. A webhook can send a form to a CRM, validation can check completeness and a schedule can create a reminder.

AI becomes useful for text, documents, classification and ambiguous data. In that case define sources, allowed actions, answer quality, permissions, logging and human approvals. NIST frames AI risk management across the system lifecycle rather than around model choice alone.

A pilot should support a small group, a limited case type and a clear measure. Recommendation mode is often useful: the system proposes an action while a person approves it.

Every failure needs a visible status, log and manual route. If an integration times out or the model cannot find a source, the case must not disappear. It should enter a queue with an explanation.

Compare process time, manual steps, corrections, ownerless cases and exceptions requiring people. It is not enough to say the team uses AI. A tool can be opened frequently without shortening the process.

Only after several cycles should the company add case types, integrations or permissions. Stopping or changing a pilot that creates no value is a valid result, not a failure.