Why nobody can price "an app" honestly
Ask five development companies what an app costs and you will get five very different numbers, because the question hides the only thing that matters: scope. A login screen, a payment flow and ten report screens are each "features", but they differ by days of design, development and testing. Any quote given before your workflows, users and integrations are understood is a guess dressed up as a price.
The useful question is not "what does software cost?" but "what are we building, for whom, and what has to connect to it?" Once those are written down, a fixed-price proposal becomes possible — and comparable between vendors.
The five things that actually drive cost
Scope and screens: every distinct screen, role and workflow adds design and development time. A tool used by five staff in one office is a different build from a platform serving customers in three countries.
Integrations: connecting to payment gateways, accounting tools, CRMs, marketplaces or third-party APIs is often where estimates quietly double. Each integration needs mapping, error handling and testing against a system you do not control.
Users and permissions: roles, approvals and audit trails multiply complexity. "Only admins can see this" is simple to say and real work to build safely.
Data: migrating existing records from spreadsheets or an old system, and reporting on that data, takes its own planned stage.
Platforms: a web application is one build. Adding native-quality iOS and Android apps, offline behaviour or a desktop component adds further builds that each need testing and maintenance.
Budget ranges we plan against
These are the ranges we use when scoping proposals. They are planning guides, not market statistics, and your written proposal is the number that counts.
Under $1,000 usually covers maintenance, small fixes and minor features on an existing website or application rather than a new build. Between $1,000 and $5,000 fits small tools, focused website work and single-workflow utilities. Between $5,000 and $15,000 is where a focused web application, an internal CRM or a first product release typically lands. Between $15,000 and $50,000 covers a SaaS product or business system with multiple roles, integrations and reporting. Above $50,000 usually means multi-platform products or larger platforms phased over several approved stages.
If a quote lands far below the range your scope implies, ask what has been left out — testing, migration, documentation and post-launch support are the usual silent omissions.
Build, buy, or both?
Custom software is not always the right answer. If an established off-the-shelf product covers your process without forcing your team into workarounds, buying is usually cheaper and faster. Custom earns its cost when your workflow is the business advantage, when several disconnected tools need to become one system, or when per-seat subscription fees and forced processes cost more than owning the software.
A hybrid is common: buy commodity pieces (payments, email delivery, accounting) and build the workflow that makes your business different. During discovery we will tell you plainly if buying serves you better — it costs us a project, but it is the honest answer.
How to get a quote you can compare
Write down the users, the three workflows that matter most, what the software must connect to, and what "done" looks like for the first release. Share that with each vendor and ask for four things: a fixed price for the written scope, a timeline with review stages, what happens when scope changes, and what support costs after launch.
Then compare the assumptions, not just the totals. The cheapest comparable quote is the one whose assumptions you have actually read.