What people ask
beforehand.

Six to twelve weeks for a first version in production, in short cycles, with a weekly demo. Longer projects exist, but they are always cut into deliverable milestones: we never sign for six months in one block.

A fixed price per milestone, agreed before we start, rather than an hourly meter. You know what each stage costs before launching it. Requests outside the agreed scope are quoted separately and decided by you: they never slip into the invoice.

The first conversation, no: around thirty minutes to understand where you stand and tell you honestly whether we are the right people. The detailed scoping that follows, which produces a document you can use even if you go elsewhere, is billed work.

Yes, and it is the default. The studio is in Brussels, clients are not always. Weekly check-ins happen over video, and we travel when a step genuinely calls for it, a scoping workshop or a delicate switchover.

One person who can decide, and feedback within the week. That is the only real dependency: a product moves at the speed of decisions, not of code. Three weeks waiting on an opinion costs more than an extra feature.

It almost always changes, and that is usually a good sign: it means we learned something while building. The change is quoted, decided with you, and what comes in either pushes something out or moves the date. What we refuse is to pretend nothing happened and deliver late without saying so.

The repository is yours from day one, not handed over at the end. You, or a provider of your choosing, can look at it whenever you want. It is also the best guarantee that nothing is being held hostage.

You do, entirely, history included. We hand over the repository, the documentation, the deployment procedure, and the accounts for the services used are opened in your name. You can take the product to another team without asking us anything.

Anything that stems from a defect in what we delivered gets fixed, no debate and no invoice. For the rest, changes, new features, scaling, we agree on either a monthly arrangement or one-off work. Nothing ties you to staying.

Often, yes. We start by reading the existing code and infrastructure, after which we say plainly what can be salvaged, what must be rewritten, and what it costs. Sometimes we advise against taking it over: that is an honest answer, not a dodge.

Yes, and it is put in writing before we start. We reuse nothing of what we see at your end, we only name a project as a reference with your agreement, and access to production environments stays limited to what is necessary.

Yes, as a tool, and it changes nothing about what you judge us on: what is delivered, tested and put into production. When AI is inside the product itself, that is a subject of its own, with its own measurements and guardrails.

The choice is made with you at scoping, depending on how sensitive the data is and what you are bound by. In practice it is almost always in Europe. When a third-party service is needed, we tell you which one, where it processes data, and what it does with it.