“We need a new website” is one of the most common requests we hear — and often the business actually needs something slightly different. Sometimes it’s a booking system, sometimes a customer portal, and sometimes the real problem is a giant spreadsheet that runs the whole company. Understanding the difference early saves time, budget and frustration.
In this article we explain the difference between a website, a web app and a custom system, when each one fits, what usually drives the cost, and which questions to ask before you start.
A website: to present and sell
A website’s main job is to explain who you are, build trust and turn visitors into leads or customers. Business websites, landing pages and online stores belong here. The focus is on content, design, speed, accessibility and search visibility.
Examples: a site for a clinic, a WooCommerce store for a pet shop, a landing page for a campaign, a law firm’s site with a professional blog.
What matters on a website: loading speed (especially on mobile), accessibility, SEO, and being able to update content yourself without breaking the design. That’s how we build WordPress websites from ACF Flexible Content sections.
Choose a website if your goal is to attract customers, present your services or sell products online.
A web app: to let users get things done
A web app is software that runs in the browser. Users log in, manage data and take actions: booking systems, customer portals, dashboards and SaaS products. It works on any device without an app-store install, and can be added to the home screen like a regular app (PWA).
Examples: a portal where customers see orders, invoices and documents; an appointment system; a partner dashboard; a course platform.
What matters in a web app: permissions and security, performance with large amounts of data, clear UX, and infrastructure that scales with your users.
Choose a web app if your customers or partners need to interact with your service — not just read about it.
A custom system: to run the business
Sometimes the problem isn’t customer-facing at all. Teams struggle with spreadsheets, disconnected tools and processes that don’t fit off-the-shelf software. A custom system is built around how your business actually works.
Examples: a project and quoting system for a renovation company; an inventory and ordering system connected to the store and suppliers; a field-technician management system with a mobile app.
Check off-the-shelf software first. Ready-made CRM, accounting and ERP tools cover a lot. A custom system pays off when your process is your competitive advantage, when off-the-shelf software forces you to work the wrong way, or when licences for every employee cost more than development.
Choose a custom system if your operations have outgrown spreadsheets and generic tools.
Quick comparison
| Website | Web app | Custom system | |
|---|---|---|---|
| Purpose | Present, persuade, sell | Let users take action | Run operations |
| Who uses it | Any visitor | Registered customers or partners | Your team |
| What matters most | Content, speed, SEO, accessibility | UX, permissions, security | Fit to processes, integrations |
| Common technology | WordPress, WooCommerce | React, Node.js, cloud | React, Node.js, Python, APIs |
| Typical timeline | Weeks | Months | Months |
Often, the answer is a combination
Many projects combine all three: a website that brings in customers, a portal where they manage orders, and an internal system that connects everything to accounting and operations — often with automation in between.
You don’t have to build it all at once. A common, sensible path is to start with a good website, connect it to your CRM and invoicing, and add a portal or system only as the business grows.
You don’t need to know which one you need. Start by describing the challenge — the right solution becomes much clearer from there.
What drives the cost
- Number of user types and permissions — customer, employee, manager, partner.
- Integrations — every external system (invoicing, payments, ERP, shipping) adds work.
- Design — a ready template versus a custom design.
- Languages and direction — a site in Hebrew and English needs full RTL and LTR support.
- Maintenance — updates, backups, security and improvements after launch.
Questions to ask before you start
- What business problem are we solving, and how will we know we’ve solved it?
- Who will use it — visitors, registered customers or the team?
- Which existing systems need to connect?
- What’s the minimum we can launch first (MVP), and what can wait?
- Who will update content and maintain it after launch?
- Who owns the code at the end of the project?
Frequently Asked Questions
What’s the difference between a web app and an app-store app?
A web app runs in the browser and works on any device without installation. An app-store app (iOS or Android) is installed on the phone and fits when you need deep device access — push notifications, camera, background location. Sometimes it’s best to start on the web and add a native app later.
Can a WordPress site become a web app?
You can add a personal area, orders and advanced forms to a WordPress site. When the logic gets very complex, it’s usually better to build a separate app and connect it to the site.
How long does a custom system take to build?
A focused first version usually goes live within a few months, then capabilities are added in stages based on what the team actually needs.
Off-the-shelf or custom development?
If off-the-shelf software covers 80% of your needs, start with it and, if necessary, connect it to your other systems. Custom development is justified when your process is unique and important to the business.
Planning something new?
Tell us what you’re trying to achieve, and we’ll help you define the right scope before a single line of code is written. You can also explore our services and the projects we’ve built.