Live site · Web app frontend delivered
DifferentHide
UK remote · enterprise access control · marketing + product UI · RiskTech is a separate case study under the same client
Enterprise demos cut from 3 to 1
Introduction
DifferentHide sells enterprise access-control software to buyers who cannot picture permissions, roles, and admin workflows from a spec deck alone. I lead product design across the platform (including RiskTech Control, covered in its own case study), and built the web app frontend remotely with the UK team: marketing site live today, in-product UI and React frontend delivered while the platform continues development.
Challenge
Engineers trusted the product, but enterprise buyers could not see how access control would work in their company. The marketing site still looked like a template, and permissions, roles, and admin flows lived in internal language stakeholders could not follow in a single walkthrough. The team needed production UI in code, not another round of static mocks.
Research
- Sat with UK founders and sales stakeholders through walkthroughs to see where buyers stalled: permissions language, audit questions, and admin day-to-day work.
- Compared the live marketing site against in-product screens to find where visual and narrative language diverged.
- Mapped procurement questions that never appeared in the engineering spec: who gets access, how it is audited, and what admins do every week.
Approach
- Reorganized IA from company-wide policy down to day-to-day access so security, control, and daily use read in one narrative.
- Built a shared visual system across the live marketing site and in-product surfaces so sales and product finally spoke the same language.
- Designed buyer-facing flows around the questions procurement actually asks: who gets access, how it is audited, and what admins do every week.
- Implemented the web app frontend in React so permissions, roles, and admin screens matched the Figma system in production code.
- Structured the design system for new modules so engineering could extend features without breaking layout or component patterns.
- Partnered remotely with the UK product and engineering team on weekly feedback so design decisions landed in production code, not slide decks.
Decisions
- Led with a single buyer narrative instead of separate marketing and product stories, so demos could stay on one path.
- Tried a multi-deck sales path first (marketing tour, then product tour, then admin deep-dive). Buyers stalled between decks, so we collapsed into one continuous walkthrough on the live site.
- Shipped React frontend alongside Figma so design and production UI stayed aligned while the backend continued.
- Prioritized design-system extensibility for new modules over one-off screens that would break under enterprise scope growth.
Impact
- Enterprise buyer walkthroughs shortened from three separate demos to one on the live marketing site.
- differenthide.com is live and supports active enterprise sales conversations.
- Web app UI and frontend delivered to the UK team; live screens matched the design because I built both.
Hiring or building something similar?
Send a short note with the product, timeline, and what you need. I read these myself and usually reply within one business day.