← All insights
AI and automation

Where to start with AI and automation: choosing your first process

A practical way to pick the first process to automate, so your first AI project delivers a visible result instead of becoming an experiment that never ships.

Most companies don’t fail at AI because the technology doesn’t work. They fail because the first project is too vague (“let’s use AI”), too big (“automate customer service”), or too far from a real business result. The fix is to pick the right first process.

What a good first process looks like

The best first candidates share four traits:

  1. High volume. It happens dozens or hundreds of times a week, so small savings add up quickly.
  2. Repetitive and rule-based. The same steps, the same questions, the same data, most of the time.
  3. Clear inputs and outputs. An email, form, document or message comes in; a reply, record, task or report goes out.
  4. Low risk if something goes wrong. A mistake is caught and corrected, not costly or irreversible.

Typical examples:

  • Answering the same customer questions on WhatsApp or your website: opening hours, prices, locations, how to book.
  • Copying details from invoices, purchase orders or forms into your accounting system or ERP.
  • Qualifying incoming leads and creating them in your CRM with the right owner.
  • Sending reminders, follow-ups and status updates that someone currently writes by hand.
  • Producing a weekly report by pulling numbers from three different systems.

Questions to ask before you start

  • Who does this today, and how long does it take them? This is your baseline.
  • Where does the information come from, and where must it end up? That defines the integrations.
  • Which cases are exceptions? Decide which ones the system handles and which go to a person.
  • How will we know it worked? Hours saved, response time, error rate or volume handled.

Keep people in control

The safest automations don’t remove people; they move them to the decisions that matter. Let the system do the routine part and hand over anything unusual, with the full context, to the right person. Approval steps for sensitive actions such as payments, refunds or contract changes keep the risk low while the team builds trust in the system.

Start small, then expand

A focused first automation can usually go live in days or a few weeks. Once it runs reliably and the results are measured, the next process is easier: the integrations, data access and team habits are already in place. That is how one workflow grows into a company-wide program, with each step justified by the previous one.

If you’re not sure which process to start with, talk to us. A short discovery session is usually enough to find the opportunity with the clearest return.

← All insights

Tell us what you want to build

Share your idea or the process you want to improve. We reply within one working day, and we're happy to sign an NDA first.