When a business tells me they need a website, I always ask a follow-up question: what do you need it to do?
Sometimes the answer is: display information, look professional, let people contact us. That is a website. A well-built one, but a website.
More often, the answer is: let users sign up, process payments, send automated emails, integrate with our CRM, show personalised content, handle orders, generate reports. That is not a website. That is a digital system that happens to have a web interface.
The distinction matters because they are built differently, operated differently, and break differently.
What a website is
A website is a collection of pages that deliver content to visitors. The content is largely static — it doesn’t change based on who is viewing it or what they’ve done previously. The interaction is minimal — contact forms, newsletter signups, links.
Websites are best built as static HTML served from a CDN. They are fast, cheap to host, simple to maintain, and require no backend infrastructure beyond the content management system.
A website is the right tool when your primary goal is presenting information and establishing presence. Most marketing sites, portfolios, blogs, and brochure sites are websites, and that is the correct choice.
What a digital system is
A digital system is a platform with logic. It responds differently to different users. It stores and retrieves data. It integrates with other services. It performs actions — sending emails, processing payments, generating reports, executing automated workflows.
A digital system has a frontend (the interface), a backend (the logic and data layer), and infrastructure (the servers, databases, queues, and networking that make it run).
Examples:
- An e-commerce platform is a digital system
- A trading platform that connects to live markets is a digital system
- A SaaS product where users have accounts and data is a digital system
- A healthcare data pipeline that ingests, processes, and stores patient data is a digital system
Why the distinction matters
Businesses that commission a “website” when they need a “digital system” encounter the same set of problems:
Scalability ceiling hit immediately. A website-level build can’t handle user accounts, real-time data, or complex business logic. The moment you try to add these features, you’re rebuilding on an inadequate foundation.
No backend thinking applied. Who handles database design? API security? Rate limiting? Error handling? Session management? These questions don’t exist for a website. For a digital system, they are fundamental. If they weren’t answered during the build, the system is incomplete.
Operational complexity with no operational plan. Websites go down occasionally — it’s annoying. Digital systems going down can mean lost transactions, data inconsistency, and significant business impact. Systems need monitoring, runbooks, and incident response processes that websites don’t require.
Security gaps. A static website has a small attack surface. A digital system with user data, payment processing, and API integrations is a target. Security has to be designed in — input validation, authentication, authorisation, dependency scanning, secrets management — not added after launch.
How to know which one you need
Ask this question: does the system need to remember anything, do anything, or treat different users differently?
If yes to any of these — you need a digital system. Design it as one from the start.
If no — you need a website. Build it as one. Don’t over-engineer it.
The mistake runs in both directions. Businesses that need a website get sold a complex platform they don’t need and can’t maintain. Businesses that need a digital system get delivered a website that can’t do what they actually need.
Building a digital system the right way
The foundations of a well-built digital system:
- Architecture designed for the actual requirements — not the most impressive architecture, the correct one
- Backend with proper data modelling, API design, and security
- Infrastructure as Code — reproducible, version-controlled environments
- CI/CD pipeline — automated, reliable deployments
- Monitoring and observability — visibility into what the system is doing
These are the starting point, not optional extras. A digital system without these foundations will need to be rebuilt — it is a question of when, not whether.
If you’re trying to figure out what you’re actually building and what it requires, let’s have a conversation. I’ll give you a straight answer.