Project
A bounded undertaking with a defined result, date and fixed price.
- Scope and acceptance criteria in writing beforehand
- Fixed price after the design phase
- Handover including documentation
What I build, integrate and run. Each service lists what it delivers and what I advise against.
Applications for workflows no standard product maps cleanly, built to grow with your business.
A decision you can rely on before budget flows into an architecture that can't be corrected later.
The design of the whole: how the parts fit together, where data lives and what happens when a part fails.
Automated delivery with checks that actually block, and a way back when something goes wrong.
Infrastructure as code instead of grown handiwork, including an honest calculation of the running costs.
AI capability built into the systems you already run — on your data, in your infrastructure, with an evaluation that proves the benefit.
Three shapes of engagement, depending on how clear the scope already is. The number you can rely on comes as soon as we have settled it.
A bounded undertaking with a defined result, date and fixed price.
Fixed capacity per month for projects whose scope still shifts with every new finding.
Second opinion, architecture review or technology decision, clearly bounded in time.
The answers that otherwise cost the first quarter of an hour of a first call.
There is no lower limit. A two-day architecture review is as welcome as an application I build for a year. If a project is better placed with someone else, I tell you so in the first conversation.
Billing is by day rate, or at a fixed price once the design phase is done. You get a written order of magnitude for your project before I bill any effort at all. The first conversation and the assessment are free.
Yes, that is the rule. Before changes to a grown system comes an inventory: what runs, what depends on it, and what breaks on a change? I only propose a rebuild when it is genuinely cheaper than the repair.
Code, infrastructure definitions and access belong to you and live in your accounts. Onboarding your team is part of the handover. Working together further is an option afterwards, not a precondition.
In the EU by default. If a project requires a service outside the EU, I name and justify that beforehand, before you sign a data processing agreement.
Yes. Since 28 June 2025 the European Accessibility Act applies, which refers to WCAG 2.1 level AA for web content. I build against it from the start. Accessibility retrofitted later costs more and usually stays incomplete.
You get an honest first assessment — including the times I tell you not to do it.