The short answer
- Cost follows the number of user types, rules and integrations more than the number of screens.
- Offline working, payments and compliance each add real work, and are often worth it.
- A fixed-price first release with a tight scope is the best way to control cost.
Screens are the wrong unit
People often estimate an app by counting screens. Screens are the visible part. The cost sits underneath: who can do what, what the rules are, what has to talk to what, and what happens when something goes wrong.
What moves the price
Types of user
An app used only by your office staff is one thing. Add customers, subcontractors and an admin who can see everything, and each needs its own permissions, screens and notifications.
Rules
Tax treatments, approval steps, pricing rules and deadlines are where the real work is. They need to be written down, built and tested against real examples from your business.
Integrations
Every connection to another system, such as accounting software, a payment provider or a supplier's API, has to handle failures, retries and changes on the other side.
Platforms
A web app, an iPhone app and an Android app are three front ends. Sharing one backend and one set of rules stops that from tripling the cost, but it is still more work than one.
Offline working
An app that must work with no signal needs a database on the phone, a sync process and rules for conflicts. For people on sites or in the field it is essential. For an office tool it usually isn't.
Data you already have
Moving years of spreadsheets, an old system or paper records into the new one is often underestimated. Messy data takes time to clean.
What it costs to keep running
After launch there is hosting, monitoring, backups, security updates, app store releases and the occasional fix when another service changes. Budget for running costs from the start.
How to keep cost under control
- Scope a first release around the one job that costs you most today.
- Fix the price for that release from a written scope.
- See it every two weeks, so changes happen early, when they are cheap.
- Leave the nice-to-haves for the second release, when real use shows which ones matter.