Map the work as it happens
Follow a real request from arrival to completion. Record each application, person, handoff and decision. Include the informal spreadsheet and the message someone sends when information is missing. These details usually explain the actual workload.
Separate the predictable steps from the judgment calls. A fixed calculation or a known status transition often belongs in ordinary code. AI is most useful where a step must interpret varied language or unstructured information.
Choose a bounded opportunity
Look for a repeated process with accessible inputs, a clear owner and a result you can check. A lead-routing workflow may be easier to evaluate than an assistant that is expected to handle every operational question.
Consider the cost of failure as well as the time spent. A low-volume task can be a poor first automation if a wrong action is difficult to reverse. Prefer a workflow where uncertain cases can safely wait for review.
Define the source of truth
When two systems contain a different email address or status, the automation needs a rule for deciding which record to trust. Document who owns each field and when updates may flow in either direction.
Use stable identifiers instead of matching only by display name. Keep an event or request ID so repeated notifications can be recognized. An integration should not produce two appointments because a webhook was retried.
Design exceptions before the happy path
List what happens when a required field is absent, an API is unavailable or a model returns an unsupported answer. Each exception needs a visible status, a next step and an accountable owner.
Retries should be bounded and appropriate to the operation. A read can often be retried safely. A message or payment needs a provider-supported duplicate-prevention strategy and reconciliation before another attempt.
Measure the pilot honestly
Record the starting handling time, correction rate and completion volume. During the pilot, include the time spent reviewing and fixing automated output. Comparing only model response time with the full manual workflow exaggerates the benefit.
Review results with the people doing the work. An automation that saves minutes but creates confusion or duplicate records is not ready to expand. Keep the pilot narrow until exceptions are understandable and recoverable.
Turn the thinking into a project
Use the project planner to describe your objective, integrations and constraints. The result is a discussion brief, with no invented price or delivery commitment.
Plan your project