"How much will this cost" is almost always the first question, and it's a fair one. It's also the hardest to answer with a single number, because two projects that sound similar in a first conversation can end up costing very different amounts once the actual requirements are clear. Here's what really drives the cost, so you can judge a quote when you see one.
Scope is the biggest factor, by far
A simple internal tool with a handful of screens and one user role costs a fraction of what a customer facing platform with payments, multiple user types, and integrations costs. Before you can get a meaningful number, someone needs to actually define what the software does, screen by screen. Vague requirements produce vague, usually optimistic, estimates.
Integrations add up quietly
Connecting to a payment gateway, an SMS or email service, an existing ERP or accounting system, a third party API, each of these sounds like a small addition but often takes as much work as a core feature, especially when the other system's documentation is incomplete or its behavior doesn't match what was promised.
Design work is often underestimated
A functional looking interface and a genuinely well designed one take very different amounts of time. If your software will be used by customers, not just internal staff, investing properly in design usually pays for itself in lower support requests and better adoption.
Rough ranges, with the obvious caveat
These are broad, general ranges for the Indian market, meant to help you sanity check a quote, not to replace one. A simple internal tool or basic web application typically falls in the range of a few lakh rupees. A moderately complex platform with multiple user roles, a proper admin panel, and one or two integrations usually runs into the mid to high lakhs. A large scale platform with heavy custom logic, multiple integrations, and ongoing feature development can run well into seven figures over its first year. Where your project lands depends entirely on the specifics, and any agency giving you a firm number before understanding your requirements in detail is guessing, not quoting.
The cost that doesn't show up in the first quote
Software isn't a one time purchase. Hosting, monitoring, security updates, bug fixes, and future feature work are ongoing costs that continue well after launch. A cheaper initial build that skips proper architecture or testing often costs more over two or three years than a slightly more expensive one built correctly the first time.
How to actually get a number you can trust
Write down what the software needs to do in as much detail as you can, even roughly. Share it with more than one agency or developer. Ask what's included in the estimate and what would trigger an additional cost. A detailed quote that walks through the reasoning is worth more than a fast, low number with no explanation behind it.