Website vs Web App: Which Does Your Business Actually Need?
One costs a few thousand and takes weeks. The other costs tens of thousands and takes months. Here's how to tell which one your problem calls for.
A lot of wasted budget comes from getting this one distinction wrong.
Businesses build a beautiful brochure website when what they needed was a tool their staff could use. Or they commission a full custom application when a good website plus two existing services would have done the job for a tenth of the cost.
The difference is simpler than the jargon suggests.
The distinction in one line
A website presents information. A web app does work.
If people come to read, browse, and then contact you, it’s a website. If people log in and change something — book a slot, submit a claim, track a job, manage inventory — it’s an app.
The clearest test: does the thing get more valuable the more your users put into it? A website is equally useful on day one and day one thousand. An app accumulates state, and that state is the point.
You need a website when
- Customers need to find you, trust you, and get in touch
- Your content is mostly stable: services, prices, case studies, contact details
- The goal is a phone call, an email, a booking, or a visit
- You want to rank in search for what you do
Cost: $2,000–$8,000 for something genuinely good — fast, well-written, properly structured for search, easy for you to update.
Timeline: two to five weeks, and most of that is writing the content, not building.
Don’t underrate this. A fast, clear, well-written site with sharp copy converts better than most custom software ever will, and it’s a fraction of the price. A lot of businesses need a better website far more than they need an app.
You need a web app when
- People log in and see data that belongs to them
- Something is currently being tracked in a spreadsheet that three people edit and one person guards
- Your process has states — pending, approved, in progress, complete — that people need to move things between
- You’re re-typing the same information into two different systems
- Your customers are asking you for status updates you have to look up manually
Cost: $12,000–$60,000 for a solid first version, depending mostly on integrations and permissions rather than screen count.
Timeline: six weeks to six months.
The middle ground almost nobody offers you
Here’s what agencies rarely mention, because it doesn’t bill well: a large number of “we need an app” problems are solved by a good website plus two or three off-the-shelf services wired together properly.
Real examples I’ve built or recommended:
A booking system. You almost certainly don’t need to build one. A scheduling service embedded in your site handles availability, timezones, reminders, rescheduling, and payments — problems that are genuinely hard and completely solved. Building it yourself is months of work to end up slightly worse.
A client portal for sharing files and updates. Often a well-structured shared drive plus automated status emails. Zero build cost, works immediately, and your clients already know how to use it.
An online shop. Use a hosted platform. Custom e-commerce is a decision you make when your requirements have genuinely outgrown the platforms, not before — and you’ll know when that happens, because you’ll be fighting the tool daily.
Internal dashboards. Connect a dashboard tool directly to your existing data. Days of setup instead of weeks of building.
Spend the saved money on the part that’s actually unique to your business. That part is usually smaller than it feels.
The question that settles it
Forget the technology for a moment and ask:
What is the thing my business does that no product on the market does for me?
Build that. Buy or embed everything else.
If your honest answer is “nothing, really — we just need people to find us and call us,” you need a great website, and you should feel relieved rather than disappointed. That’s the cheap, fast outcome.
If your answer is “we coordinate a specific workflow between customers, suppliers, and field staff, and nothing off the shelf matches how it works” — that’s a real app, and it will pay for itself.
What I’d actually recommend
Start with the website regardless. You need one either way, and it’s the thing that brings you customers while everything else is being built. Make it fast and make the writing good.
Then, if there’s a workflow problem, spend two weeks documenting it precisely — every state, every person, every exception — before anyone writes code. That document will halve your build cost, and roughly a third of the time it reveals that an existing product does the job.
Then build only the part that’s genuinely yours.
One practical warning
Whichever direction you go: make sure you own the domain, the hosting account, the code repository, and the ability to export your data. Have that conversation before the first invoice, not after a relationship goes sour.
I’ve watched businesses pay thousands to recover access to their own website. It’s an avoidable, entirely self-inflicted category of pain.
Not sure which side of the line you’re on? Book a free call and describe the problem in plain English. I’ll tell you which one it is — including when the answer is “you don’t need to build anything.”