Most enquiries arrive as a version of the same sentence: "we need a website." Sometimes that is exactly right. Sometimes what is actually needed is an application, or a piece of custom software, and the word "website" is just the nearest familiar term for "something on a screen that fixes this." The difference matters, because building the wrong one of the three is not a small miscalculation — it is a working thing that solves nothing.
Here is a way to tell which one you actually have, before anyone writes a quote.
Start with what the thing has to do
A website's job is to be read. Someone arrives, finds out what you do, and either leaves or acts — calls, buys, enquires. Nothing on the page needs to remember who they are or change based on who is looking at it. If your entire problem is "people don't understand what we do" or "people can't find us," you need a website, and a good one is usually enough.
An application's job is different: someone logs in, does something, and comes back to do it again. The moment a screen needs to know who is looking at it — a customer checking an order, a staff member updating stock — you have crossed into application territory, whether or not anyone on your team has used that word yet.
Custom software is what you need when the process itself is the product. Not a screen that represents your business, but a system your business runs on: quoting, scheduling, production tracking, the actual mechanics of how work moves from one person to the next.
The test that actually works
Ask one question: does this need to remember anything about the person using it?
- No — they just need information, and the information is the same for everyone. That's a website.
- Yes, but what they're doing is a defined, contained task — checking a status, submitting a form, viewing their own history. That's an application.
- Yes, and the "task" is actually your whole operation, with steps, exceptions, and people handing work to each other. That's software.
A saree showroom that wants customers to see the collection and get directions needs a website. The same showroom, once it wants customers to check whether their order is ready without a phone call, needs a small application layered onto that website — a portal, in practice, even if nobody calls it that. If the showroom then wants production, stock, and dispatch to stop living across four different notebooks and a shared phone, that is software, and it is a genuinely different project from the first two.
Why this is worth getting right before you ask for a quote
A developer who is only ever asked to "build a website" will build exactly that — a good one, possibly — even when the real problem was underneath it the whole time. That's not a failure of skill. It's what happens when a brief is treated as an instruction rather than a symptom.
This is also why the first real step in any project we take on is not a design file or a sitemap. It's a conversation about what the thing actually has to do, for whom, and how often — which usually takes less than an hour and saves considerably more than that later. If you're not sure which of the three you need, that uncertainty is itself a completely normal place to start from.
Tell us what you're building, even if you're not sure yet which of the three it is. Working that out together is the first stage, not a prerequisite for it.