How much does a custom app cost?
There is no credible universal price for a custom app. Once the client explains the core user task, existing systems, target market, budget, and timing, Wavesteam converts them into client, administration, API, data, quality, and release work packages. We calculate a range from role effort, explicit purchases, and evidence-based risk. A price offered from the phrase “build an app” is not ready for contract.
The mobile interface is only one part of an operable product. Delivery may also include iOS, Android, administration, backend services, data, push, payments or maps, monitoring, deployment, and store evidence. A single-merchant store and a marketplace with onboarding, inventory reservation, discount allocation, refund disputes, and settlement cannot share a price merely because both are called commerce apps.
| Scope | Lower-complexity case | Cost driver | Evidence for quotation |
|---|---|---|---|
| Users and clients | One role and one mobile client | Customer, merchant, and field-worker clients with distinct native capability | Client list, roles, critical tasks |
| Business rules | Lookup, submission, one-way state | Concurrent inventory, allocation, refund, approval, settlement | State map, rule table, exceptions |
| Integration | One mature standard API | Legacy systems, hardware, two-way synchronization | Samples, sandbox, owner, responsibility |
| Data | New system | Cleanup, migration, master-data alignment, audit | Dictionary, samples, volume |
| Quality | Normal online use | Offline/weak network, background work, high load, accessibility, strict recovery | Performance, security, availability targets |
| Release | One market with client-owned account | Multiple stores, regulated evidence, private deployment, migration | Channels, accounts, acceptance artifacts |
Cross-platform is not automatically cheaper, each extra client does not mechanically double effort, and Bluetooth or AI is not “a few more days.” Shared business state and components may help, while payment, push, background execution, permissions, hardware, and store behaviour still require separate work. An undocumented legacy interface can cost more to integrate than several screens.
When defining budget, scope, and cost assumptions, also compare Why can one app quote cost ten times another? and Can Wavesteam estimate a project before the requirements are complete?; the linked guidance adds context that should be considered in the same decision.
Build a recalculable range
One service estimate is Σ(role days × disclosed role rate) + named purchases + risk allowance. Check product, UX/UI, mobile, backend, testing, DevOps/security, and coordination instead of hiding everything under “development.” Each risk allowance should point to an unverified interface, dataset, or policy.
At idea stage, the responsible output is comparable solution differences, discovery questions, and discovery cost—not a committed total. With roles and a primary flow, Wavesteam can define the first release, an order-of-magnitude range, and principal risks. A prototype, interface samples, and acceptance criteria support work-package effort and bounds. High-risk proofs then establish the contractual baseline and milestones.
Every range states assumptions: included clients and administration, migration exclusions, available sandboxes, supported systems, load, and recovery targets. Maintenance is also separated into baseline defect warranty, new iterations, cloud resources, operations, and subscriptions rather than an automatic percentage of development.
Store submission is real work. Apple's App Review Guidelines cover safety, performance, business, design, and legal matters. Domestic Android channels and overseas markets add their own accounts, privacy material, screenshots, remediation, and coordinated versions. These requirements justify scope but never guarantee approval.
When budget is constrained, shorten the first business loop: fewer roles, branches, channels, bespoke visuals, and non-critical reports. Do not remove monetary and permission tests, backup recovery, monitoring, account ownership, or handover. If configured SaaS covers the process, Wavesteam recommends it; custom investment is stronger when differentiated workflow, hardware integration, or data control creates operational advantage.