How to automate repetitive tasks with AI when you run an SMB with fewer than 20 people

As an SMB owner, you lose hours every week on tasks no one accounts for. Follow-ups, data entry, searching for information. AI can handle them, without an IT department or tech budget. As long as it knows your context. Anakoro is built for exactly that.

Arnaud Groussac
June 1, 2026
You're following up with the same prospect for the third time this month. You're rephrasing the same brief to your AI because it forgot everything since Tuesday. You're copying and pasting data from one tool to another, wondering why no one thought to connect them. These aren't technical problems. They're hours. Yours. Your team's. They disappear into gestures no one notices, no one counts, but that weigh on every single week. The question isn't whether AI can help you. It can. The real question is how it fits into your daily routine without creating yet another project. Without hiring a technical profile. Without asking you to become someone else. This article is about that transition. The one that starts by identifying what you're still doing by hand, and ends with a day where those gestures are gone. Not because you eliminated them. Because something took care of them before you did.

1 – What you're still doing by hand without realizing it

When talking about repetitive tasks, a business owner first thinks of the obvious ones: invoicing, follow-ups, accounting entries. But the real losses are elsewhere. They're in the dozens of daily micro-gestures that have become invisible through force of habit.

1.1: The ghost gestures that structure your day

Monday morning. You open your inbox, spot three important messages, mentally note that you need to call back a client, forward a quote to your partner, and check whether last month's payment has arrived. None of these gestures are in your job description. None of them produce direct value. All of them take up your time. These ghost gestures are what fragment your attention. Not meetings. Not emergencies. The little things between emergencies. The ones you do while walking to the coffee machine, the ones you forget one time in three. Count them over a week. Note every time you copy information from one place to another. Every time you search for a name, an amount, a history. The total will surprise you. Not because it's enormous, but because no one on your team sees it.

1.2: Why these tasks resist traditional delegation

You've probably tried to delegate. To an assistant, an intern, a trusted colleague. The problem is that these tasks require context. You need to know the client, know that this prospect prefers to be called on Tuesdays, remember that this invoice has already been disputed. That context lives in your head. Not in a file. Not in a tool. And every time you pass it on, you lose time explaining what should be obvious. If the person changes, you start over. That's why you end up doing them yourself. Not out of a need for control. Out of energy efficiency. Explaining takes more time than doing. Except that doing traps you in a role you didn't choose: that of your company's living memory. We detailed this trap in un article sur les raisons pour lesquelles la plupart des dirigeants ratent leur passage à l'IA. The main obstacle is never technology. It's the reflex of carrying everything alone.

1.3: The real cost of this way of working

Take your real hourly rate. Not your salary — your hourly rate as a business owner: the one that includes the cost of your attention, your deferred decisions, your exhaustion at the end of the day. Now count the number of hours per week you spend on gestures that require neither judgment nor creativity. Gestures a system could perform in your place if it knew your context. Multiply the two. The number you get is what you spend every week maintaining an operation that doesn't grow. It's not an investment. It's a toll. And it's also paid in energy: the kind you no longer have at 5pm to think about what truly matters.

2 – What AI changes when it knows your context

Most business owners have already tried AI. They asked questions, got generic answers, and concluded it was a useful gadget for writing an email but incapable of understanding their business. The problem wasn't the AI. It was the absence of memory.

2.1: Why generic AI solves nothing durably

You open a session. You explain your business, your target, your way of working. The AI produces something correct. The next day, you come back. It has forgotten everything. You start over. This cycle of constant explanation is exhausting. And it explains why so many business owners give up after a few weeks. It's not a problem with the AI's capability. It's an architecture problem. An AI without business memory is a brilliant intern who starts from scratch every morning. We explored this mechanism in depth in un article dédié à la mémoire de l'IA. The conclusion is simple: as long as your AI doesn't retain your context, it costs you time instead of saving it.

2.2: An AI that remembers is an AI that prepares

