
What should you automate first in your business?
A simple way to choose a first project your team can use, measure, and manage.
Choose a repeatable problem
The best starting point is often a small task that happens frequently and already has a clear definition of done. Think of routing an inquiry, preparing a meeting summary for review, or reminding a team member that a quote needs attention.
List the repetitive work your team does in a typical week. For each task, record how often it happens, roughly how long it takes, and what goes wrong when it is delayed. Estimates are useful at this stage as long as you label them as estimates.
Check the rules and the inputs
Before automating, ask whether another person could complete the task from your instructions. If the answer depends on unstated judgment or information scattered across inboxes, document those dependencies first.
What starts the task?
Which information is required?
What should the result look like?
Who checks the result?
What happens when the information is missing?
Ordinary automation may be enough for clear routing rules or reminders. AI can help when the work involves interpretation or drafting, but it still needs boundaries and a review process.
Pick a small, reversible pilot
Choose a project where mistakes are easy to catch and correct. Drafting an internal summary for review is easier to control than allowing a new system to send customer commitments without approval.
Start with a limited set of approved information. Give the system only the access it needs for that task. Name the person who will review the output and handle exceptions. Define how the team can pause the process if it behaves unexpectedly.
Measure the whole job
Record the time the task takes before the pilot, including checking and correcting the result. Then measure that same end-to-end time during the pilot. An output that appears quickly but takes a long time to fix may not be an improvement.
Also track accuracy, missed cases, and whether the team actually uses the process. Expand when the workflow is reliable enough for its purpose and the people responsible understand how to manage it.
Start with one useful process, one owner, and one clear measure.
Your next move
Choose a frequent task with clear inputs, a reviewable result, and a named owner. Run a limited pilot before connecting it to more of your business.