Everything between an idea and a releaseEverything betweenan idea and a release

It depends entirely on scope, and we would rather give you a real number than a misleading one. Tell us what you are trying to build and we will come back with a considered estimate - usually within a few days of the first conversation. Quoting a figure before understanding the problem helps nobody.

We do fix the price, once the scope is actually known - which is what discovery is for. A fixed price quoted before anyone understands the problem is either padded to cover the worst case, or it is about to be revised upward through change requests. Both are worse for you than spending two weeks working out what you are actually buying.

A deposit to start, then invoices against delivered work at agreed milestones, with the balance on handover. Retained engagements are invoiced monthly. Everything is set out in the proposal before you commit, and we can invoice in USD, EUR, GBP or INR.

Scope changes are normal and we plan for them. Anything outside the agreed scope gets estimated in writing before work starts, and you decide whether it is worth it - often the answer is to swap it for something already in scope rather than add budget. You will never receive an invoice for work you did not approve.

You do, completely, once invoices are settled. That includes source code, design files, and the repositories and accounts they live in. We do not retain a licence, we do not hold anything hostage, and we do not build on a proprietary platform that requires you to keep paying us. Any third-party open-source libraries remain under their own licences, which we list for you.

A discovery phase is two to three weeks. A focused first version of a mobile app is typically three to five months from kickoff to store submission; a web platform is often a little faster. We give you a real schedule after discovery, not before - an estimate offered before anyone understands the scope is a guess dressed up as a commitment.

You will see working software every two weeks, on a staging environment you can use yourself, plus a written summary of what changed and what is next. No monthly status decks. If something has gone wrong you will hear it in that fortnight's update rather than at the end.

One decision-maker who can answer questions within a couple of days, access to whoever understands the domain, and honesty about constraints - budget, deadlines, internal politics. Projects almost never fail on technical grounds. They fail because a decision sat unanswered for three weeks.

Yes, and we would rather do both. When design and engineering are in the same team, the questions that usually surface as a handover problem get resolved in a conversation. We are also happy to build from your existing designs or design system - we will just flag anything that is going to be expensive to implement before we start.

Sometimes, and we will be straight with you about which case you are in. We start with a technical audit - typically one to two weeks - that tells you honestly whether the existing codebase is worth continuing with or whether a rebuild is genuinely cheaper. Occasionally the answer is that you should stay with your current team and fix the process instead.

Every project includes a support window - usually 30 to 90 days - where we fix anything that surfaces at no extra cost. After that you can move to a retained arrangement for ongoing work, call us ad hoc, or take it fully in-house. All three are fine; we build so that the third is genuinely possible.

Yes, and it is a goal rather than a grudging concession. Every project ships with written documentation covering architecture decisions, setup, deployment and the known rough edges. We will run handover sessions with your developers and stay reachable for questions afterwards.

We can, either on your infrastructure or on a managed platform, with monitoring, backups and security updates handled. We will give you an honest cost comparison between self-hosting and managed services, including the operational time self-hosting actually costs - rather than the recommendation that happens to suit us.

During the support window we fix it, at no charge. After that, defects in work we delivered are still handled at no charge where they are genuinely our error - we do not litigate the boundary. New features and changes are quoted normally.