Everything people ask us. No detours.

With a conversation. You write to us, we reply, and we set up a first call. Then comes framing — the first stage of our method: we get to know your business, your users and the real scope. Everything else follows from it.

No. Come with the problem, not the solution. Framing exists precisely to turn an idea into a clear scope — priorities settled, key journeys, technical direction. If you already have documents, all the better: we use them as a starting point, never as a straitjacket.

There is no rate card: the price is an output of framing, never a point of entry. Once the scope is set, we commit to a firm amount and a firm schedule. The whole reasoning is laid out on the Investment page.

Yes. The studio works remotely across French Polynesia, Australia and France, and collaborates just as easily locally as internationally. Conversations happen over video or in writing, whichever suits you — distance has never stopped a product from being built well.

As long as its scope demands — we do not publish typical timelines, they would be false. What we do commit to: a firm schedule set at the end of framing, and held. You know where you are going before the first line of code.

By milestones, with regular check-ins — never a black box. Every client also gets a dedicated area: the status of their projects, follow-up notes and invoices, available at any time.

We talk about it first, we price the difference, you decide. No quote that quietly inflates, no surprise on the invoice — the scope validated during framing stays the shared reference.

Guiding you is our job, not yours to arrive with the answer. We start from your uses, your users and your constraints, and we recommend a direction. Four ways to build — only one that fits your situation.

You do. The code is written to be picked up: clean architecture, tested, that your teams — or another provider — can keep alive. We build no dependency on us.

Yes, when it is the right call. We start by understanding what is already there — code, architecture, usage — before saying what we keep, what we strengthen and what we replace. And if rebuilding everything is the wrong idea, we will tell you.

That is the fifth stage of the method: maintenance, monitoring and evolutions. As a monthly retainer sized during framing, or as one-off work when something needs to change. Launch is a beginning, not an end.

A product we support is monitored — most of the time, we see the problem before you do. When something breaks, we fix it: that is exactly what long-term support is for.