App Development

A spreadsheet is doing a job that several people now depend on

Your process works but only because one person remembers the exceptions

You need customers or staff to do something on a phone and there is currently no way to

Scope that grows quietly

Most overruns are not engineering failures, they are additions nobody wrote down. Each phase has a fixed price and a written scope, and a new idea becomes a new phase rather than a delay with no explanation.

Built for the demo, not the Tuesday

Software is judged on the dull week, not the launch. We build with the awkward cases in from the start, because the exception your team handles by hand is usually the reason the old process was slow.

A launch with no handover

An application nobody but the builder understands is a liability. Handover is documentation, credentials, a runbook and a recorded walkthrough, so another developer could pick it up without calling us.

Discovery first, paid, producing the written scope per phase, the fixed price per phase and the list of what is not included. Then a working prototype in the first week, so the shape of the thing is in your hands before the bulk of the budget is spent. Weekly demos against real data through the build. Then the part teams doing it for the first time underestimate: store submission for iOS and Android, which is its own small project with its own review cycle, and which we handle because we have shipped our own apps through it. Handover is documentation, credentials, a runbook and a recorded walkthrough, plus a training session for the people who will use it daily.

A new idea mid-build becomes a new phase with its own price, not a quiet addition. That is what keeps a fixed price fixed.

Five things, in roughly this order. How many kinds of user there are, because three user types each seeing different data with different permissions is more than three times the work of one. Whether it must talk to systems you already own, because integration is usually the largest line and the most underestimated. Whether it needs to be a real mobile application rather than a website, because store submission and offline behaviour are their own work. Whether anything runs unattended or is time critical, because background work that must not fail quietly costs more than a button somebody presses. And how much of the process is already written down, because undocumented processes are discovered during the build, and discovery is the expensive way to find requirements.

Published UK ranges from our custom software cost guide, September 2026. Each phase is quoted separately with a written scope.

The code, the repositories, the hosting and the provider accounts are in your name from day one, not transferred at the end. At go-live you hold documentation, credentials, a runbook and a recorded walkthrough, so another developer could pick the system up without us. A monthly support line starts after launch at a price agreed at go-live, and because you hold everything you can stop paying it and keep the software. Our guide on your data when a supplier builds your software sets out what to ask any supplier for; we simply do all of it by default.

We build and operate two products of our own, on web, iOS and Android: a recruitment operations platform in daily use across a national recruitment network, and an AI career platform with consumer and institutional customers. They are the same stack, the same practices and the same people you would be working with, which is why the timelines above are real rather than aspirational. The case studies describe what each one does and the commercial difference it made.

How much does it cost to build a business app in the UK?

Augustova quotes £8,000 to £30,000 depending on surface area, fixed per phase so the budget does not drift. A single process automation sits at the lower end and a multi user platform with mobile apps at the upper end.

Do you build for web and mobile?

Both. We run our own products on web, iOS and Android, and we handle the App Store and Google Play submission process, which is usually the part that surprises teams doing it for the first time.

What happens after launch?

A handover pack of documentation, credentials, a runbook and a recorded walkthrough, plus a training session for the people who will use it daily. A monthly support arrangement starts at go live and is agreed in the original document rather than negotiated afterwards.

Do you work fixed price or day rate?

Fixed price. A day rate pays a supplier for being slow and penalises them for being fast, which is backwards. Fixed price forces the scope conversation before the money is committed, and the risk of being wrong sits with us.