Systems, not tools
It isn't the AI that makes the difference.
It's the workflow around it that does.
Whoever gets somewhere with AI today isn't working with AI. They are working with systems — workflows ordered once, set up once and used over and over again afterwards. The effort happens once. The benefit happens every time.
Working with AI is not the same as having a system.
From the outside both look identical: someone sits in front of an AI and gets a result. The difference only shows the second time round — and the twentieth.
| Working with AI | Having a system |
|---|---|
| You explain the context again every single time. | The context is fixed once and travels with the task. |
| The result is good sometimes, and sometimes not. | The result is consistently good because the route is the same. |
| You remember the good prompt — or you don't. | The good route is written down and simply gets called up. |
| The effort stays just as high every time. | The effort was high once and is small from then on. |
| You cannot hand it over to anyone. | You can hand it over — to a person or to the AI. |
Four steps. The first one is the one people skip.
None of these steps is technical. Technology only enters at step three — and is the smallest part of the work by then.
Write down what you already do.
Don't plan the future, note down the present. How does a blog post, an offer, a client conversation actually come about in your business today? Which steps, in which order, with which documents? Most systems fail right here — because that note never gets written.
Order the workflow before you hand it over.
AI does not make an unclear workflow clearer, it makes it unclear faster. So tidy up first: what genuinely belongs, what is mere habit, what can go? This step is uncomfortable because it forces honesty — and it is the one that makes the difference later.
Build it once.
Now the tool comes in — and specifically the one that fits the workflow: a skill for something you need often; a board for something you have to keep an eye on; an agent for something that should run without you. Not the other way round.
Let it run and sharpen it.
A system is never finished, and that is not a flaw. The difference is: from now on you improve one thing instead of reinventing it every time. After the third run you notice you have stopped thinking about it at all.
Seven systems that carry my business.
None of them appeared in one go, and none was big at the start. Each began with a task that annoyed me for the third time. For each one there is an article here in which I take it apart.
The website
I build my website myself, change it myself and optimise it myself — no service provider in between, no waiting for a wording change. The part that pays off most is not the building, though. It is what happens every week afterwards.
The content workflow
An article does not come about in a chat window here, it comes about in a workflow: collect sources, condense, write, proofread. Always the same route — which is why it is always the same standard, even on a day when I don't feel like it.
The command centre
My business sits on one board: offers, content, tasks, numbers. Not because I like boards, but because otherwise I cannot see what is actually going on — and because decisions without an overview are gut decisions.
Capabilities instead of prompts
A good prompt helps once, and next time you go looking for it. A capability the AI keeps helps every time. That is exactly where the line runs between “I typed something good once” and an actual system.
What runs without me
Some things should not wait for me to remember them. An agent gets a goal instead of an instruction and picks the steps itself. That is the stage a system moves towards — but only once the workflow before it is clean.
Tools of my own
When I cannot find anything that fits a problem, I build it — without writing a single line of code myself. One of those tools has since turned into a product that other people use.
The launch
Landing page, emails, checkout, lead magnet: it feels like a creative feat of strength, but it is a workflow with fixed steps. And workflows can be set up once instead of being suffered through every time.
Frequently asked questions
What is the difference between an AI tool and an AI system?
The tool is the instrument, the system is the workflow around it. A tool answers a single question. A system makes sure the same task gets done equally well every time: with the same steps, the same documents and without you having to explain the context all over again.
Where do I start if I want to build myself a system?
With writing it down, not with the tool. Take a task you do at least once a week and note the steps exactly as you actually go through them today. That note is already half the work. Only afterwards do you decide which parts the AI takes over.
Do I need programming skills for this?
No. Everything on this page comes about in ordinary language: you describe the workflow, the AI implements it. Even the tools of my own were built without a single line of code written by hand. What you need is clarity about your workflow — not about technology.
Is this even worth it for a one-person business?
Especially there. In a larger company recurring work is spread across several pairs of shoulders. As a solopreneur you carry it alone. Every task you order once and never have to think through again gives you back time that nobody else is going to give you.
How long does it take before a system pays off?
The first run costs more time than the task itself — that is the price, and you pay it knowingly. From the second or third time round the arithmetic flips. With the systems on this page the effort paid for itself after a handful of runs.
And where do you stand right now?
Six questions, three minutes — and you know which workflow to order first. Free, no sign-up.
take the position check →