Plans

It depends on scope, which is why there is no price list. What we can tell you is how the number forms: a tailored website is the most predictable, an MVP depends on how many flows it has, and a platform with several integrations is where variation is widest. The proposal gives you a fixed figure per phase, not an open estimate that grows along the way.

A tailored website usually runs four to eight weeks. An MVP with authentication, payments and an admin panel, two to four months. Larger platforms are phased, so you have something in production before everything is finished. Dates go in the proposal, not vague ranges.

Less than you think. We need to understand the business, who the users are and what you consider a good outcome. You do not need written specifications, wireframes or technical decisions made: that part is our work, and doing it with us usually beats bringing it done.

The same people you talk to. We do not hand the project to another team once it is signed, and we do not subcontract the build. When a specific specialism is needed, we tell you who and why.

We expect it. We work in short cycles precisely so changes stay cheap while they still are. What we ask is that the change is explicit: we reassess the impact on scope and timeline, you decide with that in front of you, and we move.

You do. Code, repositories, domains and service accounts are in your name from day one. We do not use closed platforms that force you to stay with us, and handing over to another team, if that day comes, is a matter of granting access.

Yes, and often. We can join as engineering reinforcement on a product that already exists, own a specific part, or work alongside the people already there. In that case we adapt to your process, not the other way around.

The product keeps living, and there are three paths: you keep it, with your team from there; we keep a maintenance and evolution agreement with monthly hours; or we come back for a new phase when you need it. None of them forces the others.