How to start with AI in your company — the first 90 days

Nick van der Falk — AI expert for mid-sized companies
· AI expert for mid-sized companies
8 min read · Updated August 2026
Managing director planning next quarter with sticky notes on a wall
Managing director planning next quarter with sticky notes on a wall
On this page
  1. 01Days 1–21: find the hours
  2. 02Days 22–42: choose one process and define success
  3. 03Days 43–90: build it and run it for real
  4. 04The four mistakes that kill first projects
  5. 05What you need internally

Most companies get stuck at the same point: everyone agrees AI matters, nobody knows what to actually do on Monday morning.

Here is the sequence that works, without a strategy programme and without a six-figure commitment up front.

01

Days 1–21: find the hours

Before any technology decision, you need an honest picture of where time is spent. Sit with the people doing the work and record each recurring task: how often, how long, which systems, which hand-offs, what goes wrong.

The output is not a slide deck. It is a list of workflows with hours attached — which immediately shows the two or three that are worth attacking.

If you skip this step you will automate whatever is easiest to demo, not whatever is expensive.

More on this: What is a process audit — and why does it come before any software?

02

Days 22–42: choose one process and define success

Pick the process with high frequency, clear rules and real pain. Then write down the target in numbers: quote turnaround from two days to two hours, invoice processing time down 70%, month-end close from five days to one.

Without that number, the project ends in opinions. With it, the decision about a second stage takes five minutes.

More on this: Which tasks can AI actually take over in a company?

03

Days 43–90: build it and run it for real

Build the smallest system that runs the whole process end to end, connect it to the systems it needs, and put it into production with a human approving every output for the first weeks.

As the approvals become boring, reduce them to exceptions only. What you have then is not a pilot — it is a working part of the company that already pays back.

04

The four mistakes that kill first projects

  • Starting with technology instead of hours: buying a platform before knowing the workload.
  • Pilots with no production data. They always succeed and prove nothing.
  • Automating a process the team disagrees about. Fix the disagreement first.
  • No owner. A project without one named decision-maker on the client side stalls by week six.
05

What you need internally

Not an IT department. You need one person who can decide, a few hours per week from the people who know the process, and a willingness to write down how the business actually works — including the parts that are messy.

Everything else — architecture, build, integration, hosting, operation — is the provider's job, and any provider that needs more from you than this is offloading their work onto you.

In short

  1. Weeks 1–3: understand where the hours go. No tools, no vendors.
  2. Weeks 4–6: pick one process and define what success means numerically.
  3. Weeks 7–12: build it, run it in production with a human reviewing.
  4. Only then decide about the second process.
01What you get

How could AI employees be used in your firm or your business?

Tell us where you stand today. We outline one realistic first step, what it delivers in the first 90 days and what it costs.

After 30 minutes you have

  • A clear yes or no

    Whether your task is suited to an AI employee at all.

  • A real number

    What it roughly costs — and what you realistically save.

  • The first step

    Concrete and doable. Even if it happens without us.

02Who you will speak to
Nick van der Falk — AI expert for mid-sized companies

AI expert for mid-sized companies

„I can help you move the repetitive work in your company over to AI employees.”
03Your next step

Tell us the task that eats the most time

You do not need to know the technology behind it. Just write, in your own words, what costs you the most time.

What happens next

  1. 1

    We review your task

    We check whether an AI employee is worth it for this at all.

  2. 2

    We write back to you

    Usually within one business day — short and without obligation.

  3. 3

    30 minutes of clarity

    What works, what does not, and what your first step would be.

We reply personally, usually within one business day. No sales pressure, no newsletter. Your data goes to no one else.

04Why now

What happens if you do not switch to AI

Your competitors are switching already.

The majority of companies plan to introduce AI in 2026.

That means up to 30% more margin.

Because AI employees take over the recurring tasks.

Costs drop significantly.

AI works around the clock, needs no holidays and no payroll overhead.

More money is left for marketing.

Saved costs flow into advertising — and bring in more customers.

Customers move to the competition.

More ad budget pulls customers away — and leaves less market for you.

Whoever does not adapt is pushed out of the market.

Over the next two to three years AI becomes the standard for mid-sized companies — not an option.

This is not scaremongering — it is already happening in the first industries. And most companies do not fail because they lack the will, but because they do not know how to walk this path. That is exactly what we show you — and implement for you if you want. We create clarity and we deliver.

05Act now

Do not put your decision off until tomorrow

One conversation, 30 minutes, free. Afterwards you know which task in your company suits an AI employee — and what the first step is.

Nick van der Falk
Nick van der FalkAI expert for mid-sized companies
Request your free 30-minute call

No obligation. No lock-in contracts, no sales pressure. Prefer to write? Go to the form

Nick van der Falk — AI expert for mid-sized companies

Frequently asked

Should we hire an AI specialist first?

Rarely. In a mid-sized company the first system is best delivered by a team that has done it before; you hire internally later, once there is a system worth maintaining.

What if we pick the wrong first process?

Staged delivery limits the damage to one stage. In practice a proper process audit removes most of that risk, because the hours are on paper before anything is chosen.

How do we get the team on board?

Involve the people doing the work in the mapping, and be honest about intent: this removes admin, not people. Teams that helped design the system defend it; teams it was done to will quietly work around it.

Read next