A website builder produces pages. A web system produces pages and participates in the business — capturing enquiries into your records, checking availability, routing work, updating a customer, taking a payment against a job that exists in another system.
Both are legitimate. The mistake is buying one while needing the other, which is usually discovered about a year in, when a reasonable request turns out to be impossible.
What builders do well
Modern website builders are genuinely good, and dismissing them is a mistake made mostly by people who sell alternatives.
- Fast to launch. A credible site in days rather than months.
- Low fixed cost, with hosting, certificates and updates included.
- No technical maintenance. Security patching and infrastructure are handled.
- Editable by non-technical staff, which is worth more than it sounds — pages that require a developer to change do not get changed.
- Predictable. The platform constrains what is possible, which prevents a lot of expensive experimentation.
For a business whose website needs to explain what it does, demonstrate credibility and collect enquiries, a builder is frequently the correct and complete answer. Recommending anything more is often unnecessary spending.
Where builders reach their limits
The constraints appear at predictable points, and they are usually about integration rather than appearance.
Connecting to your other systems. Getting enquiries into your CRM with the right fields, pulling live availability, showing a customer the status of their job. Builders offer some integrations; the gap appears when you need a specific behaviour rather than a supported connection.
Logic in the form. Different questions depending on the service, routing based on postcode, validating against a real service area, calculating an indicative price. Some builders manage simple versions; anything conditional tends to become awkward.
Anything with an account. Customer logins, portals, saved information, documents.
Volume of structured content. Hundreds of products or locations that need to be generated from a data source rather than maintained page by page.
Performance under constraint. Some builders produce heavy pages, and there is limited scope to fix it. See why website speed still matters.
Portability. The design and structure typically do not come with you. The content does; the build does not. See why owning your domain and business data matters.
What a web system adds, and costs
A web system is built rather than assembled. It can do whatever is specified, integrate with anything that offers an interface, and be shaped exactly around how the business works.
The costs are real and should be stated plainly:
- Higher initial cost and longer timeline.
- Ongoing maintenance. Dependencies, security updates, hosting. This does not stop.
- A supplier relationship or in-house capability that has to persist.
- Change requires the developer, unless content editing is deliberately built for staff — which should be a stated requirement, not an assumption.
A web system is justified when the website is doing operational work, not when it needs to look distinctive. A distinctive appearance is achievable on most builders; operational behaviour is not.
Choosing between them
Ask what the website must do, in verbs:
- Explain, demonstrate, collect an enquiry → a builder is very likely sufficient.
- Look up, calculate, route, authenticate, synchronise → you are describing a system.
Then ask who will change it, and how often. A site edited weekly by staff has different requirements from one revised twice a year by a supplier.
Then ask what happens in three years. If the plausible trajectory involves customer accounts or deep integration, starting on a platform that cannot reach there means a rebuild. If the trajectory is more pages and better content, a builder will still be fine.
The middle ground
There is a common and under-considered arrangement: a static, fast, well-built marketing site handling the explaining and the credibility, with specific interactive functions delivered by separate purpose-built components or existing services.
The result behaves like a system where it needs to and stays simple everywhere else. It is often the right answer for a business that has one operational requirement and otherwise straightforward needs.
A note on our own work
Alden Signal builds web systems where a site has to participate in operations — integrations, enquiry routing, internal tooling and the surrounding automation.
Our website work for contractors and local-service businesses is delivered through our sister division, Alden Sites, which is built specifically around that market: fast, mobile-first sites designed to convert local enquiries.
Builder or system?
- The verbs the site must perform are written down
- Required integrations with existing systems are listed specifically
- Conditional logic or calculation requirements are identified
- Whether customer accounts are needed, now or plausibly later, is decided
- The person who will edit content is named
- The three-year trajectory has been considered
- Ongoing maintenance cost and ownership are understood for the option chosen
- What is portable, and what is not, has been confirmed before committing
Most businesses need a good builder site and one or two things connected properly. Recognising that early saves a great deal of money, and recognising the genuine exception early saves a rebuild.