All posts

How to Bring AI into a Small Business: A Practical 6-Step Plan

Where should a small or mid-sized business start with AI? A proven plan: choosing a process, running a pilot, keeping data safe, the EU AI Act and measuring results.

Paweł Walda, , 4 min read

Most companies I talk to have the same problem: everyone feels they “should be doing something with AI”, but nobody knows where to start. Some buy licences for several tools at once; others wait for the technology to “mature”. Both approaches end the same way: lots of meetings, few results.

Here is the plan I use with small and mid-sized businesses. You don’t need an IT department or a big budget to start.

1. Start with a problem, not a tool

The most common mistake is asking “where can we use ChatGPT?”. A better question is: “which repetitive work takes up most of our time?”

Good candidates for a first project have a few things in common:

  • the task happens daily or weekly,
  • it’s text-based: emails, documents, notes, forms,
  • a person can easily check the result,
  • a mistake doesn’t cost a fortune.

Examples: answering recurring customer questions, extracting data from invoices and orders, summarising meetings, drafting first versions of proposals, searching internal procedures.

2. Work out what it costs today

Before building anything, write down three numbers:

  1. how many times a month the task is done,
  2. how long it takes on average,
  3. the hourly cost of the person doing it.

If the team spends 40 hours a month on something, even a 50% saving gives you back a week of work every month. You’ll need these numbers later to judge honestly whether the project was worth it.

3. Sort out your data before it reaches a model

Data security is the most common concern, and rightly so. A few rules to agree on from day one:

  • No personal data or trade secrets in free, personal accounts. Business plans from most vendors (e.g. ChatGPT Business/Enterprise, Claude Team/Enterprise, Microsoft 365 Copilot) don’t train models on your data and offer a data processing agreement.
  • Check where your data is processed. An EU region is enough for many companies; for highly sensitive data, consider a model running on your own server.
  • Write a simple AI usage policy. One page: which tools we use, what data must never be entered, and who is responsible for checking the output.

4. Run a small pilot (2–6 weeks)

Pick one process and one or two people who do it every day. The pilot should have:

  • a clear goal, e.g. “cut proposal preparation time from 2 hours to 45 minutes”,
  • a simple way to measure it: a spreadsheet logging time spent and number of corrections,
  • a human in the loop: AI drafts, a person reviews and approves.

At this stage, off-the-shelf tools and well-crafted prompts are often enough. If the process needs to connect to your systems, automation platforms such as n8n, Make or Power Automate, or a simple API integration, will help.

5. Train the team, don’t just deploy a tool

A tool nobody uses saves nothing. A short, hands-on training based on your team’s actual daily work beats a generic course every time.

There’s a second reason too: the EU AI Act. Since 2 February 2025, organisations using AI systems must take measures to ensure the people using them have a sufficient level of AI literacy. For a small business this usually means a short training and written guidelines, not a big compliance project. The EU is working on simplifying parts of the AI Act, so keep an eye on changes. (This isn’t legal advice. If in doubt, talk to a lawyer.)

6. Measure, then scale, fix or drop it

After the pilot, go back to the numbers from step 2 and answer three questions honestly:

  • Are we saving time or money once reviewing the output is included?
  • Is the quality at least as good as before?
  • Does the team want to keep using it?

Three yeses: roll it out to more people or processes. Otherwise, improve it or drop it and move on to the next candidate. A pilot abandoned after four weeks isn’t a failure; it’s a cheap lesson.

Common pitfalls

  • Starting too big. “A chatbot that replaces customer service” is a bad first project. “Draft replies to the 10 most common questions” is a good one.
  • No owner. Every project needs one person on the business side who is accountable for it.
  • Blind trust. Language models can state false information confidently. Design the process so key facts get verified.
  • Buying many tools at once. Better to adopt one tool well than pay for five nobody uses.

Summary

Bringing AI into a small business doesn’t have to be a big project. Pick one specific, repetitive process, work out its cost, protect your data, run a short pilot with a human in the loop, train the team and measure the results. Only then scale up.

If you’d like help, I can guide you through the whole process: from a workshop where we find the best places for AI in your company to a working solution. See how AI enablement works.

Want to put this into practice?

Book a free 30-minute call and I'll tell you where to start in your company.

Book a free call