Custom software development cost in India: what drives the price

Custom software in India is priced by what has to be built, not by how many hours a developer sits at a desk. The four things that move the number most are scope (how many screens and workflows), integrations (what the software must talk to), users (how many, in how many roles, from how many places) and compliance (what regulators and auditors will ask for). A serious vendor turns those four into a fixed price after a short discovery, and that is the number you should compare.

What are the four cost drivers?

Every quote we have written in the last few years comes down to the same four inputs. If a vendor cannot explain their price in these terms, the price is a guess.

Compliance is the driver owners underestimate. The Digital Personal Data Protection Act applies to any business that holds personal data, and healthcare, diagnostics and invoicing each add rules of their own.

Why does scope cost more than screens?

Owners often count screens and expect the price to follow. It does not. A screen that shows a list is cheap. A workflow that moves a record through five states with approvals, reversals and a printout is not, and it may live on one screen. The expensive part is the rules: what happens when a payment bounces, when a doctor edits a signed note, when a branch closes for the month. Discovery exists to find those rules before anyone writes code, because each one found later is a change request.

The data model is the other hidden driver. If your business has a concept the software does not, such as a 'party' that is both customer and supplier, the model has to be designed for it. Getting the model right is slow at the start and cheap forever after. Getting it wrong is the opposite.

Why do integrations move the price so much?

Integration is where projects slip, so it is where honest quotes carry the most margin. Three questions decide the cost. Is there a documented API, or will the connector have to read a database or a file export? Does the other side need certification, as the ABDM milestones and GST e-invoicing through the Invoice Registration Portal do? Does data have to flow both ways, as it does for a bidirectional analyser interface? Each yes adds days of work and, more importantly, days of waiting on a third party. A WhatsApp integration through the Cloud API is well documented, but template approval and business verification still sit on Meta's clock, not ours.

How is a fixed-price quote built?

A fixed price is not a guess with a margin on top. It is built from a written scope, and the writing is most of the work. This is the sequence we follow on custom projects.

1. Discovery: a week with your team, at your site where possible. We watch the work happen and list what is slow, what is retyped and what is on paper.
2. Screen list and data model: every screen named, every field on it, every table and relationship drawn. You sign this before code starts.
3. Integration list: each external system, the direction of data, who owns the credentials, and who is responsible when the other side is down.
4. Compliance list: what must be logged, what must be consented, what must be exportable, and where data must sit.
5. Estimate by module: each module gets days for build, test and fixes. Integrations get extra days for waiting on third parties.
6. One number, one schedule: the price, the milestones and what is not included, all in writing. Changes after signing are priced as changes.

Why do hourly rates mislead?

An hourly rate answers the wrong question. It tells you what one hour costs and nothing about how many hours the work will take, which is the only thing that decides the bill. A cheaper hour from a team that has not built a GST connector before will cost more than a dearer hour from a team that has done it four times.

Rates are fine for one situation: open-ended work where nobody can define the scope, such as a research spike or an ongoing retainer. For a business system with a known workflow, ask for a fixed price and judge the vendor on how well they wrote the scope. We cover the choice in detail in fixed price versus time and material.

What is not in the build price?

Two lines are missing from most quotes, and they are the ones that hurt later. The first is running cost: hosting, backups, monitoring, SSL, SMS and WhatsApp message charges, and the annual maintenance that keeps the thing patched. The second is migration and training, which is real work with real days. Ask for both as separate lines so the build price is comparable and the running price is known before you sign.

Frequently asked questions

Can I get a price without a discovery phase?

You can get a range, and it will be wide. A useful fixed price needs the screen list, data model and integration list written down first, because those are what the number is built from. A week of discovery is cheap next to a quote that was wrong by half. Treat any exact number given on a phone call as a guess.

Does compliance really change the cost that much?

It changes the shape of the build more than the size. Audit trails, consent records and exports have to be designed into the data model from the start. Adding them later means touching every table. If your software will hold health, financial or personal data, say so at discovery and it will be quoted correctly the first time.

What is the cheapest way to lower the price?

Cut scope, not quality. Ship the workflow that hurts most first, with the data model built to take the rest later. A good vendor will show you which modules can wait. Integrations that nobody will use in year one can be designed for and built in year two. Lowering the hourly rate saves nothing if the hours double.