Questions worth asking before you hire anyone

There is no useful list price, because two projects that sound identical in a first email can differ by a factor of five in practice. What moves the number is scope and certainty: how many distinct screens or flows there are, whether you need a content system someone else will maintain, whether it talks to payments, logins or third party systems, whether designs already exist, and how much of the requirement is still undecided.

We quote a fixed price for an agreed scope, so the figure you approve is the figure you pay. If the scope changes later, we price the change before we build it rather than after.

Payment is tied to milestones agreed before work starts. Each milestone is a piece of working software you can look at, not a date on a calendar, so you are paying against visible progress rather than trust.

The milestones, what each one includes and what each one costs are written into the proposal, so there are no invoices you did not expect.

It depends on scope, and on how quickly decisions and content come back from your side, which is usually the real constraint rather than build time.

You get a timeline with the proposal, before anything is agreed, and we tell you what we need from you and when. If something slips, you hear it when we find out, not at the deadline.

You do. The repository, the hosting, the domain and every third party account are in your name, and we work inside them rather than holding them on your behalf.

Nothing is locked behind us. If you decide to take the project to another developer, there is no handover to negotiate, because you already hold everything.

If something we built is broken, we fix it free for 30 days after launch. That is a defect warranty, not a change budget: new features and changes of mind are quoted separately.

After that, you can leave it alone or put the project on ongoing care, which covers updates, monitoring, performance and search work. Plenty of clients take the first option, and that is fine.

Yes, on request, before you tell us anything about the idea. Send us yours and we will sign it, or ask and we will get one in place.

Often, yes. We start by reading the code and telling you honestly what shape it is in, what it would cost to stabilise and whether continuing is a better use of money than rebuilding.

Sometimes the honest answer is that a rebuild is cheaper than the repair. We would rather say that up front than bill you to discover it.

Yes. The studio is remote and works with clients worldwide, in English, and we reply to enquiries within one business day.

In practice we overlap with your working hours for calls and keep everything else written down, so a time difference slows nothing but scheduling.