Case study / Delivered in four weeks · live website

Sterillo: complex engineering, made clear

How we gave a key product its own engaging web presence within a wider brand family — with a responsive React experience, client reviews and four-week delivery.

One product story, with space of its own

Sterillo needed a distinct destination within a broader ecosystem of product brands. Its relationship with Handy Dryers remained valuable, but the product needed room to explain itself, build recognition and guide customers through a more focused journey.

We created a product-led website that keeps the parent relationship visible while giving Sterillo its own identity, pace and content structure. The experience begins with the product range and a useful question: what does this visitor need to understand before they can make a decision?

The live Sterillo desktop and mobile website presented in browser and phone frames on a JAS CMYK background.
Desktop and mobile · final public website captures presented in browser and phone frames.

Explore the live Sterillo website

Complex engineering, simply explained

The design turns a technical story into something visitors can explore. Clear product choices sit alongside an interactive chamber illustration, short explanations and routes into supporting material. The customer can move from the overall idea to the detail that matters to them.

The work was as much about the order of information as its presentation. Product function, technical evidence, applications and purchase routes each have a clear place. The interface makes room for the detail without asking every visitor to read everything at once.

The screenshots below are captures of the final public website, rather than concept mockups.

The live Sterillo interactive engineering explanation presented in a browser frame on a JAS CMYK background.
Interactive technical explanation · the live enclosed-lamp annotation presented in a browser frame.

Four weeks, with the client in the loop

Four weeks was the right cadence for this project and customer. Tight deadlines aligned the website launch with PR activity and other planned marketing, giving the work a clear purpose and a defined launch window.

The schedule still allowed time to plan the experience, represent the brand carefully and create meaningful opportunities for client feedback. Reviews ran through the project so the product story, content and working experience could be assessed together, rather than leaving feedback until the final handover.

Working versions made the discussion concrete: how the product was explained, how people moved through the range and what they needed to see before contacting sales. Feedback informed the next revision, followed by checks and an agreed launch.

The flow below summarises the delivery approach; it is not a week-by-week allocation of the programme.

THE WORKFLOW

From brand brief to launch

Four-week delivery, with client review and refinement before the agreed launch. This is an overview of the approach, not a weekly schedule.

Project flow from brand brief through product story, React experience, client reviews and agreed launch.

High-level workflow. Explore horizontally on smaller screens.

A responsive React experience

The frontend is built in React, with responsive product journeys, interactive technical content and clear navigation across the site. Product pages, sector content, news and technical resources work as part of the same customer experience.

The component-led foundation gives future progressive web app features a practical starting point. New app capabilities can be scoped around how customers use the product, while the shared brand and content structure continue to serve the website.

The live Sterillo Duo product page at mobile width, showing the product identity, introductory explanation and structured product benefits.
Mobile · product identity, introduction and benefits adapted to a narrow screen.

A defined task becomes a controlled update

Sterillo is connected to Mintbios, our engineering control plane. Ongoing page changes can begin with a simple task definition: the intended outcome, relevant context and what should be checked before the change is considered ready.

Mintbios keeps the request connected to its engineering work, review and release evidence. That gives dynamic content and page evolution a practical route through the delivery process, with technical checks and client review where required.

Simple initiation does not make production changes unreviewed. The useful distinction is that the next update can start with a clear request, while implementation and release remain controlled.

THE WORKFLOW

Ongoing updates, with control

A defined task moves through Mintbios, implementation, checks, review and release. Status and evidence remain connected to the work.

A defined task passes through Mintbios, implementation, checks, review and controlled release, with status and evidence returned.

High-level workflow. Explore horizontally on smaller screens.

Connect interest to the next useful action

The website supports two different next steps. A visitor with a requirement can send an enquiry through the React form. Server-side validation precedes the handover to the existing Handy Dryers sales endpoint, and the interface displays success or error feedback.

A visitor ready to purchase can follow the listed retailer route. Checkout, pricing and fulfilment remain with the selected retailer. The brand website focuses on helping people understand the product and reach the right commercial conversation.

The transaction diagram shows these high-level handovers. It does not expose customer records, form identifiers, credentials or private sales-system details.

THE WORKFLOW

From product interest to next action

Customer enquiries and retailer purchase journeys have different handovers. Private sales-system details are deliberately omitted.

Product exploration leads to a validated enquiry and the sales endpoint, or to a listed retailer and retailer checkout.

High-level workflow. Explore horizontally on smaller screens.

A launch with room to keep improving

The outcome is a focused product-brand presence that makes complex engineering approachable and gives customers clear next steps. The four-week delivery created the live foundation; the connected task workflow provides a way to keep refining it.

Future work can build on the same structure: additional product information, new sector journeys, content revisions and customer-experience improvements. Each change starts with a defined need and can be reviewed in the context of the product story already established.

Discuss your product-brand website