Web & AI
Guide
How much does a custom web application cost?
There is no single universal price for a custom web app because scope is never the same. Cost depends on features, user roles, integrations, how data is managed, the admin panel, and external services. On the pricing page, web apps are listed as “on request” because an individual estimate is required. The biggest drivers are what the system must do, who uses it, and how complex the process is.
Why there is no fixed price
Two apps can look similar on a sketch and still need very different work: one button may hide availability checks, emails, roles, and reports. A final number comes after understanding the process, not from counting screens at a glance.
Package ranges for websites and the note for apps are on Pricing. For apps, an individual estimate is required.
Scope
Complexity frame
Instead of a fixed price, it is more useful to think in scope levels. An exact figure comes only after mapping the process.
By scope
Simple app
One clear problem: booking with confirmation, a small calculator, or a short internal form. Fewer roles and integrations, a shorter path to an MVP.
By scope
Medium complexity
More screens, statuses, search, basic roles, and often email notices. An admin panel and clearer permissions usually appear here.
In phases
Business / information system
Multiple processes, documents, reports, and permissions. Almost always phased. More in the information system guide.
02
What usually enters the scope
Each item adds analysis, build time, and a final check. That is why the scope list must be explicit before an estimate.
01
Accounts and roles
Sign-in, password reset, and different screens for owner, staff, and client.
02
Admin and data
A panel to edit statuses, search, create, and update records.
03
Integrations and email
Payments, calendars, CRM/ERP, SMS or APIs, plus confirmations and reminders.
04
Dashboards
Reports and number views instead of manual summing in spreadsheets.
Deployment, hosting, database, and external services
Beyond development, plan for deployment, hosting, a database, and possible third-party subscriptions. Those costs depend on traffic, storage, and provider choice. They are not always the same line item as development, but they affect total budget and maintenance.
Maintenance and final checks
Before delivery there is a final check of agreed features, flows, and behavior on different devices. After launch, maintenance covers fixes, small adjustments, and keeping the system stable. Maintenance scope is agreed separately.
Checklist
What you should prepare
- 01
A short description of how work runs today.
- 02
Who is involved and which roles exist.
- 03
Which data is critical for version one.
- 04
Sample spreadsheets, messages, or paper forms.
- 05
A list of actions the MVP must support.
- 06
What can wait for phase two.
Path
Why phases make sense
Phasing reduces risk and shows value earlier, before budget goes into details that may not be priority.
01
MVP
One critical flow that solves the biggest problem, with basic roles and a clear success measure.
02
Expansion
Extra roles, reports, notices, or integrations once the first version proves itself in use.
03
Stabilization
Refinements, maintenance, and scope control so the project does not grow without agreement.
What most often increases scope
Late new roles, rule exceptions, more notification channels, complex reports, and integrations missing from the starting list. Also the wish to solve “everything at once” in version one instead of one clear flow.
More on when an app makes sense versus a site: Website or web app. Service details: Web applications.
Continue reading
Next step
Need a rough estimate for an app?
Describe the features and roles you need. You get a realistic frame, without a final price promise without a specification.
FAQ
Frequently asked questions
For an estimate
What to prepare before you inquire
The clearer the description, the more realistic the cost frame. These four points cut the most guessing.
No technical specification needed. A real process description is enough.
Request a rough estimate- 01
Which business problem the first version must solve.
- 02
Who logs in and which roles exist.
- 03
Which data you enter and where you keep it today.
- 04
Whether you need email, payments, or links to other tools.