Ask five providers what a custom web application costs and you will get five numbers that differ by a factor of ten. None of them are lying. They are answering different questions, because “web application” covers everything from a one-screen internal tool to a platform your customers log into every day. This article gives you the ranges, what moves a project between them, and how to get a number you can put in a budget.
Quick answer: Most custom web applications land between $15,000 and $150,000. A single-workflow internal tool sits near the bottom of that range, a customer-facing platform with integrations and user roles sits toward the top. Plan ongoing costs of 15 to 25 percent of the build per year. Scope drives everything, so ranges only narrow after requirements are written down.
What drives the cost of a custom web application?
Six factors explain most of the variation:
- How many screens and workflows exist. A tool that tracks one process costs a fraction of one that runs five departments.
- User roles and permissions. Every distinct role (admin, staff, customer, vendor) multiplies the states to build and test.
- Each connection to accounting, inventory, payment, or shipping systems is real work, and legacy systems with poor APIs are the expensive kind.
- Data migration. Clean data imports cheaply. Fifteen years of inconsistent spreadsheets does not.
- Design fidelity. An internal tool can use standard components. A customer-facing product needs real design.
- Healthcare data, payment handling, and similar requirements add process and testing.
What are realistic price ranges?
Treat these as 2026 market ranges for US-based teams, and confirm against actual quotes:
- Simple internal tool, one core workflow, few roles, minimal integrations: $15,000 to $40,000.
- Mid-complexity application with several workflows, roles, and two or three integrations: $40,000 to $120,000.
- Large or customer-facing platform with complex logic, many integrations, or compliance needs: $120,000 and up.
For hourly context, US independent developers and small agencies typically bill $75 to $200 per hour. Offshore teams bill a third of that or less, which is a real option with real tradeoffs covered below.
Why do quotes vary so much between providers?
Because scope is being assumed differently. One provider quotes the smallest version that could work, another quotes everything you mentioned on the call, and neither wrote the assumptions down. Rate structure adds to it: a fixed bid includes padding for unknowns, offshore rates change the base math, and some shops quietly plan to make it up in change orders. When quotes differ wildly, the useful move is asking each provider what they assumed was in and out of scope. The differences surface fast.
How do you keep a project on budget?
- Pay for a short discovery phase first. A written spec with screens, roles, and integrations listed turns guessing into estimating.
- Phase the build. Ship the smallest version that replaces the current process, then add from a roadmap.
- Agree on a change process before the project starts, so new ideas get priced instead of absorbed as scope creep.
- Ask for a working demo every week or two. Problems found at week three cost less than problems found at month three.
What ongoing costs should you plan for?
Hosting for a typical business application runs $30 to $300 per month depending on load. Maintenance, meaning updates, monitoring, small fixes, and security patches, budgets sensibly at 15 to 25 percent of the build cost per year. Add any third-party fees the app depends on, such as payment processing, email delivery, or API subscriptions. An application with zero ongoing budget is an application that slowly becomes a liability.
How do you get a real number?
Send us a description of the workflow through the contact form: what the application needs to do, who uses it, and what systems it must talk to. We scope it, and you get a fixed quote with the assumptions written down. If the workflow currently lives in a spreadsheet, our guide on replacing spreadsheet workflows covers how those projects usually start.
Frequently asked questions
Should I expect a fixed bid or hourly billing?
Fixed bids work when scope is defined, which is what discovery produces. Hourly or retainer billing fits evolving work after launch. A common structure is fixed price for the initial build, then a monthly arrangement for improvements.
Can we start smaller than the estimate?
Usually, yes. Most applications have one workflow doing the heavy lifting. Building that slice first cuts the initial cost, gets the tool into use months earlier, and lets real usage steer the rest of the roadmap.
Does AI-assisted development make this cheaper?
It compresses build time on well-specified work, and we use it daily. The savings are real but bounded, because discovery, integration testing, and revision cycles still dominate a project. Be skeptical of quotes claiming AI cuts cost by 90 percent.
Why are offshore quotes a third of the price?
Hourly rates. The tradeoffs are communication overhead, timezone lag, and higher rework risk when specs are loose. Some offshore teams are excellent. The hidden cost is the management effort of finding and directing them, which is why hybrid models are common.
What is discovery and why pay for it?
A short paid scoping phase, typically one to three weeks, that produces a written spec and a fixed quote. It is the cheapest insurance in software: a few thousand dollars to avoid building the wrong thing at fifty thousand.
What happens after launch?
A warranty window for defects, then a maintenance plan covering hosting, updates, and support. Feature work continues from a roadmap at whatever pace the budget sets. You own the code and the accounts regardless of who maintains it.