As founding UX engineer on a B2B sustainability platform, I redesigned a core service workflow, shifting consultants from back-stage setup to client-facing deliverables and helping the business close a large deal with a global electric vehicle manufacturer.
Problem
The platform's main workflow requires users to connect thousands of items to the right reference sources. Think of it like tagging every row in a massive spreadsheet, one by one. For small projects, this worked. It wasn't built for enterprise scale.
Through session recordings in PostHog, demo observations, and stakeholder interviews with the consulting team, I identified mapping as the service delivery bottleneck, the back-stage work gating every client engagement:
rows in the largest enterprise projects
of manual configuration per project
every row configured individually, no bulk actions
A key requirement for closing a large deal with a global electric vehicle manufacturer: the prospect needed confidence the platform could handle their scale before signing.
Key Decision
The same materials appear across dozens of projects, yet every new project required connecting them from scratch. I designed mapping presets: reusable templates that operationalise expert judgement, turning tacit consultant knowledge into shared service infrastructure the whole team can apply in seconds.
Outcome
reduction in project setup time
more projects delivered with the same team
saved annually in consultant hours freed for billable work
The workflow that was blocking enterprise adoption became a selling point in demos, landing a large deal with a global electric vehicle manufacturer. Consultants who spent days on manual setup now start delivering value immediately, turning hours of configuration into recoverable billable time.
With the bottleneck gone, consultants now spend their days on the actual deliverable: impact breakdowns, hotspot analysis, and supplier comparisons that clients pay for. The redesign rebalanced the service: hours of back-stage configuration moved into front-stage analysis.
Process
I owned research, PRD (Product Requirements Document), and design end-to-end, and contributed directly to front-end development. I built an AI-assisted design workflow on Figma MCP and custom Claude Skills to keep Figma and code in sync, smooth hand-offs, and prevent the drift that usually creeps in between design and implementation.