SAAS B2B · PHYSICAL SECURITY

Rhombus
Turning a complex, multi-product security platform into a clear enterprise buying experience.
ROLE
Design Lead. Led the site architecture, visual system and design direction, contributed to messaging, and directed two junior designers.
TEAM
Brandmates team (1 developer, 1 copywriter, 2 junior designers)
TIMELINE
June–October 2025
SCOPE
Full website redesign · Information architecture · Visual system · 14 industry pages
CHALLENGE
Rhombus sells an integrated platform of cameras, sensors, access control and cloud software to buyers as different as a facilities manager securing one building and a CISO evaluating architecture across forty sites. The existing website didn't reflect that. It opened with stock security photography and a generic tagline, then presented five product features as equally weighted blocks. Enterprise buyers had to read the entire page to understand what Rhombus actually was, and where they fit.
OUTCOMES
+40%
demo requests in the 6 months after launch vs. the previous 6, with ad spend held flat
62
pages rebuilt across five top-level sections
14
industry pages, each speaking to its sector
BEFORE / AFTER

BEFORE - 2024

AFTER - 2025
The redesign leads with the platform proposition and builds a clear hierarchy across the product suite. It also sharpens the path to a demo: the hero’s vague “See Rhombus in action” became two direct CTAs, See demo and Request a free trial, and every customer story now leads with a measurable result, putting proof right at the decision points.
INFORMATION ARCHITECTURE
62 pages across five top-level sections. The color split shows the organizing principle: Solutions maps to buyer identity, Products to product taxonomy, and the rest to visitor intent.

DESIGN DECISION
[ 1 ]
Let buyer identity and product taxonomy coexist instead of forcing one
The site had to serve a facilities manager evaluating cameras for one building and a CISO comparing platform architecture across forty sites. Forcing both through a single hierarchy would fail one of them. Solutions is organized by who the buyer is: industry, team, or reason to care. Products are organized by product taxonomy, because someone who already knows they need a fisheye camera wants to go straight there. The same 62 pages are reachable through whichever mental model the visitor arrives with.

[ 2 ]
Replaced fear-based stock photography with an ownable 3D product language
The original site opened with stock security photography, an image of a break-in that sold fear rather than capability. I art-directed a 3D product language on colored pedestals, defining the style, lighting and camera angles, while two junior designers produced the renders. It runs consistently across the hero, product cards, platform section and closing CTA, giving Rhombus a visual identity that belongs to them and nobody else.

[ 3 ]
Turned a feature list into an argument structure
Five alternating image-text blocks gave every capability equal weight, forcing buyers to read everything to find what mattered. I restructured the page around two platform pillars, Built to protect and Designed to adapt, each supported by three specific proof points, then positioned the four products as components of that system rather than a menu of options.

[ 4 ]
Met every buyer in their own industry
Enterprise buyers don't look for "security cameras"; they look for security in their world. I designed 14 industry pages, from education and healthcare to manufacturing and retail, each adapting the message, risks and proof points to that sector while sharing one consistent structure. They give the Solutions section its depth and send each visitor to a demo request that speaks their language.

FINAL DESIGN

Global navigation: the Solutions and Resources mega menus

Mobile navigation and pages

Product page heroes built on the 3D pedestal system
REFLECTION
The real test of an information architecture is what happens after launch. Since the site went live, Rhombus has added two new product lines, Guest Management and Rhombus Recon, and both slotted into the existing Products structure without a redesign. Separating who the buyer is from what the product is meant the site could grow on either axis: a new industry or a new product line, without touching the other.
NEXT CASE STUDY
Mashgin
Making invisible, complex checkout technology feel immediately obvious and trustworthy.
