How much does a custom web app cost in India? How we scope it

"How much will it cost?" is the right first question, and "it depends" is a frustrating answer. So here's what it depends on — the factors that actually move the price of a custom web app — and the process we use to turn an idea into a written, fixed quote.

Why nobody can quote from one paragraph

Two briefs can sound identical and differ by a factor of five. "A customer portal where clients can see their orders" might mean a read-only page pulling from a spreadsheet, or a multi-role system with approvals, payments, notifications and an integration with your ERP.

Any agency that quotes a precise number from one paragraph is either padding heavily or planning to renegotiate later. We'd rather spend an hour understanding the work.

The five things that move the price

1. The number of distinct users and roles

Every role — customer, staff, manager, admin — has its own screens, permissions and edge cases. A system with one type of user is dramatically simpler than one with four. Audit trails ("who changed what, and when") add more.

2. Integrations

Payments, WhatsApp or SMS notifications, accounting software, an ERP, a logistics provider, Google sign-in. Each integration is its own small project: documentation to read, a sandbox to test, failure cases to handle. Mature APIs are quicker; older systems without good APIs take longer.

3. Data and reporting

Storing data is easy. Deciding what the owner needs to see on Monday morning is where the work is. Dashboards, exports and scheduled reports are often underestimated — and often what the business values most.

4. Platforms

Web only, or web plus Android and iOS? A responsive web app works on phones, but staff in the field may need a native app with offline support. Adding mobile apps usually increases scope significantly, even with a shared codebase.

5. Design depth

A clean interface on a proven component library is efficient. A fully custom brand experience with bespoke illustrations and motion takes longer. Both are valid; it depends who uses the product and why.

What makes projects cheaper (without making them worse)

• A smaller first release. Launch the workflow that saves the most time, then add to it. Most "must-have" features turn out to be "nice-to-have" once real people use the first version.
• Existing tools where they fit. You don't need custom-built invoicing if your accounting software already does it well — you need a clean integration.
• One decision-maker. Projects slow down, and cost more, when every screen needs a committee.
• Content ready on time. Missing copy and data delay launches more than code does.

How we scope: from enquiry to written quote

This is the process described on our pricing page.

1. You tell us. A form or a WhatsApp message is enough. We reply within 24 hours, usually with a few questions.
2. Discovery call. We learn the goals, the users, the timeline and the constraints. We ask how the work happens today — the spreadsheet, the WhatsApp group, the paper register.
3. Written scope. A short document with the first release's features, what's explicitly out, the milestones and the quote. Readable in ten minutes, not a 60-page specification.
4. Build in milestones. Work is delivered and reviewed milestone by milestone, so you see progress and can adjust early.

Fixed price or time and materials?

For a well-defined first release, we prefer a fixed-scope quote: you know the cost, and we carry the risk of estimating well. For ongoing work after launch — new features, iteration on real usage — a monthly retainer is usually fairer for both sides.

Two briefs, two very different scopes

To make the five factors concrete, here are two briefs that sound alike and scope very differently.

Brief A: "A portal where our dealers can see their orders." One user type (dealers) plus an admin. Orders are read from the existing accounting system once an hour. No payments, no approvals, a simple dashboard and an export. This is a focused first release: a small team, a few weeks, low risk.

Brief B: "A portal where our dealers can place and track orders." Now there are dealers, sales staff, a warehouse team and managers. Orders need approval above a credit limit, stock must be checked in real time, dealers pay online, and WhatsApp updates go out at each stage. Each of those sentences adds roles, integrations and edge cases. It is a much larger project — and it is often the right one, delivered in phases.

The difference isn't the technology. It's the number of decisions the software has to make on someone's behalf. A good scope makes every one of those decisions visible before anyone writes code, so the quote reflects the real work.

What's included in our quotes

So you can compare like with like, our written quotes spell out:

• Discovery and interface design for the screens in scope
• Development, testing on real devices and deployment
• Documentation and a handover walkthrough for your team
• A defined period of post-launch fixes [CONFIRM duration]
• Hosting and third-party costs listed separately, at cost

Questions to ask any agency

• What exactly is included — design, testing, deployment, documentation?
• Who owns the code, the cloud accounts and the domain?
• What happens after launch: bug fixes, hosting, support?
• How are changes to the scope priced?
• Can I speak to the people who will build it?

So, how much?

The honest answer is a range that narrows quickly once we understand the five factors above. One conversation usually gets us from "no idea" to a confident estimate; a written scope turns that into a fixed number.

Start with a message — tell us what the software needs to do and who will use it. We'll reply within 24 hours.