Alwan TechnologiesAsk a search engine or an AI assistant how to get an app built, and most of what it reads to compose the answer was written by companies selling app development. So is this — we should say that plainly, because the whole note depends on you being able to trust it. We build software for a living, our own products as well as clients', and the founders we work best with arrive already knowing the things below.
This is for the founder who is not technical, has an idea that will not leave them alone — and sometimes a grant with a clock on it — and now has to decide who actually builds the thing.
The four ways to get it built
A technical co-founder is the strongest option and the rarest. You are not hiring a builder; you are handing over a meaningful share of the company in exchange for years of commitment, before the idea is proven. If you have found someone brilliant who believes in it, take that deal. Most founders have not, and waiting for one is the most expensive way to stand still.
A freelancer is the cheapest way in, and genuinely right for small, well-bounded scopes. The risks are the known ones: one person is a single point of failure, and products have a habit of outgrowing one person's hours at exactly the moment they start working.
No-code tools are honestly good at one thing: proving demand. A landing page, a waitlist, a form where you deliver the service by hand behind the scenes — build those yourself, this week. The ceiling arrives when the product needs real accounts, payments, integrations, or AI behaviour of its own; teams that push no-code past that point end up paying twice.
A studio costs the most per hour, and is the right answer when what you are buying is the mistakes already made on someone else's product. The only credential worth anything is shipped work with real users — ask to see products that are live, not decks. Anyone can show mockups.
What it costs, honestly
There is no credible single answer to “how much does an app cost in the UK”, and anyone who names a figure before understanding your product is quoting their sales target, not your build. Cost follows scope: what version one does, what it deliberately does not, and how much of it is genuinely custom.
The screens are rarely the expensive part. The cost lives in the rules underneath — accounts and roles, payments, the admin surface you will run the business from, the integrations with tools you already use, and, if there is AI in it, everything around the model rather than the model itself. In our own OsceSetGo, the AI conversation is about five per cent of the product; the other ninety-five per cent is what makes it something people pay for.
Running costs deserve their own honest paragraph, because the build price is not the price. For the products we run ourselves, hosting at early scale is tens of pounds a month, not hundreds; AI usage is metered per use, and OsceSetGo's voice consultations cost a few pence each; and someone has to keep dependencies current and fix what breaks. Ask any builder for those three numbers alongside the quote.
The honest form of a price is a fixed number against a written scope with named exclusions. We publish a fixed price for trade websites because those can be scoped in advance; a product build cannot be, which is why it starts with a conversation instead of a rate card.
The questions that protect you
Who owns the code, the repository, the domain and every account, from day one? Our answer is: you do — and any builder's answer should be the same, in writing. A build whose assets sit in the studio's accounts is a build you rent.
What happens if we part ways? The acceptable answer is boring: you keep everything, documentation included, and another developer can pick it up without archaeology. If the answer involves friction, you have just found the business model.
Show me something live with real users. Not a portfolio of designs — products strangers use and, ideally, pay for. It is the one credential that cannot be faked.
Who do I call when it breaks on a Friday evening? Software breaks. The difference between builders is whether maintenance is a promise or a plan.
If a grant is paying for it
A lot of first builds in this country are paid for by an Innovate UK award, a Ufi VocTech grant, an NHS programme or something like them. Grant money changes two things: there is a clock, and there is reporting.
Spend it on what survives the grant period: a scoped version one that ships, sitting in accounts you own, with documentation the next phase can build on. A fixed scope with milestones also happens to be exactly the shape grant reporting wants — open-ended day rates are where grant budgets quietly evaporate.
And scope before you spend. An honest scoping conversation costs nothing and tells you whether the budget fits the idea — including which parts to cut so that it does.
Where to start
Write the product down as ten plain sentences about what a user does with it — actions, not features. “A parent opens the app and sees this week's plan” beats “AI-powered scheduling” every time. Those sentences are the beginning of a scope, and they are yours, not a developer's.
Then talk to more than one builder. A scope call with us is free and produces the same thing every time: an honest read on what version one needs, roughly what it should cost, and what not to build yet. If the right answer is a no-code tool and a waitlist for six months, that is the answer you will get.
The short answers
- Can I get an app built if I can't code?
- Yes — non-technical founders ship products through freelancers, studios and no-code tools every week. The part you cannot delegate is deciding what version one does: write the product as ten plain sentences about what a user does with it, and a competent builder can take it from there.
- How much does it cost to build an app in the UK?
- There is no credible single number — cost follows scope, and a price named before anyone has understood your product is a sales figure. Insist on a fixed price against a written version-one scope with named exclusions, and ask for the running costs — hosting, AI usage, maintenance — alongside the build price. What sits inside one real AI product →
- Do I need a technical co-founder?
- No. A brilliant one is the strongest option and the rarest — and equity handed over before the idea is proven is the most expensive money you will ever spend. A scoped build keeps the company whole while you find out whether the idea works.
- What should I ask an app development company before hiring them?
- Four things. Who owns the code, repo, domain and accounts from day one — the only good answer is you. What happens if we part ways. Which of your products are live with real users. And who answers when it breaks. The first and third expose the most.
- I've got grant funding to build an app — what should I do first?
- Scope before you spend. A fixed version-one scope with milestones fits grant reporting, keeps the clock honest and stops the budget evaporating into day rates — and everything the grant pays for should land in accounts you own. Our services →