From an idea to a product that works.

It depends on scope, so every project gets its own quote. The main drivers are the number of user journeys, external services and user types. You work directly with the person writing the code, with no layers in between, which keeps my rates well below agency pricing. Tell me about your idea and I'll give you a concrete number. For the factors behind it, see how much it costs to build an MVP.

The timeline comes from the scope and is written into the quote before work starts. It depends on the technical work, but just as much on how quickly decisions, content and account access arrive. You won't be waiting in the dark, either: I work in iterations, so you see and test the product as it takes shape.

You do, from day one. The repository, server, domain and third-party accounts are all registered to you, not to me. If you later want someone else to take the product forward, they can do so without asking my permission or relying on credentials only I hold.

Less than you'd think. A clear picture of the problem you're solving, who will use the product and the core journey they need to complete is enough to begin. Later on we'll need account access (domain, payment provider, external services) and someone on your side who can make decisions so the project doesn't stall waiting on answers.

You set the pace. Usually we watch how people use the first version and build the next phase around what they've actually shown they need. If you just need the product kept current and bugs fixed, that's covered by support and maintenance. And because the code is written for others to read, your own team can pick it up too.

Me, directly. There are no account managers or project managers between you and the person writing the code, so technical questions get answered without being passed around, and changes of direction get settled in one conversation. I explain every decision in business terms, so you can weigh in without needing to code.