Redesigned Industries Page
The Industries page has been rebuilt with a consistent structure across every sector — clearer use cases, richer content, and a new video-driven hero.
The old Industries page was a collection of loosely related sections with no consistent structure. Each sector looked different, answered different questions, and made it hard to compare. We rebuilt it from scratch.
The new version follows a single template across every industry: a video-driven hero, three use cases, key metrics, and a CTA. Same depth, same rhythm, every time.
What changed
Consistent section structure
Every industry now answers three questions in the same order:
- What is the problem? — a customer pain point that’s costing the business
- How does GLUCOSE solve it? — the specific agent behaviour and workflow
- What does success look like? — a metric, a result, or a customer outcome
This makes it easier for a visitor to scan across sectors and understand the platform’s depth without reading every word.
Video-driven hero
Each industry section now opens with a 6-second background video — no audio, loops seamlessly. An animated overlay sits on top, timed to the clip, so the motion and the message land together.
The goal wasn’t to make the page look impressive. It was to make the first 6 seconds do the work of explaining what GLUCOSE actually does in that industry.
Two new sectors added
| Sector | Tagline |
|---|---|
| Consumer Appliances | Turn unboxing into brand loyalty |
| Industrial | Autonomous AI support for equipment and fleets |
These join the existing primary sectors: Automotive, Healthcare, Financial Services, Retail, Telecoms, and Real Estate.
Fixes
- Removed inconsistent section depths across different industry entries
- Standardised copy length and heading hierarchy across all sectors
- Fixed a spacing regression on mobile that caused the hero text to overlap the nav
What’s coming next
The video assets for the new sectors are being finalised. Once those are in, each industry hero will have its own clip rather than sharing the default one.
We’re also exploring pulling real customer metrics into the stats row — right now the numbers are illustrative. That requires a content sign-off process, which is in progress.
Design by Christophe. Implementation by the engineering team.