Only a couple of people know how your company really works.
And a lot of it is not written down.
Sound familiar?
Clear first, then clever.
What AI can actually do, once your business is written down.
Most companies that start with AI start with a tool. They buy a subscription to an AI service. Someone tries it for two weeks. Then it quietly stops.
The technology is rarely the problem. There was just nothing for it to work on.
AI can't do anything with knowledge that was never written down. If the way you work lives in a couple of heads, a chat group and a spreadsheet nobody dares touch, every tool you put on top of it gives you the same thing. An answer that sounds convincing and is wrong.
So I don't start by building. I start by finding out what actually happens in your company, and I write it down.
Only then is it worth asking which parts should be made clever. And which parts should deliberately stay exactly as they are.
The part most people skip
A good part of what I do is about what not to do.
Every Scan ends with a written list of what I advise against. One of the four buckets exists purely for work that should stay with a person.
That's not caution. It's the list most advisors leave out — what not to build, and why.
- Your company is not too small. Size doesn’t decide it. What decides it is how much of the work depends on one or two people. The gain is in work nobody wrote down.
- The owner is in the room. Without you this doesn't work — not because I need your signature, but because half of what I'm looking for is only in your head.
- What gets written down is yours. Everything I deliver you can keep using, editing and extending. Including if you never work with me again.
- Not everything should be clever. Part of your work belongs with a person. That is a choice, not a backlog, and I say it out loud.
Every process goes into one of four buckets.
That's the whole model. Simple enough to explain to your team. Strict enough to stop you investing in the wrong thing.
This work does not need to exist. A report nobody reads, an approval that is always yes, a list kept twice. Costs nothing to remove, returns time immediately.
The work stays, the way it is done changes. Fewer handoffs, one place instead of four. What changes here is the shape of the work, not the tools.
Happens constantly, has a fixed shape, and you can tell within a minute whether the answer is right. This is where building pays off.
Judgement, relationships, exceptions, or real damage if it goes wrong. Deliberately not automated. A choice, not a backlog.
How I sort
Every process gets scored against five things. The first one outweighs the rest: what happens if it goes wrong and nobody notices. Then how often it happens, whether the knowledge is written down, whether the input is clean, and whether you can check the result within a minute.
Want a first look at your own? Answer eight questions from a scan day and get a quick sort, free.
Try the quick sortThree steps, then maintenance.
Each step gives you something you keep, and you're never locked into the next one. The Build and maintenance run on a Core, so they come after it.
1. The Scan
I come for a day. I talk to you, and then to the people who actually do the work. I walk the floor and look at screens. If your team is spread out, we do it in a few video calls instead. At the end I go through a rough first picture with you. The full map follows in the report, within five working days.
- The process map of your business. As it is, not as it was meant to be.
- Every process sorted into the four buckets, and three things I would do first.
2. The Core
Right now, how your business runs is scattered. Some of it lives in a few heads, the rest in inboxes, chat threads, spreadsheets and folders. That works as long as everyone can ask each other. It stops working when the person who knows is busy, or away.
The Core brings it all together in one digital hub with AI built in. You and your team use it, and everything made with it draws on your company's prices, policies and way of saying things. So a quote, a reply to a complaint and a post for your website all start from the same base. And when someone needs to know something, they ask the Core before they ask you.
What goes in depends on your business, and the Scan already showed where it all lives. Much of it may already sit in folders. The work is in the rest. I fill in what was never written down, and where two versions disagree, you decide which one holds.
- What your team now has to ask around for, brought into databases, with an AI project on top that answers from them. Every entry shows when it was last checked, and who keeps it up to date.
- It lives in your accounts, not mine. You get the short list of subscriptions it needs, and what each one is for. My access is for the work only, and it ends when the work does. Nothing that touches customer data gets connected until you've decided the rule for it.
- Before I hand it over, I connect it to a job your team will notice. We choose it together when we go through your Scan report. For example: the questions your customers ask most often get a reply drafted straight from the Core. Customer service checks the draft and sends it, instead of starting from a blank page.
3. The Build
The map from the Scan shows what else is worth building. The Core makes it possible, because everything I build reads from it. In the Build I take the next item from that map and make it work. An internal app your team works in every day. A product advisor on your website that helps customers choose the right product. Invoices that land in the right place. Reports that arrive without anyone putting them together. An assistant that answers customers with your rules.
- The next item from your map, built on your core and in use by your own team.
- Your people trained on it, so it keeps working when I'm gone.
4. Maintenance
A core that isn't maintained goes stale. Rules change, prices change, your team changes. I keep it current, feed back what comes out of daily use, and put the core to work in small new places: an FAQ page, a partner update, a starting guide for a new colleague.
Taking it over yourself, once it runs, is exactly the intention.
Fixed prices. The Build is quoted before it starts.
All amounts excluding VAT. The prices are for owner-led companies, where I work with the owner directly. There is no headcount limit. What matters is that you're in the room. If a job needs travel and an overnight, I say so before we book, not after.
Free scans
The Scan is €1,750. Until the 31st of December 2026 it's free. What I ask in return: a full day of your time, the report read before we sit down with it, and three things picked from it.
Founding Core price
The first three Core projects go out at €4,500 rather than €8,500. In exchange: permission to describe the result publicly, your name as a reference, and half an hour on the phone with someone weighing up the same decision. Ends at three, or on the 31st of December 2026.
What I don't do
- Resell software on commission. That makes my advice unreliable.
- Place people with you.
- Build something that only keeps running while I'm being paid.
- Promise percentages of time saved before anything has been measured.
- Take on work where the owner isn't in the room.
Taktältarna, Åre
Taktältarna sells rooftop tents from its own showrooms in Duved and Västerhaninge, with partners across Sweden and Denmark. I spent a day there, asking the owner how the work actually moves and where it gets stuck.
Every one of them went into a bucket: Cut, Simplify, Add AI or Keep Human. I didn't recommend a tool. I recommended what to fix first, starting with a few things that needed nobody outside the company.
Then we built the Core: the products, the suppliers, the rules and the answers to what customers keep asking, written down in one place. The team now uses it as its intranet. Customer service works in an app built on top of it.
This method was not invented on a whiteboard.
It was worked out on a real business.
Rental Valley rents out homes in Portugal and the Netherlands. It now runs on an AI core — invoices process themselves, owners get answers, prices are advised, reports simply arrive.
Every part of this method broke there first, and got fixed there first.
Tim Boffe
Process thinker, and the person who runs brainsandbuckets. Sees in a day where the work gets stuck, and can draw it in a way your team recognises and reacts to. That last part is the craft: a process map nobody responds to is a nice picture with no value.
Tim asks the questions you stopped asking because it was always done this way. He comes himself, he draws it himself, he builds it himself, and he is your only point of contact from the first call to delivery.
Niels Marcelis
Entrepreneur. Built Rental Valley, a rental business with homes in Portugal and the Netherlands, and turned it into an organisation running on an AI core.
Email me and we'll book 30 minutes.
I'll ask a few specific questions: where it gets stuck, what costs the most time right now, and what you'd like gone by tomorrow. After that call you'll know two things — whether a Scan makes sense, and whether I'm the right person. If the answer to either is no, I'll say so.
Book the free introduction call