I build, rescue and upgrade the software your business runs on
Web platforms, SaaS and mobile apps in Laravel and Vue. I write the tests first, fix what I find along the way and keep watching after go-live, so you hear about a problem from me, when it is already solved.
Sound familiar?
These are the situations I get called for most.
“Our system runs on a PHP version nobody supports anymore.”
I upgrade it while your people keep working in it. Tests first, old and new compared on real data, go-live at night with a way back.
How one upgrade went →“The developer who built it is gone.”
I take over systems without documentation: read the code, write down how it works, cover it with tests, and only then change it.
Legacy rescue →“We need a platform or SaaS, and it has to be right the first time.”
Multi-tenant platforms with a separate database per customer, billing, roles and a mobile app on the same API. Built by one person who owns the result.
See what I've built →“Money runs through it. It cannot go wrong.”
Payments and payouts built so a retry, a double webhook or two clicks at once can never charge or pay twice.
How the payouts are built →“We want AI in our product, but not the risk.”
AI that drafts and researches while a person approves. It only sees the data it needs, cites its sources, and every exchange is logged.
AI, done safely →“Our team needs a senior for a few months.”
I join agencies and product teams as a senior developer, also white-label. I work in your process and your repository, in Dutch or English.
About me →Two projects, told in full
No wall of logos. What was at stake, what I did, and what I found that nobody had asked about.
A live order system from CakePHP 3.6 to 5.4, with zero errors for users
A Dutch e-commerce company runs its orders, stock and courier routes on it every day. 353 tests first, six days to go-live, and a list of security holes fixed that nobody had asked about.
Marketplace payouts that can never pay twice
Creators get paid through Stripe Connect or PayPal. Seven things that go wrong with money in real life, and the rule and the test that stop each one.
How I work
Your system is what your business runs on. I treat it that way.
Safety net first
Before I change a line, I write automated tests that record how your system behaves today. Every step only goes ahead when they still pass.
Fix what I find
If I come across a security hole or an old bug, I don't walk past it because it wasn't in the quote. I fix it and tell you.
Keep watching after go-live
After a major update I read the logs myself for days. Problems are fixed before you or your users know there was one.
Code review for a fixed €950
Not sure what state your system is in, or what an upgrade would take? I read the code and tell you, in writing, before you commit to anything bigger.
- I read the code and the dependencies of one application
- A written report in plain language: what is out of date, what is risky and what is fine
- Security findings, ordered by how urgent they are
- A step-by-step plan for the upgrade or repair, with a fixed quote
- A call to walk you through it
If you order the work from the report, the €950 is deducted from that invoice.
Is your system very large? Then I tell you before I start, not afterwards.
Let's work together!
Tell me in a few sentences what you have and what you need. You get a reply from me personally, usually within one working day.
