The questions we get asked before anybody signs anything.

Both. The difference is what we optimise for: a startup usually needs the shortest honest route to something real users can try, while an established business usually needs the new thing to fit what already exists without breaking it. We say which of those we think you are before quoting.

Yes, and it is a large part of what we do. We start with an audit of the codebase and infrastructure, tell you plainly what is worth keeping and what is not, and give you a cost for each path. We will not tell you to rebuild something that works.

Yes, before any detail is shared if you prefer. Send yours over, or ask and we will send ours.

Because a price without scope is a guess, and a guess published on a website turns into an argument later. Two apps with the same description can differ fivefold in cost depending on integrations, compliance and expected load. We would rather spend an hour understanding yours.

Marketing sites: four to eight weeks. Mobile apps: eight to sixteen weeks. Custom platforms and SaaS products: three to six months to a first release. Those are working ranges from real projects, not best cases — and the proposal names the dates for yours.

Almost always one of three things: scope added mid-build without adjusting the plan, waiting on content or third-party access, or a decision that needs someone who is not in the room. We name a single decision-maker at kickoff and flag delays the week they happen, not at the end.

Against milestones set out in the proposal, or monthly in advance for retainers and dedicated teams. Invoices are due within fourteen days. Everything is listed — there are no line items you have not already seen and agreed.

From constraints, not preferences: expected load, compliance rules, who maintains it after us, and how fast you need to be live. Where two options are genuinely close we say so and explain the tradeoff instead of picking silently. Our reasoning is set out on the technologies page.

Yes. Work goes to a staging environment you can open at any time, and there are scheduled review points in the plan. You will never first see the product on launch day.

Built in. Site architecture, page speed, structured data and content structure are decided during the build, because retro-fitting them costs more and works less well. Ongoing SEO campaigns are a separate service.

Defects in what we built are fixed free for thirty days after launch. Beyond that, ongoing support is a separate maintenance agreement so you are only paying for it if you want it.

That is the intended outcome. Handover includes documented code, environment setup, deployment instructions and a walkthrough session. We are not interested in being the only people who understand your product.

Yes — updates, security patching, uptime monitoring and small improvements on a monthly agreement. It is optional, and priced separately so you can see exactly what it costs.