"How much does custom software cost?" is the first question every owner asks and the one no honest developer can answer in a sentence. The real answer is a list of what drives the price and a method for getting a fixed number in writing before any code is written. This article gives you both, with market ranges you can use as a sanity check, and the questions that separate a serious quote from a guess.
One warning. This article deliberately gives relative sizes, not rupee bands, because a number on a page without a scope behind it is a guess, and the one rupee figure we do publish is a product we actually license. Any specific price comes only after a written scope, and a developer who quotes a firm number without one is quoting a number they intend to change later.
Want a real number for your project? A scoping sprint produces a written scope with a fixed price per milestone that you can take to anyone. See our custom software development page for how it works.
Book a free scoping callWhat a custom software quote is made of
A system is a set of screens, each with rules, connected to data and to other systems. Price follows those four things almost exactly. A ten-screen internal tool with simple rules and no integrations is a small build. A forty-screen multi-branch system with approval chains, five integrations and a regional-language print format is a large one. Everything else, the stack, the design polish, the hosting, moves the number by percentages. The screens, rules, data and integrations move it by multiples.
The seven things that move the price
1. Number of screens and roles
Count the screens a user sees and the roles that see different versions of them. Owner, branch manager, cashier and auditor seeing four versions of "daily closing" is four screens of work, not one. This is the single biggest driver and the easiest to estimate honestly once someone has sat with your team and written the list.
2. Business rules and approvals
"A purchase above Rs 50,000 needs the branch manager; above Rs 2 lakh needs head office; rate-of-the-day applies unless the customer has a locked rate" is three rules and a dozen edge cases. Rules are where custom software earns its keep and where estimates go wrong. A good scope writes each one down before pricing.
3. Integrations
Every system you want connected is a line item: Tally, Zoho, Razorpay, the WhatsApp Business API, a bank export, a vendor portal. The cost depends less on the developer than on the vendor. A clean API is a day; a vendor who only allows a nightly CSV export is a week; a vendor who refuses access is a change of plan. Ask your vendors about access before you ask a developer for a price.
4. Data migration
Years of spreadsheets with inconsistent columns, duplicate customers and three spellings of every city. Migrating it is real work, often a week or more, and it is routinely left out of quotes until the last month. Insist that it appears in the scope.
5. Indian specifics
GST invoice formats, state fields, e-invoicing, TDS, regional-language labels and receipts, rate-of-the-day pricing for the gold trade, RERA fields for real estate. These are not exotic but they add screens and rules, and a developer unfamiliar with them will underquote and then overrun.
6. Multi-tenant versus single business
A system for your business is one thing. A product you sell to other businesses, where each customer's data must be isolated, each has their own users and plans and billing, and an admin console sits above them all, is a different and larger build. If you plan to sell the software later, say so at scoping, because retrofitting isolation is expensive.
7. The stack and who maintains it
PHP and MySQL on shared hosting is inexpensive to run and easy for any local developer to maintain, which matters for a branch business in a tier-two city. A modern TypeScript stack on a managed platform scales further and costs more in specialist time. Neither is right in the abstract. The question is who will run the thing in year three.
How the build sizes compare
| Type of system | Typical shape | Relative size of the build |
|---|---|---|
| Focused internal tool | 5 to 12 screens, 2 roles, no or one integration | 1x, the smallest build |
| Billing or CRM for one business | 12 to 25 screens, 3 roles, print formats, one or two integrations | Roughly 2x to 3x |
| Multi-branch operations system | 25 to 50 screens, approval chains, reporting, migration | Roughly 4x to 8x |
| Multi-tenant SaaS product, first release | Tenant isolation, plans, billing, admin console | Roughly 6x to 12x for a first release |
| Licensed ready product | Existing software configured for you | A fixed yearly fee, no build |
Notice the last row. If a product already exists for your trade, the honest answer is often a licence, not a build. Our own gold buying ERP is offered under licence at Rs 50,000 a year for up to three branches; a custom build of the same would cost many times that. Ask any developer you talk to whether they would rather license you something that fits.
What a serious quote looks like
- A written scope first. Screens, roles, rules, integrations, migration, print formats, listed. If the developer will not write this before pricing, the price is not real.
- A fixed price per milestone, each with a definition of done you sign off before it is invoiced. Hourly billing on a fixed-scope build moves the risk onto you.
- Scope changes priced in writing, not absorbed into delay. Changes are normal; silence about their cost is not.
- Ownership stated: repository, hosting, domain, database and documentation in your name from day one.
- The year-one running cost beside the build cost: maintenance, hosting and third-party services. A quote without it is half a quote.
What it costs after launch
Software is a living thing. Hosting is usually small for a single business, often a few hundred to a few thousand rupees a month on a managed platform or shared hosting. Maintenance, meaning fixes, small changes, backups and checks when a vendor on your side changes something, is commonly a fixed monthly care fee. A rough planning figure many firms use is 15 to 20 percent of the build cost per year, though it varies with how much you change. If the budget cannot cover year one of running, build less or buy. A half-maintained system is worse than a good spreadsheet.
Three ways to cut the price without cutting the system
- Ship the first module early. Replace the single most painful sheet first and use it for a month. What you learn changes the rest of the scope, usually by removing screens nobody needed.
- Decide your process before scoping. Every undecided rule becomes a change later. A half-day session to write the process down is the best money in the project.
- Check vendor access before you start. Knowing that Tally will only give you a nightly export, or that the HMIS vendor charges for API access, changes the plan and the price before anyone has built around the wrong assumption.
When to buy instead of build
Buy when a packaged tool covers 90 percent of your process and you have not tried it, when the process changes every month, or when nobody on your side will own the system after launch. Build when the workarounds cost more than the licence, when your process is your advantage, when several branches or partners need one truth, or when the product you need does not exist. A good developer will tell you which on the first call, including when the answer is not them. Our custom software development page describes how we scope, price and ship, and what we build for ourselves, which is the only proof worth showing.
Frequently asked questions
How much does custom software cost in India in 2026?
It depends on screens, roles, rules and integrations, so no honest developer can answer in a sentence. A focused internal tool is the smallest build; a billing or CRM system for one business is roughly two to three times that, a multi-branch operations system four to eight times, and a first release of a multi-tenant product more again. A real number needs a written scope with a fixed price per milestone.
Why do software quotes vary so much?
Because most quotes are given before anyone has counted the screens, roles, rules and integrations. Two developers quoting the same one-line brief are pricing two different systems. A written scope removes most of the variation.
Is hourly or fixed-price better for custom software?
For a defined business system, fixed price per milestone with a written definition of done puts the risk where it belongs, on the builder. Hourly suits open-ended research work, not a billing system.
What does software maintenance cost per year?
A common planning figure is 15 to 20 percent of the build cost per year for fixes, small changes, backups and checks, plus hosting at cost. The exact figure depends on how much you change. Budget for it before you build.
Should I buy ready software or build custom?
Buy when a packaged or licensed product covers about 90 percent of your process and you have tried it. Build when the workarounds cost more than the licence, your process is your advantage, or the product you need does not exist.