What custom software actually costs in India

Custom software in India generally falls between about ₹1 lakh and well over ₹50 lakh, and the honest answer to "what will mine cost" is that nobody can tell you before understanding what the system has to do. Anyone who quotes a firm number in the first call is either selling you a template or planning to revise the figure later.

That is an unsatisfying answer, so this article explains what actually moves the number, and roughly where different kinds of work land.

What actually drives the price

Not the number of screens. Four things, in descending order of impact:

How many distinct audiences the system serves. One kind of user is straightforward. Four — customers, staff, partners, administrators — is not four times the work, but it is close, because each needs its own interface, its own permissions, and its own testing. Every audience you add multiplies the states the system can be in.

Whether money moves through it. Software that handles payments, invoices, commissions or loan balances is a different category of engineering. It needs reconciliation, audit trails, idempotent writes so a retried request cannot charge twice, and tests around every rule. That work is invisible in a demo and it is most of the cost.

How many systems it must talk to. Each integration is a negotiation with something you do not control. A payment gateway, a government API, a supplier feed, an existing ERP — each brings its own failure modes, and the honest cost of an integration is mostly in what happens when the far end is slow, down, or returns something unexpected.

Whether anyone has done it before. Conventional work is cheap because the path is known. Genuinely novel work should be quoted in phases, because the second phase should be priced after the first has taught everyone something.

Notably absent from that list: visual design complexity. It matters for the result, but it rarely dominates the budget.

Roughly where things land

These are the bands we actually scope against, not industry averages:

• Under ₹1 lakh — a marketing site with a handful of pages and an enquiry form. Real design, real performance work, no bespoke functionality.
• ₹1–5 lakh — a substantial marketing site with an admin panel your team runs, or a small internal tool that replaces a spreadsheet for one team.
• ₹5–15 lakh — a real application. One or two user types, an admin back end, a few integrations. Most first-version business platforms sit here.
• ₹15–50 lakh — multi-audience platforms, ERP and CRM systems, anything holding financial records, mobile apps with a serious backend.
• Above ₹50 lakh — multi-portal systems, regulated workflows, platforms replacing several existing tools at once.

A project can move between bands on one requirement. "It should also let our channel partners log in and see their commissions" is a sentence that moves a build from the third band to the fourth.

Why fixed quotes need scope first

We quote fixed prices, and that is precisely why we will not do it before a discovery conversation. A fixed price given without understanding is either padded heavily to cover the unknown — you overpay — or it is optimistic, and the gap reappears later as change requests. Neither is a good way to start.

The sequence that works: a short discovery session establishes what the system does, who uses it and what it integrates with. That produces a written scope. The scope produces a fixed quote. If the scope changes later, that is normal, and it is priced and agreed before the work starts rather than appearing on an invoice.

Questions worth asking any firm you approach

• What happens to the price if we change our minds in week six?
• Who owns the code, the repository and the hosting accounts?
• What is included after launch, and for how long?
• Can you show me what you would build this on, and why that stack?
• What would you tell me not to build?

That last one is the most revealing. A firm that has never talked a client out of a feature is a firm that bills for features.

The cheapest version of this decision

Before commissioning anything, it is worth checking whether an existing product does the job. Accounting, payroll, email marketing, basic e-commerce — these are solved, and buying is almost always cheaper than building. Custom earns its cost when the process is the thing that makes your business different, or when you are paying for a tool and then paying again in workarounds to make it fit.

We tell prospects this regularly, including when it means there is no project. It costs less than delivering the wrong thing and owning it for three years.