Website or web app: which one does your business actually need?

"We need a website" is how most conversations start. Half the time, by the end of discovery, it turns out the business needs something else: a web application. The two look similar in a browser — both are "a site" — but they solve different problems, cost differently, and grow differently. Here's the difference in plain business terms.

A website talks. A web app works.

A website is your public face: who you are, what you offer, why you're trustworthy, how to reach you. Its job is communication and conversion — turning a visitor into an enquiry or a sale. Think of it as your best salesperson, on duty around the clock.

A web application is a tool: it does work. People log in, create records, move things through a process. A booking system, a POS, a customer portal, an inventory dashboard — these aren't pages you read, they're software you use.

Signs a website is all you need

• Your goal is to be found, look credible, and receive enquiries.
• Content changes weekly or monthly — not by the minute.
• Visitors don't need accounts or personalized data.
• Transactions, if any, are simple enough for a payment link or basic store.

If that's you, don't over-buy. A fast, well-structured website with clear calls to action will outperform an over-engineered app at a fraction of the cost.

Signs you've outgrown a website

• Staff coordinate work through spreadsheets, chat threads and phone calls.
• Customers keep calling to do things they could do themselves — book, check status, reorder.
• You re-type the same information into multiple places.
• "Who approved this?" and "what's our stock, really?" have no quick answer.

Every one of those is a process wearing a human costume. Web applications exist to take those costumes off.

What about cost and time?

A focused business website typically takes 2–4 weeks. Web applications start around 4–6 weeks for a lean first version and grow with scope. The mistake we see most isn't choosing the wrong one — it's building a web app with website expectations: no discovery, no workflow mapping, no plan for training. That's how budgets burn.

How to decide in one afternoon

1. List the top five things you want visitors or staff to do.
2. Mark each one: is it reading/contacting (website) or doing/recording (app)?
3. If three or more are "doing" — you're shopping for a web application.
4. Either way, start smaller than you think. Version one should solve the most painful thing only.

Start with the pain, not the product. The right build reveals itself the moment you write down what people actually need to do.

Still unsure which side you're on? That's exactly what our free discovery call is for — bring your list of five, and we'll tell you honestly what to build (and what not to).