You’ve got an app in mind, or a problem you think an app would fix. You want to know what it’ll cost before you commit. Every page you’ve read says “it depends”. It does, but that isn’t an answer. Here’s what it actually depends on, so you can shape the project yourself and walk into any conversation knowing what you’re paying for.
Why won’t anyone just give me a price?
Because an app’s price follows its scope, and the scope usually isn’t settled when you first ask. Two apps that look the same on a phone can be very different underneath. One shows a menu and takes a booking. The other handles payments, remembers every customer, syncs with your till and sends reminders. Anyone who quotes a firm figure before knowing which one you need is guessing. I don’t publish prices. I agree them after a conversation, once I know what the thing has to do.
What makes an app cost more or less?
The amount of work behind the screens decides most of it. These are the things that move it:
| Factor | Usually less work | Usually more work |
|---|---|---|
| Platforms | One: iPhone, Android or web | Several at once |
| Logins | None, or one simple login | Different roles for staff, admin and customers |
| Connections | Stands alone | Talks to bookings, payments, your CRM or till |
| Data | Little or nothing stored | Personal or health records, history per person |
| Content | Fixed screens | Content your team edits through an admin panel |
| Design | Clean and standard | Custom animation and bespoke interactions |
| After launch | Occasional updates | Regular new features and ongoing support |
The connections row is the one people underestimate. When I built Zeena, the voice and the web page were the parts you see. Underneath sit a workflow engine with 43 automatic steps, a database that remembers every person, and her own server. That’s where the work lives, and it’s the same for most business apps.
If your app will hold personal or health data, check your obligations with the ICO, and with your regulator if you have one, before you scope it. It shapes how the data is stored and who can see it.
Do I actually need an app, or would a website do?
Often a well-built website does the job, and it’s worth asking that first. A website needs no download, works on every phone and can be found through search engines. An app earns its place when people use it again and again, need it on the move, or need things a phone does well, like notifications.
FreshPlate, my own iPhone app, has a website alongside it with a free food and medication checker and guides cited to NHS and NICE. In the 30 days to 4 October 2026, 2,057 people visited that website, most from search engines. The website is how people find it. Plenty of businesses need that part before an app.
How do I scope it so I only pay for what matters?
Start with the one job the app must do for one type of person, and build that first. Everything else can wait until you know it’s wanted. You can do this today:
- Write one sentence: who uses it and what they get done.
- List every feature you want, then mark each one “launch” or “later”. Be strict.
- Pick one platform to start, based on what your customers actually use.
- Write down every system it must talk to: bookings, payments, email, accounts.
- Note what data it keeps and who needs to see it.
- Decide who looks after it once it’s live.
That single page is worth more than any brief template. It lets you compare quotes like for like, and it stops you paying for features nobody asked for.
Why does seeing it working early matter so much?
Because the earlier you see the real thing, the cheaper it is to change. A wrong assumption caught in the first few days costs a conversation. The same assumption found after launch means reworking everything built on top of it. Specifications and mock-ups hide problems that become obvious the moment you tap through a working screen.
That’s why, once a build starts with me, you see it working within two working days, and you keep seeing it as it grows. I work the same way on my own projects. FreshPlate has been through over fifty TestFlight builds as it gets ready for the App Store.
What should I ask anyone who quotes for my app?
Ask questions that show what’s in the price and what isn’t:
- Who builds each part: design, app, server and database?
- When will I first see something working on my own phone?
- What happens after launch: updates, fixes, app store changes?
- Who owns the code and the data?
- What have you left out that I might assume is included?
I build every layer myself, so one person answers all of those. I’m based in Wirral and work with businesses across Liverpool and the rest of the UK.
If you want it done for you
Tell me what you need the app to do. If a website is the right place to start, I’ll design a free preview of your new homepage for your business, with a short video of me walking you through it, within two working days.

