When people ask "how much does an app cost?", the honest answer is: it depends entirely on what's in it. Two apps can look similar from the outside and cost wildly different amounts to build, because the complexity lives in the features, not the screens.

Some features are inexpensive because they're well-solved problems with great tooling. Others are expensive because they involve hard algorithmic problems, complex infrastructure, or third-party integrations that require significant setup.

Here's a breakdown of which features drive cost — and why.

High-cost features (add $4,000–$12,000+)

Real-time updates

Real-time updates — live dashboards, collaborative editing, instant messaging — require persistent connections between client and server (WebSockets), careful state management, and infrastructure that handles concurrent connections at scale. This adds $2,000–$5,000 above a standard request-response app, and significantly more if you need real-time collaboration across many simultaneous users.

Route optimisation

Route optimisation is one of the most computationally demanding features in common business apps. Finding the optimal sequence for a fleet of delivery drivers or field service technicians involves NP-hard algorithms. Integration with mapping APIs and real-time traffic data adds further complexity. Budget $2,000–$6,000 for this.

Multi-tenant organisations

Multi-tenancy — where different organisations each have their own isolated data, users, and settings within your platform — requires careful database design, permission scoping at every query, and organisation-level configuration throughout the app. It's not a single feature you add; it's an architectural pattern that affects everything. Add $2,000–$5,000.

Video calling

Video calling requires specialised WebRTC infrastructure, typically via providers like Daily.co or Twilio Video. Building the UI, handling connection states, managing bandwidth, and making it work reliably across device types adds $2,000–$5,000. Recording and transcription add significantly more.

High availability

High availability infrastructure — multi-region deployments, automatic failover, load balancing, zero-downtime deployments — is the right choice for apps where downtime has real business consequences. The setup and ongoing operational requirements push cost up: expect $5,000–$12,000 above a standard deployment.

Medium-cost features (add $1,000–$4,000)

Resource and staff scheduling

Resource and staff scheduling — coordinating multiple staff members, rooms, or equipment with individual availability, booking rules, and conflict detection — has deceptively complex logic underneath a simple-looking interface. Add $2,000–$4,000 on top of a basic booking system.

Custom reports builder

Letting users design their own reports — choosing fields, applying filters, saving layouts — is substantially more complex than building fixed reports. A custom reports builder involves building a mini query system and a flexible rendering layer. Budget $2,000–$5,000.

Enterprise SSO

Enterprise SSO (SAML 2.0 / OIDC integration with Okta, Azure AD, and similar identity providers) is technically complex and requires careful testing with each customer's identity provider. Most business apps don't need it until they're selling to enterprise customers where IT departments mandate it. Budget $2,000–$6,000.

SOC 2 readiness

SOC 2 readiness isn't a single feature — it's a cluster of controls (audit logging, access reviews, encryption, incident response processes) that need to be implemented and documented before an audit. It's expensive because it requires work across many parts of the system. Budget $2,000–$6,000 for the technical implementation alone, before auditor fees.

Custom AI models

Adding a custom AI model — fine-tuned on your domain data, rather than using a general-purpose LLM off the shelf — requires data preparation, training, evaluation, and ongoing model management. This is the right choice when general models produce unreliable results for your use case. Add $2,000–$6,000 and up.

Lower-cost but commonly misunderstood

Some features that feel complex are actually well-solved and reasonably priced:

• Social login (Google, Apple, Facebook) — $1,000–$2,000, not $5,000
• Subscription billing — $1,000–$2,000 via Stripe, not a custom billing engine
• Push notifications — $1,000–$2,000 for standard implementation
• Role-based permissions — $1,000–$2,000 for typical 2–3 role structures

These feel complex because the concepts are unfamiliar, but the tooling is mature and the implementation is straightforward for a developer who's done it before.

What actually drives app cost

The biggest cost drivers aren't individual features — they're the interactions between features and the decisions made about architecture.

Scope creep is the most common cause of cost overruns. Every "small addition" to scope mid-build carries hidden integration cost.

Complex integrations — especially with legacy systems, accounting software, or industry-specific platforms — often cost more than the feature they're supporting.

Unknowns in the data — apps that process real-world data (documents, images, addresses, phone numbers) always hit edge cases that weren't in scope.

Ambiguous requirements — features that aren't fully defined before build often cost 2–3× the estimate once all the edge cases are discovered.

The app cost calculator lets you select features and see rough estimates. Use it as a starting point — then talk to a developer to identify where the real complexity in your specific app will live.

---

See also: Real-time updates costs · Multi-tenant organisations · App cost calculator