When a business says "we need a website", they might mean a five-page brochure site — or a customer portal with logins, payments and dashboards. Both run in a browser, but they are very different projects. Knowing which one you need saves time, money and frustration.
A website: information and enquiries
A website mainly presents information and captures enquiries. Visitors read, look at your work and contact you.
Typical features:
- Pages about your business, services and team
- Blog and resources
- Contact forms, WhatsApp and call buttons
- Basic SEO and analytics
Good for: most service businesses, clinics, consultants, institutes, local businesses.
An e-commerce site: selling online
A step further — visitors can browse products, add to cart and pay.
- Product catalogue and search
- Cart, checkout and payment gateway
- Order management, shipping and GST invoicing
Good for: businesses selling physical or digital products directly to customers.
A web application: doing work
A web application lets users log in and get something done. The value isn't reading — it's the work the software does.
Examples:
- A client portal where customers track orders or projects
- A booking or appointment system with schedules and reminders
- An internal tool for managing leads, inventory or field staff
- A SaaS product that other businesses subscribe to
Typical features: user accounts and roles, dashboards, data entry and reports, integrations (payments, WhatsApp, email, accounting), and business rules specific to you.
Questions to decide what you need
- Do users need to log in? If yes, you're likely in web application territory.
- Is the main goal enquiries, sales, or getting work done?
- Does it need to follow your specific process — approvals, calculations, workflows?
- Does it need to connect with other systems?
- Will it store customer or business data that needs security and backups?
Why costs differ so much
A website is mostly design and content. A web application involves logic, databases, security, testing and ongoing maintenance. The more rules, roles and integrations, the more it costs — and the more careful scoping matters.
That's why a good web application project starts with a discovery phase: mapping your process, deciding what's essential for version one, and planning the rest for later.
You might need both
Many businesses have a marketing website to attract customers and a separate web application to serve them — like our own products AgencyNest and PeopleNest, which each have a public site and the application behind the login.
Not sure which you need? Our website development and web application development teams can help you scope it — or get a quick range from the cost estimator.