Custom management software
The software adapts to you. Not the other way round.
Most companies don't have a software problem. They have a process problem that the software simply set in stone. That's why I never start from the program: I start from how you work today.
Custom management software is a system built around one company's specific processes rather than a standard model meant to fit everyone. It makes sense when the way you work is a competitive advantage, and bending it to fit a packaged product would mean losing it.
When it is genuinely worth it — and when it is not
Custom software is worth it when your way of working differs from your competitors' and that difference makes you money. If your process is standard, an off-the-shelf product costs less and works perfectly well — and I will tell you that before we start, not after.
The most reliable signal is not revenue: it is the number of exceptions. If every order has its own rule, if a quote passes through three people, if someone keeps a personal spreadsheet "because the system doesn't handle it", then standard software is costing you more than it saves.
The second signal is the indispensable person. If someone "knows how it's done" and the department stops without them, that knowledge needs to live in the system. Not to replace the person — to free them.
What I build
I build the system that holds together information currently scattered across different places: orders, stock, production, customers, documents. One place to look, kept up to date on its own.
Concretely: order and job management, customer and supplier records, stock and inventory, production planning, documents and electronic invoicing, control dashboards, role-based permissions, and integrations with the tools you already run.
Everything done twice today gets done once. Everything you can only find out by asking someone becomes visible at a glance.
What happens to your existing data
Historical data gets migrated. No company starts from zero: archives, customers, order history and documents move into the new system, checked row by row before going live.
Migration is the phase where projects fail, so I treat it as a project inside the project: extraction, cleaning, cross-checking against the old system, and a period where both systems run side by side until you are confident the new one tells the truth.
What it includes
- Process analysis before a single line of code
- Integration with what you already use (accounting, stock, email)
- Historical data migration, nothing left behind
- Up to 2 years of warranty on delivered software
The other routes
02
Applied artificial intelligence
Not "doing AI". I take the three manual jobs that cost you the most hours every week and hand them to the machine.
Read more03
Websites and e-commerce
A site that brings in enquiries while you do something else, and that gets found both by Google and by the AI assistants people now ask for advice.
Read moreThe first step
We start with a conversation, not with a quote.
Forty-five minutes in which you tell me where your day gets stuck. At the end you will have at least one useful thing: my honest opinion on what to tackle first — even if you then decide to do it with someone else, or not at all.
No commitment, no email sequence afterwards. If you are not the right client, I will be the one to say so.