Ask five vendors to quote "a web application" and you will get numbers from $7.5k to $80k. They are not lying. A dashboard over one database for ten employees is a different product from a customer portal with payments, roles, and a mobile-responsive UI that has to survive 10,000 daily users. This guide is the web-app slice of our custom software cost hub: four price tiers, the eight variables that move a quote, a line-item $20k budget, and when to customize a product core instead of building from scratch. For SaaS-specific stages see our SaaS development cost guide; for a first launch see MVP cost in 2026.
The four web-app price tiers in 2026
Internal tool or operations dashboard: $7.5k–$15k, 4–8 weeks
One primary user type, one or two data sources, role-based access, and a UI that replaces a spreadsheet or an aging Access database. Typical examples: an operations dashboard, an inventory tracker, a simple CRM for a sales team, a reporting screen over existing data. This is the floor of our web application development work. You own the code and the data. If the workflow is already close to a known product, we often start from a core and customize — which is how a $7.5k tool ships in four weeks instead of ten.
Customer or partner portal: $10k–$30k, 6–12 weeks
Two or more user types (admin plus customers, vendors, or patients), authentication, file upload, notifications, and at least one integration — Stripe, a payment processor, a CRM, or an existing ERP. This is the most common web-app engagement we see from California businesses: a booking portal, a vendor portal, a patient intake flow, or a client dashboard that sits in front of work already happening offline.
Multi-tenant SaaS front-end: $20k–$75k+, 10–20 weeks
Tenancy, billing, permissions that differ per company, an admin console, and a public marketing site. The front-end is only part of the bill — tenancy model, data isolation, and billing integrations usually decide whether you land at $20k or $60k. Our SaaS development page covers the product side; this guide is about the web application you actually sit in front of users.
Regulated or high-scale web apps: from $15k, often $25k–$80k
HIPAA, WCAG 2.1 AA as a contractual requirement, SSO into an enterprise IdP, or 10,000+ daily users with real-time updates. Compliance and scale add design, testing, and documentation more than they add screens. HIPAA-compliant builds start at $7.5k for a first automation and typically $15k–$45k for a patient-facing web app — see HIPAA-compliant AI when the product also talks to a model.
The cheapest web app is the one that reuses a working core. The most expensive is the one that looks simple on a slide and has six integrations nobody mentioned in the brief.
— Rocket Systems Team
What actually drives the cost
- User types and permissions: one role is cheap. Each additional role with a different view of the data adds screens, tests, and edge cases — typically $1.5k–$4k per distinct role after the first two.
- Integrations: a documented REST API is $1.5k–$4k. A legacy SOAP service, a scraped portal, or a desktop database with no API is $4k–$12k because we have to build the API first.
- Workflows vs pages: a marketing site is pages. A web app is workflows — create, review, approve, export, notify. Count the workflows, not the mockups.
- Data migration: 500 clean rows is a day. 50,000 messy rows with duplicates and missing keys is $2k–$8k and is the line item most briefs forget.
- Design: we ship a working UI as part of the build. A custom design system, illustration set, or brand-heavy marketing surface on top of the app is extra.
- Accessibility: WCAG 2.1 AA is the default on public-sector and healthcare work. A focused audit and remediation on an existing app starts at $1.5k.
- Realtime and files: live updates, large uploads, and media processing add infrastructure and testing. Budget $2k–$6k when they are core, not decoration.
- Who writes the code: a senior team at $15–$50/hour via web developer staff augmentation is cheaper than a $150/hour local agency for the same seniority. The quote should say which.
A $20k web-app budget, itemized
Take a customer portal for a regional services company: login, two roles (staff and customer), job status, document upload, email notifications, and a Stripe invoice. A realistic 2026 split:
- Discovery and information architecture: $1.5k — user types, workflows, and a written scope.
- Auth, roles, and core screens: $8k — the product itself.
- Stripe + email + one CRM sync: $4k.
- Data migration and admin tools: $3k.
- QA, accessibility pass, and launch: $2.5k.
- Buffer for the thing nobody mentioned: $1k.
That is a 8–12 week engagement with a small senior team. If the same company already has engineers, we can embed one full-stack developer from $15/hour and a tech lead part-time, and the same portal lands cheaper over a longer calendar — useful when the workflow is still changing week to week.
Build vs customize vs no-code
Three routes. No-code (Retool, Bubble, Softr) is the right first move for an internal tool used by five people; it fails when you need custom permissions, a customer-facing brand, or an integration the platform does not have. Customizing a product core — our Inflow CRM from $6k, Marketplace Engine from $7.5k, or B2B Job Marketplace — is the fastest path when your workflow is 70% of a known product. A from-scratch build is for the remaining 30%: the workflow no product covers, the integration nobody has a connector for, or the regulated surface that has to be yours. Most quotes we write in 2026 are a hybrid: a core plus custom screens, which is why a $20k portal often ships in eight weeks instead of sixteen.
Timeline and hidden costs
Internal tools go live in 4–8 weeks. Portals take 6–12. Multi-tenant products take 10–20, and the long pole is usually tenancy and billing, not the UI. Hidden costs that show up after launch: hosting ($30–$200/month for most SMB apps), observability, a staging environment, and the first three change requests. Budget 15–20% of the build for the first six months of changes, or keep an embedded engineer on a month-to-month staff-augmentation contract so those changes do not become a new project.
What software costs in California cities
Local agency rates in Los Angeles, San Diego, San Jose, and Orange County typically run $120–$200/hour. Our model — California management, Yerevan engineering hub — is $15–$50/hour for the same seniority, which is why the starting prices above are half of a fully local quote. If you are comparing vendors by city, start with the list: San Diego, San Jose, Orange County, or Sacramento IT companies — then come back to this page for the number that belongs in the proposal.
Internal tools from $7.5k · portals from $10k · written fixed quote within 48 hours of a free discovery call.
Get a web-app quoteFrequently asked questions
How much does web application development cost in 2026?
Internal tools and dashboards typically run $7.5k–$15k over 4–8 weeks. Customer or partner portals with auth, two roles, and one or two integrations run $10k–$30k over 6–12 weeks. Multi-tenant SaaS front-ends run $20k–$75k+ over 10–20 weeks. Regulated or high-scale apps start around $15k and often land at $25k–$80k. Staff-augmentation rates for the same work start at $15/hour.
What is the difference between a website and a web application?
A website is mostly pages: content, forms, and a CMS. A web application is workflows: users log in, create and change records, trigger notifications, and integrate with other systems. Quotes that treat a portal like a marketing site are the ones that blow up at week six.
Is it cheaper to customize a product than to build a web app from scratch?
When your workflow is close to a known product, yes. Customizing Inflow CRM (from $6k) or Marketplace Engine (from $7.5k) typically cuts delivery time and cost roughly in half versus a from-scratch build of the same scope. Build from scratch when the workflow, integration, or compliance requirement is the product.
How long does it take to build a web application?
A focused internal tool: 4–8 weeks. A customer portal: 6–12 weeks. A multi-tenant SaaS front-end: 10–20 weeks. Discovery and a written scope happen in the first week; a fixed quote follows a free 30-minute call.
Can we start with a no-code tool and rebuild later?
Yes for internal tools with a handful of users. Rebuild when you have paying customers, regulated data, or an integration the no-code platform cannot do. Using the prototype as the specification is cheaper than it used to be — see our guide on vibe coding versus professional development.