Software for problems that don’t fit a template.
I build AI systems, custom software and web applications for companies that have outgrown spreadsheets, SaaS limitations or disconnected systems.
Best suited for business-critical software and complex workflows.
A few lines is enough to start. I read everything myself.
Your software problem probably isn’t “we need a developer”.
It’s usually one of these five. If you recognise yourself, the conversation is short.
A manual process is eating hours every week.
Copy-paste between systems, spreadsheets as the source of truth, and one person who knows how it actually works.
Your SaaS tools don’t talk to each other.
Data is re-entered by hand, reports disagree, and nobody trusts the numbers in the meeting.
Your internal software has become impossible to maintain.
Every change breaks something else, and the people who wrote it are gone.
Your AI prototype works, but it isn’t production-ready.
No evaluation, no guardrails, no clear view of cost or failure modes at real volume.
Your team needs a senior engineer who takes ownership.
Someone who decides, writes it down and ships it, instead of waiting for tickets.
Three categories. Concrete things inside them.
If you can find your problem somewhere in this list, we have something to talk about.
Put AI inside the workflow.
AI where it removes real work, with tests and guardrails around it. Not a chatbot on the side.
- 01AI workflows
- 02Document intelligence
- 03RAG / knowledge systems
- 04AI automation
- 05Evaluation & QA
- 06Human-in-the-loop systems
Replace the spreadsheet. Connect the systems.
Internal tools, APIs and integrations for when your business doesn’t fit a generic SaaS box.
- 01Internal tools
- 02Business applications
- 03APIs
- 04Integrations
- 05Process automation
- 06Legacy modernisation
Ship the application your customers use.
UX that holds up under real use, performance you can feel, security you can defend in an audit.
- 01Customer portals
- 02SaaS applications
- 03Dashboards & reporting
- 04Business platforms
What those three categories look like in practice.
Three shapes of work I take on most often. Same building blocks, different business problem.
Your data, exposed safely to the people who need it.
The manual process, written down as software.
Grounded in your data, checked before it ships.
Not a list of everything I’ve touched. This is the stack I can take responsibility for in production.
- Laravel
- PHP
- Symfony
Where most of the business logic lives.
- React
- TypeScript
Interfaces for customers and internal teams.
- Google Cloud
- Docker
- Terraform
Reproducible environments, not snowflakes.
- LLMs, RAG & evals
- REST and event APIs
- Microsoft Entra
- SAP integrations
AI as an engineering capability, not a personality.
The problem, the build, what changed.
Anonymized projects I actually built. No client logos, no invented metrics. Open a case for the full notes.
Planning, fieldwork, customer updates and invoicing lived in separate systems that never quite agreed.
One operations platform with route planning, webhook sync, field evidence and draft invoicing.
Disconnected tools → one authoritative place for the operational day
Read more →Tour attendance and guide pay depended on fragmented check-in evidence and manual reconciliation.
Multi-tenant platform with photo-based group counts and commissions. Mismatches go to human review.
Manual disputes → check-in you can audit, with a person still in the loop
Read more →Leads arrived from forms, ads and marketing tools into inboxes and spreadsheets that disagreed.
Webhook-fed lead capture, deduplication that keeps every source event, and explicit deal stages.
Scattered channels → one path from lead to deal you can inspect
Read more →One person.
No handoffs.
You work directly with the developer designing and building your software. No sales person, no project manager, no chain of people between you and the code.
Direct communication
You email me, I answer. Nothing is relayed through an account layer.
No account manager
The first conversation and the last one are with the same person.
No handoff to junior developers
The person who scopes the work is the person who writes it.
Faster technical decisions
One conversation instead of an internal approval chain.
One person accountable
For the implementation, end to end, including the parts that go wrong.
Architecture stays connected
Design decisions and the code that implements them never drift apart.
Simple model. Strict execution.
Explicit decisions, maintainable software, no theatre.
Discover
We align on success metrics, map workflows and systems, and name risks early. You get a scoped plan with understandable trade-offs.
- A scoped plan with trade-offs in writing
- Named risks instead of surprises
- A first milestone worth committing to
Build
I ship in milestones with demos, automated tests, and documentation. You see progress continuously.
- A working slice you can review every milestone
- Tests where they save pain
- Decisions written down when they matter
Scale
I add observability, harden integrations, and tighten playbooks as usage grows, so reliability improves over time.
- Monitoring and alerting you understand
- Runbooks your team can follow
- Code and notes so you can run it without me
The questions I actually get.
Still unsure? Send a short message. I’ll say if someone else is a better match.
Often, yes. Usually I take the part that needs senior depth (architecture, integrations, the AI layer) while your team keeps the product context. I’d rather make your team faster than replace it.
Usually. Laravel, PHP, React and the cloud around them are home turf, and I’ve inherited plenty of other people’s code. If your stack is somewhere I’d be slow or risky, I’ll tell you instead of learning on your budget.
Yes, and not only LLM ones. Sometimes rules, classical ML or plain search beat a big model. I pick what fits the problem and your budget, then treat it like any other software: tests, monitoring, guardrails.
From a focused few-week automation to multi-month platform work. Business-critical software and complex workflows are the sweet spot. If a project needs a team of five, I’ll say so and help you scope it properly.
Yes, from Belgium, mostly with clients across Belgium and the EU. On-site when a kickoff or a workshop genuinely benefits from it.
A short message. I reply with a couple of clarifying questions, or a straight “not a fit”. If it makes sense we book a short call, and afterwards you get a written summary with a suggested next step. No obligation.
A scoped first milestone, then delivery in reviewable slices with demos and documentation. You’re buying experience and blunt honesty about what is worth building now, not the cheapest day rate on the market.
Have a problem worth turning into software?
Tell me what you’re trying to build, automate or fix. A few lines is enough.
I read everything myself. No newsletter, no CRM sequence.