Custom software pricing in India: the build, and everything after

Custom software quotes in India vary so widely that people reasonably assume nobody knows what they are doing. The same brief can come back under a lakh from one team and over ten lakh from another, and both can be honest. They are pricing different things, and neither quote says which.

So here are the ranges, what sits inside each one, and the part of the cost that arrives after the invoice is paid.

The ranges you will actually be quoted

Under ₹1,00,000. A single tool with one job: a form that feeds a sheet and sends a notification, a small calculator, a script that moves data between two systems every night. Usually one person, a few weeks. This is often the right purchase — plenty of businesses need exactly one small thing — as long as nobody pretends it is a system.

₹1,50,000 to ₹5,00,000. A focused business application. Logins, two or three kinds of user, a handful of screens, one or two integrations. A CRM shaped around how you sell, a portal where customers check the status of an order, an internal dashboard that replaces a monthly spreadsheet. Most small businesses that genuinely need custom software need something in this band.

₹5,00,000 to ₹25,00,000. Several connected modules, several kinds of user, a mobile app alongside the web, reporting that other people depend on. At this size there is a real project to manage, and the quality of that management matters more than the code.

Beyond that. You are building a product. It needs a team that stays rather than a project that ends, and it should be budgeted by the year, not by the build.

Underneath, most quotes are a count of developer-months. An experienced developer at an Indian studio is typically billed at somewhere between one and two and a half lakh a month, so a quote is a guess at how many months, plus design, testing, and whatever the team has learned to add for surprises.

What moves a project up the range

User roles. Every kind of user who sees something different — admin, staff, manager, customer, dealer — multiplies the screens, the permissions and the testing. Two roles is simple. Five is a different project.

Integrations. Payment gateways, Tally, WhatsApp, an existing ERP, a courier's tracking API. Each is a small project of its own and each fails in its own way. The hard part is rarely connecting them. It is deciding what happens when they disagree, which is where most integration projects go wrong.

Moving your existing data. Nearly always underestimated. Years of records in spreadsheets, half of them inconsistent, have to be cleaned before they can go anywhere. Budget for it explicitly or it will be discovered in week six.

An undecided process. If three people in the business describe the process three different ways, the first weeks of the project are spent getting them to agree. That work is necessary, but it is not software, and it is better done before anyone quotes. A clear brief is the cheapest discount available.

Reports. "And a dashboard" sounds like the last line of a brief. Reports that people make decisions from have to be right in every edge case, and that is where a surprising share of the testing time goes.

Two quotes for the same brief are rarely pricing the same thing. Ask each one what it assumed.

The costs after the build

This is where custom software earns its reputation, and all of it is predictable.

Hosting. A small business application runs comfortably on ₹2,000 to ₹15,000 a month of cloud infrastructure. It rises with users and with files — anything that stores photos or documents grows every month.

Maintenance. A reasonable planning figure is fifteen to twenty-five per cent of the build cost every year: security updates, libraries that stop being supported, the browser change that breaks one screen, the person whose access has to be removed today. Software nobody maintains does not stay the same. It decays.

Per-use charges. SMS, WhatsApp template messages, email delivery, maps, payment gateway fees. Each one is small. Together they are a line on the monthly bill that nobody quoted.

Changes. You will want them. The software teaches you something about your own process the moment people start using it. If every change is a separately negotiated project, you will stop asking, and within a year the team will be working around the tool you paid to remove the workarounds.

How to read a quote

Ask who owns the code, the repository and the cloud account. If the answer is anything other than you, that is the real price, whatever the number says.

Ask what the first usable version is and when it arrives. A quote with nothing usable until the end puts all of the risk in one place.

Ask what a change costs after launch, and what happens if the project runs longer than planned. The answers tell you more about a team than its portfolio does.

And ask what they would leave out. A team that cannot name anything to cut has not understood what you are trying to do.

The cheaper option most people skip

Before paying for any of this, run the process for a month on tools that cost almost nothing: a structured Google Sheet, a form, the free tier of Zoho or HubSpot. If it holds up, you may not need custom software at all, and you should not let anyone talk you into it. If it breaks, you will know exactly where — and that is the brief, written by your own operation instead of by guesswork.

If the month convinces you it is worth building, read how to decide between building and buying first, then how we approach custom software. If it convinces you the tools were fine, that is the better outcome. It cost you a month instead of a budget.