If you ask five studios how much a custom web app costs, you will get five different numbers, and all of them might be defensible. Software pricing feels opaque because the same phrase, "a web app," can mean a two-week internal tool or an eighteen-month platform with payments, real-time data, and a mobile companion. The honest answer to how much does a custom web app cost is that it depends on scope, but the factors that move the price are predictable once you know what to look for.
This guide gives you concrete ranges in both USD and INR, explains what actually drives the cost up or down, and walks through the trade-offs between fixed-price and time-and-materials engagements so you can budget with your eyes open.
Realistic price ranges by scope
The cleanest way to estimate is by complexity tier rather than by feature count. Here is how projects tend to group in 2026.
- Simple app or internal tool. A handful of screens, one user role, a database, basic authentication, and a clean UI. Think a booking form, an admin dashboard, or a lightweight CRM. Expect roughly 6,000 to 18,000 USD, or about 5 to 15 lakh INR. Timeline: 4 to 8 weeks.
- Standard product MVP. Multiple user roles, third-party integrations like email or payments, a designed user experience, and some business logic. A marketplace skeleton or a SaaS first version fits here. Expect 18,000 to 55,000 USD, or 15 to 45 lakh INR. Timeline: 2 to 4 months.
- Complex platform. Real-time features, heavy data processing, multiple integrations, strict security or compliance, and a polished experience across devices. Expect 55,000 to 150,000 USD and up, or 45 lakh INR to well over a crore. Timeline: 5 to 12 months.
These ranges assume a competent team building it properly, not a single freelancer cutting corners or a large consultancy padding the bill. The INR figures reflect what an India-based studio like ours can deliver at, which is often why global clients see meaningful savings without sacrificing quality.
What actually drives the cost
Most of the price is labour, so anything that adds hours adds cost. The biggest levers are rarely the ones founders expect.
- Integrations. Each external system you connect to (payment gateways, shipping APIs, accounting tools, CRMs) carries hidden work: authentication, error handling, edge cases, and their inevitable quirks. Three integrations can easily add a month.
- User roles and permissions. An app where everyone sees the same thing is cheap. An app where admins, managers, and customers each see a tailored, secured view is several times more work because every screen multiplies.
- Design fidelity. A functional interface built from a component library is fast. A bespoke, branded experience with custom animations and pixel-level polish takes designers and front-end engineers far longer.
- Real-time and scale. Live updates, chat, notifications, or anything that must handle thousands of concurrent users introduces infrastructure complexity that a simple request-response app avoids entirely.
- Compliance. If you handle health data, payments, or regulated information, expect added cost for security reviews, audit trails, and documentation.
Fixed-price versus time-and-materials
This choice shapes both your budget and your risk, and neither model is universally better.
Fixed-price
You agree on a defined scope and a single number. It works best when requirements are clear and unlikely to change, such as rebuilding a known process or delivering a tightly defined MVP. The advantage is budget certainty. The downside is rigidity: every change becomes a negotiation, and good studios price in a risk buffer because they absorb the overruns. You often pay a premium for that certainty.
Time-and-materials
You pay for actual hours worked, usually billed weekly or monthly against an estimate. It suits evolving products where you expect to learn and adjust as you go. The advantage is flexibility and transparency. The downside is that you carry the budget risk, so it demands trust and active involvement on your side. A capped time-and-materials arrangement, where the studio commits to a not-to-exceed figure, is a sensible middle ground.
For a first build with real unknowns, time-and-materials with a clear weekly cadence usually serves founders better. For a well-understood deliverable, fixed-price removes anxiety.
The ongoing costs people forget
The build is a one-time number. Running the app is forever, and underbudgeting here is the most common mistake we see.
- Hosting and infrastructure. A small app might run on 20 to 100 USD per month. A busy platform with databases, file storage, and background jobs can reach several hundred to a few thousand USD monthly.
- Third-party services. Email delivery, SMS, payment processing fees, error monitoring, and analytics add up. Budget a realistic recurring line for these.
- Maintenance and updates. Dependencies need patching, browsers change, and bugs surface. A common arrangement is a monthly retainer of 10 to 20 percent of the build cost annually for upkeep and small improvements.
- Support and iteration. Real users generate feature requests. The apps that succeed are the ones that keep evolving, so plan for continued development rather than treating launch as the finish line.
A useful rule of thumb: over three years, ongoing costs often match or exceed the original build. Plan accordingly rather than being surprised in month four.
How to get an estimate you can trust
A reliable estimate comes from a real conversation about your goals, not from a number plucked from a price list. When you brief a studio, share what the app must achieve, who uses it, what it integrates with, and what your timeline and budget constraints are. A good partner will push back, suggest a leaner first version, and explain where the cost lives.
At Naazware we build custom web, mobile, and desktop applications for clients in India and around the world, and we are happy to give you a grounded estimate and an honest opinion on scope before you commit a rupee or a dollar. If you are weighing what your project should cost, reach out and we will talk through the trade-offs with you.