AI-native editorial website
Build the public experience around what your organisation knows.
I build editorial websites for B2B organisations, expert-led businesses and research teams whose value depends on making complex knowledge understandable, navigable and useful.
This is the website itself: information architecture, page system, content structure, editorial presentation, implementation and deployment. It is separate from the AI-native publishing system, which changes how the organisation creates, maintains and develops the knowledge behind the site.
The distinction
Website build: what the audience experiences. Publishing system: how the organisation creates and maintains the knowledge behind it.
A website can be more than a container for pages
Many organisations have useful research, expertise, services and thought leadership, but the website presents them as disconnected pages or a chronological blog feed. The material exists. The public structure does not help people understand how it fits together.
I approach the website as an editorial product: what should the audience understand first, which bodies of knowledge deserve their own structure, how should evidence connect to services and ideas, and how can the site keep evolving without becoming harder to maintain?
Knowledge is hard to navigate
Research, services, ideas and proof exist, but the architecture does not reveal the relationships between them.
The blog has become the architecture
Important thinking disappears into a date-ordered feed rather than becoming a durable part of the site.
Pages multiply without a system
Each new initiative creates another template, route or one-off page because the content model was never designed to grow.
The website no longer matches the organisation
The business, expertise or point of view has evolved, but the public experience still reflects an older structure.
What I can build
The exact stack follows the job. The durable part is the editorial and information architecture, not a particular framework or vendor.
Information architecture
Define the sections, hierarchy and navigation around what audiences need to understand rather than the organisation chart.
Editorial content model
Design the page types, metadata and relationships needed for services, research, frameworks, narratives, articles or other knowledge assets.
Page and component system
Create reusable structures that make the site coherent while giving different kinds of evidence and thinking enough room to do their jobs.
Content shaping and migration
Restructure and adapt existing material where required so the new architecture is populated with meaningful content rather than empty templates.
Front-end implementation
Build the responsive public experience, connect the content layer and put the agreed technical structure into production.
Deployment and handover
Launch the site and document how the team can maintain, extend and publish within the system after the engagement ends.
What this is — and what it is not
It is
- a functioning website build;
- information architecture and editorial product design;
- a structured public home for expertise and evidence;
- technical implementation shaped by editorial logic;
- a foundation that can later support richer AI workflows if useful.
It is not
- generic brochure-site development;
- a visual-design-only engagement;
- an AI content factory;
- automatically a knowledge-management transformation;
- the same service as the AI-native publishing system.
Who this is for
The strongest fit is a small or specialist organisation whose public credibility depends on expertise, research, evidence or a distinctive point of view.
- B2B founders and expert-led businesses.
- Specialist consultancies and professional-services firms.
- Research and thought-leadership organisations.
- Small editorial teams building a knowledge-led publication.
- Organisations with strong existing material but a weak public structure for presenting it.
The proof so far
Editorial Intelligence is the first full implementation: a site built around a connected discipline rather than a conventional blog hierarchy, with separate structures for frameworks, applications, narratives, services, experiments and working notes.
That is implementation evidence, not yet independent client validation. This is therefore a founding offer while the delivery process is tested outside my own system.
Founding engagement
If your organisation knows more than its website can communicate, I can help build the public structure around it.
Send me the current site, the material you are trying to organise and what you want the audience to understand. I can help determine whether you need a new website, a publishing-system layer, or both.
Discuss a website build