Which business process should you automate first?

Map one real example

Choose a recent instance of the task. Write down what triggered it, where the information arrived, who touched it, which tools were used and what finished it. Include waiting and corrections. An inquiry moving from an inbox to a spreadsheet and then to a person is specific enough to discuss; automate operations is not.

Choose work with visible friction

Look for repeated copying, predictable routing or repeated requests for missing information. Record task volume and handling time rather than guessing. Avoid beginning with a process whose rules nobody can explain. Clarifying responsibility or removing an unnecessary approval may solve part of the problem before software is needed.

Separate rules from interpretation

If a decision can be written as a stable condition, ordinary automation may be enough. AI may be useful for interpreting unstructured messages or proposing a category. Keep consequential actions distinct: producing a draft is different from sending it, and extracting invoice fields is different from authorizing payment.

An illustrative inquiry workflow

A website inquiry arrives with contact details and a project description. The workflow checks required fields, records the request and routes it to an owner. An AI step could propose a short brief; a person reviews it before replying. This example is a design pattern, not a report of a deployed client system.

Design the failure path first

Decide what happens when information is missing, a connected tool is unavailable or the same event arrives twice. Specify an exception queue, a responsible person and a way to retry without creating duplicate work. The pilot should expose failures rather than make a successful-looking screen the only evidence.

Use a simple pilot scorecard

Before the pilot, record volume, handling time, errors and waiting time over a representative period. During the pilot, track those same measures plus review effort and software costs. For example, 100 tasks at six minutes each represents ten hours of baseline handling time—not ten hours of guaranteed savings. Subtract remaining review and recovery work before estimating benefit.

Expand only after the result is useful

Agree in advance what would justify continuing: reliable completion, manageable exceptions and an improvement against the baseline. If the pilot adds review work or creates silent failures, revise it before connecting more processes. A bounded workflow is easier to evaluate than a broad agent with unclear permissions.

Questions before you start

Explore our work and services

View Recall and Focus Battery development work →

Try a sample automation workflow →

Start with your business problem.

Share the task, the people involved and the tools you already use. We can discuss the right scope for a first version.