Information architecture
Technical services organised for business audiences.
Anonymised engagement · Transport and Infrastructure · Client identity withheld
A confidential corporate website engagement improving how a transport technology provider presents complex services, technical expertise and international experience.
Modernise Your Corporate WebsiteCapabilities described in this engagement.
Technical services organised for business audiences.
Consistent content across screen sizes.
Content and URL continuity in the delivery scope.
An international transport technology provider needed a corporate website that made its engineering capabilities accessible to commercial and technical audiences. Its existing presentation needed clearer information structure, more consistent design, better responsive behaviour and attention to page performance.
For a reader assessing a technical supplier, those details matter together. They need to understand what the company does, where its expertise applies and how to take a relevant question further. A website should help them make that assessment without losing the technical substance.
Our engagement covered the corporate website: how technical services were organised, described and presented to visitors. The customer’s underlying transport and tolling systems were outside our scope.
We organised service information around what a prospective customer needed to understand. Technical service pages had to connect each capability with its application, so a reader could follow the explanation without piecing together fragments from across the site. Corporate positioning and content restructuring supported that navigation.
For example, on a technical company’s website, a commercial reader might first need to establish whether a service addresses their requirement. An engineer reviewing the same page may need a more detailed explanation of the capability. Clear headings and a considered reading order help both readers find their starting point.
Executive-profile presentation also formed part of the corporate information design, bringing the presentation of people and expertise into the wider site structure. We have kept individual names, project locations and identifying references out of this account to preserve the customer’s confidentiality.
Page design connected headings, content blocks and navigation patterns across the site. Responsive corrections addressed how the same information worked on smaller screens, where dense content and large imagery can make a service explanation harder to follow.
Image optimisation and modern delivery formats formed part of the performance work. Readable text, appropriate image dimensions and a stable layout mattered alongside the visuals themselves: a visitor on a phone still needs to reach the explanation and find the next step. These were practical website improvements, with the technical content remaining central to the design.
The engagement included production migration and deployment validation. Moving a corporate website brings its content, assets and navigation into a new live setting; the release needs checking as a website people will use, as well as a deployment that completes successfully.
If you are planning a similar move, start with the service pages and the route from those pages to contact. List the existing URLs you need to preserve or redirect, who can approve technical wording and who will check that enquiries arrive. This gives your team concrete things to check at release. These are planning suggestions for a future project, rather than a list of confirmed activities from this engagement.
The delivered website work brought together a modernised corporate presentation, restructured technical content, responsive corrections, optimised imagery and a validated production migration. It addressed how the business presented its expertise online. We do not publish unverified PageSpeed scores, search-ranking gains or enquiry increases for this project.
If your own technical website has become difficult to explain or navigate, bring us the current sitemap, a few representative service pages and the questions customers ask before contacting you. Those materials help us discuss what needs clearer wording, what needs a different place in the site and what needs design or performance work. They also help keep the website brief clear about the technology being presented and the systems that sit outside it.
Create a responsive business website design around a clear offer, useful content, consistent page layouts and a practical customer and publishing journey.
Review a customer or staff task through UX design, content structure, prototypes and usability questions, with an explicit research scope and design handover.
Plan a careful website redesign that protects valuable content, clarifies customer journeys and replaces outdated implementation with a maintainable foundation.
Bring positioning, content, design and development together in a business website built around useful customer journeys.
How should a technical B2B website organise services for buyers? Connect capability, application, evidence and enquiry around distinct visitor questions.
Tell us what you are working towards. We’ll help you find a practical next step.