When AI has a shared business memory, the dynamic changes. It knows you have three companies. It knows your recurring clients. It remembers that this supplier has a 45-day payment term. It no longer asks you the question. It prepares. Wednesday morning, you open Atelier. A follow-up draft is ready for the client who hasn't responded in ten days. A summary of your last exchange with a prospect is waiting in your Cercle. An alert notifies you that a quote expires on Friday. You didn't ask for anything. You didn't configure anything that morning. The AI worked in the background because it knows your rhythm. AI is not a module within Anakoro. AI is the structure of Anakoro. Every module shares the same memory. What you say in Atelier, Koro knows. What Le Cercle records, Prospection uses.

2.3: Automation that doesn't require a manual

Automating, in an SMB with fewer than 20 people, doesn't mean configuring complex workflows. It doesn't mean hiring a technical profile or spending three weeks setting up a tool. It means things get done. The reminder goes out. The meeting notes get written. The follow-up gets sent. Without you having to remember. In Anakoro, this automation is handled by Koro. It watches. It prepares. It suggests — you decide. If you're in a meeting, it takes note of what's moving. If a prospect visits your website at 10pm, Koro Entreprise responds under your brand, qualifies the request, and presents it to you the next morning. You keep control over every decision. What disappears are the gestures between decisions. That dead time that exhausts you without producing anything.

3 – How to get started without a technical budget or IT department

The transition to AI automation requires neither a prior audit, nor a dedicated budget, nor a reorganization of your team. It requires a starting point. Just one. The right one.

3.1: Start with what drains you, not what looks impressive

Don't look for the most spectacular use case. Look for the one that weighs on you the most. The one you keep putting off. The one you do with a sigh. For some business owners, it's following up on pending quotes. For others, it's preparing for meetings. For others still, it's managing contacts scattered across three notebooks and two email inboxes. Le Cercle is free, forever. It centralizes your contacts, your exchanges, your history. It's a starting point that costs nothing and immediately changes the way you find information. If you're looking for ce que le passage au numérique veut vraiment dire pour une structure de 15 personnes, that's exactly it: a concrete gesture, not a project.

3.2: Add a module when the need is clear

Once your contacts are in Le Cercle, the rest comes naturally. You see that a prospect hasn't been followed up with. Prospection can handle it. You're preparing a meeting and looking for the history. Koro prepares it for you. Each module plugs into the same memory. You never start from scratch. You don't import files. You don't learn a new logic. You add a capability to a foundation that already knows your business. That's the difference between stacking software and working within a structure designed as a whole. Your team uses the same space. What your sales rep enters in Prospection, your partner sees in Le Cercle. What Koro prepares for you in the morning, it prepares for them too. No training. No migration. No week lost to configuration. A gradual transition, at your company's own pace. We described what this transition concretely involves in un article dédié à la traversée vers l'IA pour une PME française.

3.3: What changes in your week

After a few days, you stop searching. Information comes to you. The morning brief is ready when you open Atelier. Follow-ups have gone out. Contacts are up to date. You no longer spend your evenings catching up on what you forgot that morning. You no longer copy and paste between two tools. You no longer rephrase the same context to your AI every week. What you get back isn't time in the abstract sense. It's attention. The ability to think about your next hire, your sales strategy, that important client you haven't called back in three weeks — not because you forgot, but because you no longer had the bandwidth. AI automation in an SMB with fewer than 20 people is not an IT project. It's a relief. Silent, gradual, and reversible. You keep the decisions. The AI takes the repetitive work.

What you decide to stop carrying

You can keep managing everything by hand. Rephrasing, copying, following up, searching, remembering. No one is stopping you. No one even sees it, for that matter. But you feel it. The end-of-day exhaustion that isn't linked to difficult decisions — it's linked to unnecessary gestures. The kind no one should be doing manually in 2025. Anakoro exists so those gestures disappear. Not by replacing you. By preparing what you're going to decide. Your company's memory is shared, your modules talk to each other, your AI retains what you tell it. The rest proves itself in use.