The most interesting question about a web application isn’t what it can do, but what it replaces. A web application is software you work in through the browser: people log in, enter data, and a process runs from start to finish inside it. It becomes worth building the moment the work it takes over is already costing you money, in hours, in mistakes or in customers left waiting.
That moment hasn’t arrived for every business. We’ve been developing software since 2001 for organisations that had reached that point, and we’ve spoken to plenty that hadn’t. The difference is rarely in the technology; it’s in the sums you do beforehand.
A web application isn’t a bigger website
Your website informs: visitors read, compare and get in touch. A web application works: things get planned, calculated, approved and delivered inside it. That distinction shapes how you judge the investment. You measure a website by visitors and enquiries, a web application by the work it takes off your organisation’s plate. For exactly how the two relate, read the difference between a web application and a website.
The gains are in work that repeats
A web application almost always pays for itself in the same place: work that recurs daily or weekly. Data someone retypes from one system into another. Quotes pieced together from separate spreadsheets. Customers who call for a status update that could just as easily sit in a portal. Each case is small on its own; added up, it costs someone a substantial chunk of their working week.
One-off work rarely justifies building software, and the same goes for work that’s tedious but rare. So the question isn’t whether a process could run better, because almost any process could. The question is how often it repeats and what each repetition costs.
Do the sums before you commission anything
That sum doesn’t need to be complicated. Three questions bring it into focus:
- How many hours a week go into the manual work the application would take over, and whose hours are they?
- What does a mistake cost, such as data entered twice or a missed delivery, and how often does it happen?
- How many enquiries does your team handle that customers could answer themselves if they could see their own data?
Set that against the full investment, including maintenance in the years after delivery. If the sum doesn’t add up on paper, it won’t add up in practice either. In that case, a web application isn’t important for your business right now, however convincing a supplier’s pitch sounds.
Sometimes off-the-shelf software is the better answer
If the process you want to move away from isn’t distinctive to your organisation, look at existing packages first. For bookkeeping, time tracking or a standard CRM, custom development is rarely worth the cost. Custom software wins where the process itself carries what makes your business distinctive, and off-the-shelf software would force you to bend your way of working around it. We go into that trade-off further in the difference between custom web applications and SaaS solutions.
Timing matters too. If the process itself is still changing month to month, building software would lock in a way of working that isn’t settled yet. Stabilise the process first and automate afterwards, with a small prototype in between if that helps.
Start with the process, not the feature list
A good project therefore doesn’t start with screen designs and features, but with the questions above. In a first conversation, we keep asking until it’s clear where the hours and mistakes sit; only then does it make sense to talk about web applications and portals. If you recognise a recurring process like this in your organisation, work out the sum first with someone who does the work every day. And if you’d like it checked by engineers who’ve done this sum many times before, we’re happy to join you at the table.