Skip to content
Apoliums

WorkIndustrial technologyMirion

One web platform for a group made of many acquired brands

Apoliums delivered web development for Mirion, a technology group whose industrial and medical arms carry dozens of product brands, a platform where a visitor can arrive by product name, by brand, or by the problem they are trying to solve.

Client
Mirion
Sector
Industrial technology
Services
Web development
Mirion, Industrial technology platform built by Apoliums

What was the problem?

Mirion is not one product line. It is an industrial business and a medical business, each holding brands that arrived through acquisition, each with its own catalogue, documentation and installed base. The web platform has to present that as one company without flattening brands the customers already know by name.

  • Two visitors arrive with opposite starting points: one already knows a product or brand name, the other only knows the problem they have to solve.
  • Acquired brands carry existing customer recognition, so folding them into a single voice loses the equity, and leaving them as separate microsites loses the group.
  • A technical catalogue is only useful with its documentation attached, and documentation is what goes stale first.
  • Existing customers come to the site for support far more often than prospects come to it to buy.

How Apoliums approached it.

Treat products, brands and solutions as three views of one catalogue rather than three sections of a website, and give support its own front door.

  1. Make the product the record, the brand a facet

    Every product carries its brand, its business unit and its applications as attributes. Products, Our Brands and Solutions are then three ways of querying the same catalogue instead of three content trees to keep in sync.

  2. Give the problem-first visitor a route in

    Solutions pages start from the application rather than the part number, and land the visitor on the products that serve it. Nobody has to already know the catalogue to get through the site.

  3. Keep documentation attached to the thing it documents

    Datasheets, manuals and resources hang off the product record, so a document cannot drift away from the product it belongs to or survive after that product is retired.

  4. Treat support as a destination, not a footer link

    Support and contact are top-level navigation because the majority of returning traffic is an existing customer with an installed device, not a prospect reading a brochure.

What was delivered.

  • Product catalogue spanning the industrial and medical businesses
  • Brand directory presenting acquired brands inside one group identity
  • Solutions pages routing by application rather than by product name
  • Documentation and resources attached to individual product records
  • Site-wide search across products, brands and content
  • Support and contact routing surfaced in primary navigation

What changed after launch.

One catalogue now serves the visitor who knows the part number and the visitor who only knows the problem.

  • A visitor who knows the part number and a visitor who only knows the problem both reach the same product page.

  • Acquired brands keep their names while sitting inside one group platform.

  • Documentation stays attached to the product record instead of living in a separate downloads pile.

  • Existing customers reach support without going through the sales path first.

More from the same shelf.

All case studies
Prefero, SaaS product interface built by Apoliums

SaaSSaaS development

Prefero

An AI marketing manager that gets local businesses found on Google and in AI search

  • SaaS development
  • AI development
  • AI automation
A working desk in the Apoliums studio, mid-build

Have a system that needs building?

Send the problem, not a specification. Apoliums replies with the shape of a first build, what it would cost to find out if it works, and who would do the work.

Studio
Indore, Madhya Pradesh
Reply time
One working day