Six things drive the cost of custom software in India: how many systems it connects to, how far your process differs from a standard one, the state of your data, the regulations you report against, your targets for speed and uptime, and how much time your own people give. Together they set the team size and the months it works. Add an allowance for risk and the cost of running the software afterwards, and you have the cost. A fair quote follows a measured scope, not a guess.
The six drivers, with Indian examples
| Driver | What to ask | What raises cost |
|---|---|---|
| Integration surface | Which systems must the software read or write? | Each one is its own build and test: Tally for statutory books, SAP, banks, payment gateways, the GST e-invoice and e-way bill portals, plant data from SCADA or PLC systems |
| Process variance | How far does your process differ from a standard flow? | Each exception is a rule to design, build, test and explain to users |
| Data condition | Are old records clean, complete and in one place? | Duplicate customers, missing item masters and spreadsheets with free-text fields need clean-up before they move |
| Regulatory obligation | Which laws shape the design? | GST documents (see the GST e-invoice portal), personal-data duties under the DPDP Rules, as announced by PIB, log retention under the CERT-In directions, sector rules for banks, insurers and hospitals |
| Targets for speed and uptime | How many users at peak, how quickly, and how much downtime is tolerable? | Higher uptime needs redundant infrastructure and monitoring; high peaks need load testing |
| Your availability | Who decides, tests and approves each fortnight? | Slow decisions stretch the schedule, and a stretched schedule costs the same team more months |
Which driver weighs most differs from project to project, so rank them for your own case. Custom software carries no per-seat fee on Brihat Infotech's custom work, so user count is not a driver there; check whether a vendor's quote scales with users. For the ERP version of this table, see what moves the cost of a custom ERP.
How a quote is built
A quote is an estimate of work packages, turned into people and months. Read it in this order:
- Scope. The modules, screens, reports and integrations, each named.
- Work packages. Each module split into design, build, test and release.
- Team shape. Roles (architect, engineers, tester, delivery lead) and the days each one works.
- Months. Days divided by the team's working rhythm, with testing and your approval cycles.
- Risk allowance. A contingency line for what nobody can see yet.
- Running costs. Hosting, support and licences after go-live, shown separately.
If a quote shows a single total and no team, you cannot tell which of the six drivers it assumes. Ask for the team shape and the scope list. A fixed-price discovery exists to produce exactly these two documents, so that the build quote sits on measured work and not on opinion.
Three ways to contract the work
| Model | You pay for | Who carries the risk | Fits when |
|---|---|---|---|
| Fixed scope | Deliverables, priced phase by phase | The vendor carries estimate risk inside agreed scope; you carry the cost of changes | The scope is clear and stable |
| Dedicated team | A team, billed monthly | You carry scope risk; direction changes cost nothing extra | The scope will change as you learn |
| Build-operate-transfer | The build, a run period, then a fixed transfer fee | Shared by a service level during the run period | You want a unit that you will own later |
Each shape moves risk, not the total cost of the work. A fixed price on an unclear scope buys either padding or arguments over change requests. A monthly team on a clear scope can feel open-ended. For the details, see ODC, staff augmentation, BOT and GCC compared and what staff augmentation costs to manage.
Costs that sit outside the quote
Add these to your budget before you compare totals:
- GST on top of the quoted fee, unless the quote says it is included. Ask your CA for the rate that applies.
- Hosting and infrastructure for every environment: development, test and live.
- Third-party fees: SMS, WhatsApp, email, maps, payment gateways, signature services, and any licence for a database or reporting tool.
- Support after go-live, often a monthly retainer set by the number of environments and the cover hours.
- Your own people's time for workshops, testing and training. Quote this in days, not rupees.
- Change requests after the scope is fixed.
- Data clean-up that your team must do before migration.
The clause that can change the price you paid
Ownership is a cost question. If the contract is silent on how long the code is assigned or where, the Copyright Act, 1957 can limit the rights you paid for, and a build you thought you owned outright may come with a limited term and territory. The full explanation, with the statute text and the 2011 Delhi High Court judgment, is in how to choose a software development company in India. Ask for the code to sit in your own repository from the first commit, and have counsel draft term and territory in full.
Where the money can be saved
- Cut modules, not depth. Fewer modules in the first phase genuinely cut that phase. A shallow module often moves the missing behaviour into a spreadsheet, which brings the cost back.
- Sequence by pain. Start with the process that currently runs on a spreadsheet and hurts most.
- Keep what works. Tally can stay in charge of statutory books while new software sends it entries.
- Buy where your process is standard. A packaged product fits better when your process matches its standard flow.
- Prepare the data early. Clean master data costs less in your hands, before the build, than in the vendor's hands, during it.
For the time side of the budget, see how long a custom ERP takes, phase by phase.
Eight lines that make two quotes comparable
Send the same request to every firm and ask for the answers on one page:
- The scope list, module by module.
- The team shape: roles and days.
- The assumptions behind each of the six drivers.
- What is excluded.
- The payment schedule and what each payment is tied to.
- How a change request is priced, and who approves it.
- Running costs after go-live, separately.
- The ownership clause: owner, term, territory, repository.
Why published price ranges mislead
Vendor blogs publish rupee and dollar ranges. They differ widely between sources because each one averages different projects: a booking app and a plant ERP carry the same label, "custom software". A range tells you nothing about your scope. A measured scope does.
Where Brihat Infotech fits
Brihat Infotech publishes no prices: the quote follows a fixed-price discovery, invoiced separately, and payment runs against delivered milestones. See how we work.