A website works best when it connects content, operations and customer workflows.
A client needed a redesign. An agency produced pages. The CMS managed content. The project ended.
That model is becoming increasingly incomplete.
Modern organisations operate through interconnected systems: CMS, CRM, ERP, analytics, identity, payments, automation, AI services, document management and internal portals.
The public website is simply one surface.
A polished landing page can now be generated quickly. A basic content site is increasingly commoditised.
But a functioning business system is not.
The difficult work lies in deciding where data should live, which application owns which process, how permissions work, how workflows cross systems and what happens when the company changes.
That is why agencies should build connected business systems, not only isolated pages.
It means treating the project as an ecosystem.
For example, Payload CMS may own editorial content. ERPNext may own operational records. A client portal may expose selected ERP state. n8n may connect deterministic workflows. Trilium may hold internal knowledge. Buffer may distribute approved marketing content.
The website becomes a participant in that architecture rather than the centre of the universe.
This approach also makes AI more useful.
An AI agent working inside a connected system can access structured context and create real operational value.
An AI chatbot floating on top of disconnected software usually becomes another place where information is copied and pasted.
The better question is: “Which business process should this website connect to, and who owns the information at each step?”
Starting with the operating process produces better technology decisions.
It may also produce smaller websites.
Sometimes the correct answer is fewer pages and better systems.
For agencies, that is a healthier business model because the value shifts away from output volume toward architecture, integration, governance and ongoing improvement.
AI strengthens a connected system when it can use the right context and still respect permissions, review and approval.
As generation becomes easier, the value of knowing what should be generated, where it belongs and what it connects to becomes more important.
06What buyers should ask
Ask a prospective partner to show where content, customer records, approvals and AI output will live. The answer should name the responsible system and the person who can review or reverse a consequential action.


