Guide
How Much Does a Web App or Dashboard Really Cost?
Ask three developers what your booking system, client portal, or admin dashboard will cost and you will get numbers so far apart they seem like different products. They are. "Web app" describes everything from a polished frontend over an existing service to a custom platform with its own backend team. This guide breaks down what actually moves the price, with the real ranges I quote, so you can scope a first version that matches your budget instead of a wish list that matches nobody’s.
Why quotes vary by 100x
A dashboard’s visible screens are the cheap part. The expensive parts are invisible: where the data lives, who is allowed to see what, what happens when two users edit the same thing, how payments reconcile, what the system does when a third-party API fails. One developer quotes the screens; another quotes the system. Neither is lying, they are answering different questions. Your first job is knowing which question you are asking.
The five real cost drivers
- Authentication and roles: "everyone sees the same thing" is cheap; admin/manager/customer permissions with invitations and audit trails is a project of its own
- Data source: connecting to an existing backend or service (like a rental system or LMS) costs far less than designing and building a backend from zero
- Integrations: every external system, payments, WhatsApp, maps, ERP, adds its own error cases, not just an API call
- Workflow complexity: forms that save are simple; multi-step approvals, scheduling conflicts, and real-time updates are not
- Scale of polish: internal tool for five staff vs customer-facing product judged against the apps people use daily
Honest price ranges
Application work here starts from $2,500 for a design-to-launch engagement, with larger platforms scoped custom after discovery. It covers the design and front-end build: the interface in Figma, responsive implementation in React or Next.js, authentication-ready structure, and admin and user flows, connected to your existing backend or API. Backend development, custom APIs, and third-party integrations are scoped separately per project because they range from trivial to being most of the budget. As market context: full custom builds with dedicated backend teams commonly run $10,000–$100,000+. If a quote sounds too good for a "complete custom platform", the backend is usually what is missing from it.
The MVP discipline that saves budgets
Almost every app idea arrives with three products inside it. The version that should be built first is the one answering a single question: can this replace the spreadsheet/WhatsApp-group/paper process it is meant to kill? Phase one is the core workflow with the smallest feature set that real users can adopt. Reporting dashboards, notification systems, and role hierarchies almost always survive being moved to phase two, and phase two is scoped with the knowledge of real usage instead of guesses.
How to cut cost without cutting quality
- Use an existing backend when one fits: platforms like booking engines, LMS systems, or headless CMSs remove the most expensive layer, my Auris Cars and Hackers Academy projects both build on existing systems
- Start with the workflow, not the feature list: one core journey done properly beats six done halfway
- Phase ruthlessly: a working phase one earns the budget for phase two
- Keep ownership: your code, your hosting, your accounts, switching developers later should be possible, not a hostage negotiation
Red flags in cheap and expensive quotes alike
In cheap quotes: no mention of who hosts the backend, "unlimited features", no scoping conversation before the number, and payment 100% upfront. In expensive ones: line items you cannot get explained in plain language, mandatory multi-year maintenance contracts, and platforms only that vendor can maintain. A serious quote for an app, at any price, follows a conversation about your workflow, names what is included AND excluded, and survives the question "what do I own when we finish?".
Frequently asked questions
What is included in an application engagement, and what is not?
Design and frontend: user flows, the interface designed in Figma, responsive React/Next.js implementation, authentication-ready structure, and admin/user flows, typically delivered in 4–8 weeks after discovery. Backend and API development, third-party integrations, and hosting costs are scoped separately per project, stated plainly before you commit.
Do I need a custom backend for my app?
Often no. If a proven system already handles your domain, a booking engine, an LMS, a headless CMS, an ERP with an API, building the right frontend over it costs a fraction of a custom backend and ships months earlier. Custom backends earn their cost when your workflow genuinely does not fit anything existing.
How long does a web app or dashboard take to build?
A frontend over an existing backend: typically 4–8 weeks after scope is confirmed. A full custom platform: usually 3–6 months or more depending on the backend. Discovery, agreeing exactly what phase one contains, is what makes any estimate honest; distrust precise timelines quoted before that conversation.
Is a fixed price or hourly billing better for an app project?
For a scoped phase one, fixed price with milestones protects both sides: you know the cost, the developer is motivated to finish. Hourly fits genuinely open-ended work like ongoing product development. What matters more than the model is a written scope, without one, fixed price just means arguing about what "included" meant.
Can you improve an existing app instead of rebuilding it?
Yes, and it is often the right call. My Auris Cars and Hackers Academy work were exactly this: existing platforms needing UX clarity, reliability fixes, and launch readiness rather than rebuilds. A review of the current product tells you whether targeted fixes or a rebuild is the honest recommendation.
Have an app or dashboard in mind?
Describe the workflow it should handle and I’ll tell you what phase one really needs, what it costs, and what can wait, free, before you commit to anything.