Which processes can you automate with AI?

Choose work that follows the same steps. For a job sheet, someone reads it, looks up the assignment, copies the hours and books them. Four steps repeated every day.

Each manual step takes time and occasionally something is missed. We build software that follows the same steps. Automatic handling stops when an exception occurs.

Every process begins with a trigger. In practice it is usually one of these: a mail with an attachment in a shared mailbox, a new file in a folder or on a drive, a record that changes in a system, a form filled in on your site, a message in a team chat, or simply the clock, every working day at seven.

We agree what starts the task and what should happen if something goes wrong. For software reading a mailbox, that includes deciding what to do with an unexpected email.

A job sheet arrives as a PDF in a shared mailbox. The system reads it, looks up the matching assignment in the planning and queues the hours in the package your invoicing runs from. If something does not add up, the sheet goes to a separate folder with the reason attached. The exception and the final check stay with a person.

Or a planning board that every morning at six pulls the day's assignments from two systems that do not talk to each other, and puts them side by side with whatever is still missing. The planner sees on one screen what needs arranging and moves it themselves. The board moves nothing on its own.

Work that runs differently every time, and work where the contact itself is the value. Also work that comes back once a quarter, because the maintenance on it costs more than it returns.

We start with work that recurs often enough to make a difference. Once the first version works, another task is faster to build because the integrations are already there.