Services

From building a product to maintaining it over time, with a constant quality standard.

Building sites and applications
Showcase sites and web applications built from scratch, or new features on an existing base. A healthy architecture from day one.
Modernisation and migration
Taking over existing code, migrating legacy frameworks to modern stacks, without breaking production.
Technical debt and bug fixing
Removing technical debt and fixing deep bugs, so the codebase becomes calm to evolve again.
Testing, CI/CD and quality
Unit, integration and end-to-end tests, continuous-integration pipelines, conventional commits and automated releases.
Performance and optimisation
Performance analysis and optimisation: response times, queries, infrastructure cost and user experience.
Hosting and maintenance
Deployment, hosting and product maintenance over time. I stay available and involved after go-live.

How I work

I start by understanding the domain and the real stakes, not just the ticket.
I work test-first: every behaviour is covered by a test before the code is written.
I keep the domain pure, isolated from frameworks, with the dependency rule checked automatically.
I document architecture decisions (ADRs) so the team stays autonomous after I leave.

My conviction: value comes before price. Two ways to work together, to choose depending on your need.

From 500 €/day, adjusted for billed travel, the share of remote work and the length of the mission.

Recommended

We move forward in small increments of value, and you pay as we go.

Full flexibility: you adjust your priorities from one week to the next, and I take them on board.
Value delivered continuously, with no multi-month tunnel.
You validate each increment before we continue: the risk stays minimal on your side.
Favourable rate, because nothing is wasted on specs that are going to change.

A scope defined upfront, an estimate and a firm price. Higher, because it covers the risk of freezing a need.

Estimate possible, commitment on results.
A fixed specification freezes a need that, in practice, always evolves: it's the riskiest format.
Any change of scope means re-evaluating the estimate and the quote — that's more honest than holding to a figure we already know is wrong.

In both cases, bug fixing is on me: a bug is not a feature.