POWEREC — Engineering trust into a complex B2B website

I led the UX audit, information architecture, visual direction, interaction design, and responsive implementation. The job was not to make the company look more technical. It was to make an already capable engineering business easier to understand and easier to trust.

POWEREC is a multidisciplinary Nigerian engineering company spanning power, MEP, automation, ELV, oil and gas, lifting systems, and EPCM. The original digital experience carried the breadth of that offer, but it did not help a technical buyer quickly understand fit, verify delivery experience, or confidently begin a project conversation.

The central design question became: how can a technical buyer move from a broad first impression to specific, relevant evidence without having to decode the organisation first?

Rather than exposing the whole organisation at once, the site reveals information in a deliberate order: establish accountability, make the service model legible, connect expertise to evidence, and then ask for a useful project brief.

The redesign was organised around a connected information architecture: Company, Capabilities, Industries, Projects, Partners, Insights, and Contact. Each layer answers a different buyer question, while shared calls to action preserve a clear route into project enquiry.

Each route has one communication job. That separation keeps the site easy to scan while allowing capabilities, industries, projects, and partners to reinforce one another.

Industrial interfaces can easily feel static or overloaded. I kept the visual system restrained, then used motion where it could improve comprehension: capability labels change the associated project imagery, active states remain visible, and transitions help visitors understand that the disciplines belong to one delivery system.

The redesigned capability experience lets a buyer recognise their immediate need without losing sight of POWEREC's multidisciplinary value. The selected discipline changes the imagery and supporting context, creating a direct relationship between service language and delivered work.

Projects are treated as records, not decorative cards. Sector, discipline, location, and scope create the context a procurement or technical audience needs to judge relevance. OEM partnerships are kept separate so a technology relationship is never mistaken for delivered client work.

The enquiry flow moves beyond a generic message box. It helps a prospective client frame the project, identify the relevant capability, and share enough detail for a productive first response. The language remains direct and technical without becoming intimidating.

Accessibility and quality assurance covered keyboard navigation, visible focus, semantic controls, image treatment, reduced-motion preferences, mobile navigation, responsive typography, and readable contrast over photography.

These checks were part of the design definition, not a final polish pass. The responsive implementation preserves the hierarchy, proof, and conversion path even as complex grids collapse onto smaller screens.