For a long time, the unit of digital work was the website.
For a long time, the unit of digital work was the website.
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.
This matters because AI makes isolated page production cheaper.
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.
This is why I increasingly think agencies should sell operating systems for digital businesses, not websites.
That does not mean replacing every client tool with one giant platform.
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 strategic agency question therefore changes from:
“What pages do you need?”
to:
“How does your organisation need to operate?”
That 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 does not weaken this model.
It strengthens it.
As generation becomes easier, the value of knowing what should be generated, where it belongs and what it connects to becomes more important.
06Practice context
This is the direction behind the DesignsDusted ecosystem itself: Payload CMS, ERPNext, content automation, Trilium knowledge management and external publishing are being treated as connected parts rather than separate projects.
References used for this article
If you can relate, feel free to reach out.




