Let the system do what is now done by hand
I become your technical partner. I learn how your processes actually work, take the manual labour out of them and apply AI where it demonstrably saves time. A fixed monthly fee, a fixed rhythm, and something new live every month.
Who this works for
For companies where people do work a system should be doing. That is not tied to a size or a sector.
Too much happens by hand
Quotes in Word, data retyped from one system into another, an inbox doing the job of a workflow. It works, but it does not grow with you.
Nobody leads the technology
Things get built, but nobody guards the direction. Decisions are made per project instead of per company, and you only see the consequences a year later.
AI was promised, not delivered
You know something is possible with AI, but not what, not where, and not whether it actually pays off. You do not want a pilot that fizzles out, you want less work.
Fixed rhythm, flexible effort
No timesheets, no half-days to tick off. You buy a fixed rhythm and a single point of contact, not a bag of hours.
Understand first, then build
A fixed rhythm
I bring the proposals
One process at a time
From shadowing to measurable
I have to genuinely know your processes before I can automate them. That time is not a run-up, it is the measurement everything afterwards rests on.
Shadow and measure
I sit with the people doing the work and record where the time leaks away: which action, how often, how long. At the end there is a ranked list of candidates, ordered by what automating them is worth.
First process live
We pick one, I build it, and it goes live alongside the existing process. Within that month you see the difference against month one, or we drop it and take the next.
Rhythm
A next process every month, plus maintenance and further development of what is already running. And technical decisions that no longer sit for six months.
What does not happen
Taking technical leadership does not mean turning your company upside down.
No reorganisation
Nobody has to work differently before the system exists. The change follows the software, not the other way around.
No big bang
No migration weekend, no date on which everything is suddenly different. Each process goes live on its own and can be rolled back on its own.
No AI for the sake of AI
If a simple script does it cheaper and more reliably than a model, it becomes a script. AI is a means, not a goal.
No lock-in
Code, data and documentation are in your name and in your environment. Even if we stop tomorrow, someone else can carry on.
Where this already runs
Ongoing engagements where building, automating and deciding together all run into one another.
When I can start
I take on a limited number of partnerships at a time. This is what is free per week, updated by hand.
Next start: Jan 2027, 3 days a week.
Updated 25 August 2026What it costs
One fixed monthly fee. No timesheets, no reconciliation, no surprise at the end of the quarter.
per month, excluding VAT
- A fixed rhythm: contact weekly, results monthly
- Building, maintenance and further development in one
- Technical decisions and initiative, not just execution
- A direct line: no ticket system, no account manager
- Minimum of 3 months, monthly notice after that
Then start with the review
Three weeks, fixed price, and afterwards you know exactly what you have and what is worth tackling. You are tied to nothing, and I find out whether I can genuinely help you.
More or less capacity is possible and the fee scales with it. What does not scale is the rhythm: something going live every month is what the whole model runs on.
More about the technical reviewFrequently asked questions
Do you work on site or remotely?
Whatever works best at the time. Early on I want to be there, because who retypes which file where and why there are three exceptions is something you only hear sitting next to the person doing it. Once that is clear, most of it works fine remotely.
What if there is little to do in a given month?
Then there is time for maintenance, overdue technical work and the things that otherwise never happen. The fee is fixed, how it is spent is not. If it structurally runs dry we scale back: I do not invoice for air.
Do we have to do a technical review first?
No. But if you already have software running, it is the fastest way to see whether we fit: three weeks, fixed price, and you are tied to nothing afterwards.
Do you only work with Laravel?
I build in Laravel because that is where I am fastest and most reliable. But automation is more often about connecting systems you already have than about building new ones, and that is independent of the stack.
Do you replace our current team?
No. I take on technical leadership and the things that keep getting postponed. If you have people, we work together: I am there to let your team do more, not to replace it.
What if we want to stop?
Three months minimum, monthly notice after that. Everything built keeps running and is yours, including the documentation someone else needs to carry on.
Shall we look at what can be automated?
Thirty minutes and you know whether this model fits. If it does not, I will say so, and usually I know what would help you instead.