What custom software actually costs in India

Almost every enquiry we get asks the same thing eventually, usually near the end and slightly apologetically: what will this cost? The honest answer is that nobody can tell you accurately from a paragraph. But "it depends" is a useless answer, so here is what it actually depends on, and where the numbers usually land.

Realistic ranges

These are ranges we see for work delivered from India to clients worldwide. Treat them as a starting frame, not a quote.

The spread within each row is wider than most people expect, and that spread is the interesting part.

What actually moves the number

Integration surface, not feature count. A system with twenty screens and no integrations is usually cheaper than one with six screens that has to talk to an ERP, a payment provider and a legacy database nobody documented. Every integration is a negotiation with a system you do not control, and integration is where estimates most often break.

Compliance requirements. Building to HIPAA, PCI DSS or ISO 27001 is not a feature you add at the end. It changes architecture, access control, logging, testing and documentation — and it adds a documentation deliverable that is real work. Expect regulated builds to carry a meaningful premium over the same functionality unregulated.

Data quality. This dominates AI and analytics projects specifically. If your data is scattered, inconsistent or has no recorded history, the engineering effort goes into making it usable long before any model is trained. We have seen the data preparation exceed the model work several times over.

Decision latency on your side. This is the cost nobody budgets for. If approvals take two weeks each, a four-month project becomes a six-month project, and you are paying for the calendar.

Existing systems. Building alongside a legacy system you cannot switch off is substantially more expensive than building on a clean slate. It is also usually the right call, because the alternative is a big-bang cutover that fails.

What does not move it as much as people think

Design polish. Good design is not appreciably more expensive than mediocre design once a design system exists. The cost is in deciding what to build, not in making it look considered.

Choice of framework. Arguments about React versus Vue, or Flutter versus React Native, rarely change a project total by more than a few percent. Team familiarity matters far more than the framework.

Feature count, up to a point. The tenth screen costs much less than the first, because the architecture, auth, deployment pipeline and design system already exist.

Why we charge for discovery

We do not produce free fixed quotes from a brief, and we would be sceptical of anyone who does. A number produced without examining your systems is a guess, and guesses become overruns.

Paid discovery produces a specification, an architecture, a risk list and a firm estimate — typically 5 to 10 percent of the eventual project cost. You own that output. You can take it to another supplier, or use it to decide not to build at all. That is the point: it makes the decision genuinely reversible while it is still cheap to reverse.

The question to ask instead

"What will it cost?" is less useful than "what is the smallest version that would tell us whether this is worth building?" That version is nearly always cheaper than what was originally described, and it produces information rather than just software.

Most of our best engagements started with someone asking the second question.

---

If you want a realistic figure for something specific, tell us what you are building. The first conversation is with an engineer, and costs nothing.