Custom Software
Almost every first conversation I have starts with the same question, usually within the first few minutes: "So what will something like this cost?"
It's a fair thing to ask. It's the number you need before you can decide anything. But it's also the one question I can't answer honestly in a single figure, and any developer who fires back a price before understanding your business is either guessing or quietly selling you something off a shelf with a "custom" label stuck on it.
Custom software costs what it costs because it's built around how your business actually works, not the other way round. A tool that automates one small process and a platform that runs your whole operation are both "custom software," and they are nowhere near the same price. So instead of a price list that would be wrong for almost everyone reading this, let me show you what actually moves the number, so you can place your own project on the scale before you talk to anyone.
Most work I see falls into one of three rough sizes.
A single, focused tool. One process, automated. A form that feeds a dashboard, a report that generates itself, a small internal app that replaces one painful spreadsheet. This is the smallest kind of build, and here's an honest thing most developers won't tell you: if your need is genuinely this small, custom software might not even be the right answer. An off-the-shelf tool or a well-set-up existing platform can often do it for far less. I've talked people out of hiring me at this size more than once.
A working system for one part of your business. This is where custom starts to earn its cost. A system that handles a real chunk of your operation say orders, inventory, and invoicing tied together with one or two integrations to the tools you already run, like Zoho or WhatsApp. Multiple features, real users, real business rules. This is the most common project I take on, and it's where my pricing usually starts. Most of my builds begin around ₹3 lakh, and there's a reason for that floor: below it, you're not really buying custom software. You're buying a template that looks fine in a demo and starts breaking the moment your business does something slightly unusual, which every real business does. The ₹3L isn't a random rate. It's roughly what it costs to build something that fits your operation and survives contact with it.
A platform that runs multiple parts of the business. Several modules working together, multiple integrations, different user roles and permissions, data pulled in from systems you already use, proper reporting. This is the kind of build that replaces the "five tools and a WhatsApp group" way of running things. Depending on how much it covers, these land anywhere up to ₹10–15 lakh. Not because the code is mysteriously expensive, but because there's simply more of everything: more workflows, more edge cases, more testing, more that has to keep working reliably on day 400, not just day 1.
Within those bands, a handful of things decide where your project sits:
You don't need to price these yourself. You just need to know that when a build costs more, it's usually one of these, not padding.
Here's the part that surprises people who've only ever bought software off a shelf. The build price is not the whole cost.
Custom software still needs somewhere to run (hosting), someone to fix things if they break (support), and it will need changes as your business grows, because a system that can't change is the thing you were trying to escape in the first place. None of this is huge, but it's real, and I'd rather you know it going in than feel ambushed six months later. A developer who only quotes the build and goes quiet about everything after it is not doing you a favour.
You can get "custom software" built for very little. India has no shortage of the cheapest possible option, and the temptation is obvious when one quote is a third of another.
The problem is what you can't see in the quote. Cheap builds tend to skip the boring, invisible work the security, the error handling, the testing, the documentation, the part where the person who built it can actually explain how it works. It all looks the same in a demo. The difference shows up later, when something breaks at the worst moment, or the developer disappears, or you need one change and discover the whole thing was held together in a way nobody can safely touch. Then you pay again to have it rebuilt properly, and the "cheap" version turns out to be the most expensive route you could have taken.
India's rates are a genuine advantage you can get senior-level work here for a fraction of what the same build costs in the US or Europe, which is exactly why a lot of my enquiries come from abroad, including the Middle East. But "cheap" and "custom software that lasts" don't belong in the same sentence. The sensible spot isn't the cheapest quote or the agency charging you for three layers of management. It's someone senior enough to build it right, direct enough that you're not paying for overhead, and around afterwards when you need them.
When people weigh up the cost, they usually frame it as "₹X for software versus ₹0 for carrying on as we are." That's the wrong comparison, and it's why good projects sometimes get stalled over the price.
Carrying on as you are is not free. It costs hours every week that your team spends copying data between spreadsheets. It costs the errors that slip through and the ones you only catch at audit. It costs the fact that the business runs on one person who "knows the system," and stops the day they're on leave. And it costs the growth you can't take on because the manual way doesn't scale. Add those up over a year and the real question isn't "can I afford custom software." It's "can I afford to keep doing it by hand."
That's the number worth comparing against. Not the quote.
The most useful thing you can do before talking to anyone is get clear on scope: which parts of your business you want the software to cover, what it needs to connect to, and where the current process actually hurts most. The clearer that is, the more accurate any quote you get will be, including mine.
If you already know roughly what you need built and want a straight answer on what it would take, that's the conversation I'm happy to have. Tell me what you run today, what you want it to do, and where things break. From there the price comes from the actual work, not a number pulled out of the air.
You can see the kind of systems I build on my work page, and if your build involves connecting to something like Zoho, here's how I built a customer portal on top of Zoho Books so you get a feel for how I approach it.
More to read