You have the idea.
I build the product.

Because there is no one between you and the person writing the code: no project manager translating, no brief losing its shape as it changes hands. The trade-off is real — I take on a limited number of projects at a time, and I say so before we start, not halfway through.

That is what scoping is for: understanding the work, choosing a first flow and writing down what belongs in the project. You leave with a scope, a technical recommendation and the questions to resolve before estimating delivery.

AI helps me explore options, write code and prepare checks. I remain responsible for architecture, quality and delivery. Time saved depends on the project: it is measured in actual work, not promised in advance.

Everything. The code, the repository, the hosting accounts and the domain name are in your name from day one. No licence, no subscription owed to me to keep using what you paid for.

You get written documentation for the everyday moves: edit a text, add an item, publish. If that isn't enough, The Build + Care adds weeks of support after go-live, for as long as it takes you to feel comfortable. The goal is for you to be able to do without me, not the opposite.

We see it during the framing, and I say so. If the scope goes beyond what one person can deliver properly, I tell you rather than agreeing and grinding through six months. A small product that ships and runs beats a large one left half-finished.

Services are not open yet, so no rates are published at this stage. The principle is a fixed price per project type rather than a day rate: price and date are settled at the end of the framing and do not move, unless you change the scope.

Yes, a project can run entirely remotely, in French or in English. I am based in the Lyon area, so meeting in person stays possible when it makes sense — usually for the framing.