When someone asks what an app will cost, the honest first answer is: it depends on a handful of things we can name. Knowing them lets you make trade-offs early, when they are cheap.
The number of distinct user types
An app for customers only is simpler than one for customers, staff and managers, because each group needs its own screens, permissions and testing. Every extra role adds work in design, build and support.
Integrations
Payments, SMS or WhatsApp messages, maps, accounting software and existing databases each have their own rules and failure cases. An integration with a well-documented service is quick. One with a legacy system that has no documentation is not.
What has to work offline or at scale
An app that must keep working with a weak signal, or serve thousands of people at the same moment, needs more careful architecture than one used by a small team in an office.
How clear the scope is
The biggest cost driver is change. A clear first version, with a short list of what is not included yet, costs less than a wide scope that moves every week.
- List the user types and what each one must be able to do.
- List the outside services the app must talk to.
- Decide what can wait for version two.
Bring that list to a first conversation and you will get a much more accurate range, whoever you talk to. You can also describe your idea to the project estimator on this site and get a draft plan in seconds.
