For a while our website was organised around product items: what exists, what it does, who it suits. That works for conversion, but technical buyers need a different density of information: how the platform is organised and where the boundaries are.
Three principles
- Architecture before products: the technology overview explains the four-layer stack, product pages only describe delivery differences;
- State the boundaries: capabilities still in planning or subject to project confirmation are labelled as such;
- Reduce visual noise: whitespace, hairlines and layered diagrams replace decoration.
Structural change
The site follows five sections: products, technology, solutions, cases and insights. Technology pages explain how capability is composed; product pages explain how it is delivered.
We would rather a visitor understand where this company sits in the infrastructure chain than memorise a list of product names.
Next steps
Technical white papers, API summaries and fuller project notes will follow. Real customer cases will be published once authorisation is granted.