What we do
Services
Clear technical thinking for businesses that need to move fast without breaking things. Two ways in: I build the software, or I tell you what to build and why.
What I do
Software Development
- Web applications & dashboards
- API design & integration
- SaaS MVP development
- Agentic AI features, evals to production
IT Consulting
- Technology stack evaluation
- Infrastructure & deployment advice
- Technical due diligence
- Where AI actually pays off, and where it does not
What people actually hire me for
Build a product from zero
You have a spec, a design, or a strong idea and no engineering time. I take it from empty repo to something your users can log into.
Best when: you need an MVP in front of real users this quarter.
Add capacity to a team that is behind
You already ship, but the backlog is winning. I join the team and take a slice of it: a service, an integration, a migration. Inside your repo, your process and your review cycle rather than off to the side.
Best when: you need hands that add throughput, not management overhead.
Decide before you commit
A stack choice, a rebuild-or-refactor call, or a codebase you are about to acquire. You get a written assessment you can hand to a board.
Best when: the decision is expensive and reversing it is worse.
Put agentic AI into a product
Not a demo that works once on stage. I build the agent, own the evals end to end so there is evidence it holds up on your real cases, and take it through to production.
Best when: the prototype impressed everyone and nobody trusts it live yet.
Software & consulting
Working with your team
For most of this work I join your team rather than sit beside it. Your stand-ups, your board, your chat, your review process. Not someone who disappears for three weeks and comes back with a branch nobody asked for. I am comfortable being one engineer among several and having my work reviewed like anyone else's.
Most of what goes wrong with outside help is communication, so I over-correct on it: decisions written down, questions asked early rather than assumed, and disagreement raised while it is still cheap. If your team already has conventions for branching, definition of done, or how you write tickets, I adopt them. Fitting how you already work matters more than doing it my way.
Tooling works the same way. Linear, Jira, GitHub, GitLab, Slack, Teams, Notion: whatever you already run, I work in it rather than ask you to add something for me. Your board, your repo, your pipeline, your definition of shipped.
Remote-first, from Antwerp, and on-site when a kickoff or a workshop genuinely needs a room.
How the work runs
Two tracks, and they do not run the same way. Whichever one you are on, scope is written down before anything starts and work goes out in increments you can see, not one delivery at the end.
Websites for local businesses
Fixed scope and a fixed quote up front, so you always know what the number covers. A plain-English update every week: what moved, what did not, what is next. The domain, the code and the hosting stay in your name: there is no account you have to keep paying me to get into, and no part of it stops working if you stop working with me.
Software & consulting
I work inside your setup rather than alongside it: your repo, your tracker, your review cycle, your release process. Progress is visible where your team already looks for it instead of in a separate report, and decisions get written down as they are made. You are buying someone who ships with the team, not a hand-off at the end.
Stack is chosen per project, not per fashion. The tools I reach for are the ones I run in production on my own products.
Available for new projects
Remote-first · Embedded in your team · On-site Antwerp / Belgium · Short-term contracts · Long-term partnerships
Looking for a website for a local business instead? See how that works.