Published 15 September 2026
The distinction that actually matters
The dividing line is not how it looks, how modern it is, or whether it works on a phone. It is whether the thing stores state that belongs to a particular person.
A restaurant's menu page is a website. Everyone sees the same thing, it changes when the restaurant changes it, and nobody logs in. The system the kitchen uses to track orders is a web application: it has users, each user sees something different, and what it shows depends on what has happened.
That difference drives everything downstream — cost, timeline, hosting, security obligations and what happens when it breaks. A website that is down is embarrassing. An application that is down stops work.
What each costs, roughly
For Indian projects, a business website from a custom team generally runs from around ₹60,000 for a small brochure site to a few lakh for a larger site with custom functionality. Four to eight weeks.
A web application generally starts around ₹3 lakh and runs to ₹25 lakh depending on the number of distinct roles and workflows. Three to six months for a first version people can genuinely use.
The order-of-magnitude gap is not padding. An application has to handle two people editing the same record, a user who should not see another user's data, a report that has to still be correct in three years, and a failure that must not lose anything. None of that exists on a brochure site.
How to tell which you are describing
Ask these of whatever you are planning. Any yes means you are describing an application, whatever you have been calling it.
- Does anyone log in?
- Do two different people need to see different things?
- Does it need to remember what happened last time?
- Would you be in trouble if the data in it were lost?
- Does someone need a report out of it?
- Are there rules about who may approve or change something?
The expensive mistake in each direction
Commissioning an application when you needed a website means spending several lakh and several months on something that a ₹60,000 site would have done. It happens when a business describes its ambitions rather than its immediate need, and the developer prices the ambitions.
Commissioning a website when you needed an application is the more common and more damaging error. It shows up six months later: the site is live, and the actual work is still being done in spreadsheets, because the site was never capable of it. You then pay for the application anyway, and the website was not the foundation of it.
The way to avoid both is unglamorous. Write down what happens today, step by step, including the steps done by hand. The answer is usually obvious from that document and almost never obvious from a conversation about the website.
You often need both, in order
The common path for a growing business is a website first — because that is what brings in enquiries — and an application second, once the volume of work behind those enquiries stops fitting in a spreadsheet.
Built in that order they are two clean projects. Built the other way round, or bundled into one, you tend to get a site that is slower than it should be and an application that was designed around a marketing brief.