In a nine-week engagement, we researched, redesigned, and tested Vectrix’s cloud-security platform. The redesign took task-success to 91%, cut first-run onboarding from 74 minutes to 24, and lifted activation by 76%.
A Y Combinator startup
inventing à la carte
Vectrix built an API-driven cloud access security broker, a CASB, that gave IT and security teams one-click visibility and control across all their SaaS applications. It worked like a marketplace of à la carte scanners for tools like AWS, Google Workspace, GitHub, Salesforce, and Dropbox, surfacing issues from unauthorized access and file exposure to misconfigurations and shadow IT.
Our research found the product did not fit any existing category, so part of the job was helping Vectrix define and own a new one. When Wandr came on, Vectrix was an early-stage Y Combinator team with a powerful but deeply technical MVP, and a founding team that knew adoption depended on making that power feel simple.
A powerful platform that asked too much
of its users.
Vectrix had built real security capability. The experience around it still assumed the depth of knowledge its own engineers had.
The platform could do a lot, but it exposed that capability directly. First-time users struggled with setup, deployment, and simply reading whether the system was working.
There was no clear picture of who the product was for or where it sat in the market, which made both the roadmap and the go-to-market story harder to build.
The riskiest moments were pricing and permissions. Users were unsure what they were paying for and uneasy about granting access to their data before they had committed.
Same powerful platform.
An experience built
Drag the handle to see how the experience changed, from a generic gaming site into an institution-grade platform built to earn trust with skeptical U.S. players.
Research the buyer, redesign the product, test it
Before redesigning, we defined
Eight in-depth interviews mapped who Vectrix was really for, then five security professionals tested the redesigned prototype flow by flow.
Open-ended sessions with security professionals, clustered into patterns.
Security engineers, managers, and a risk analyst tested the prototype across eight flows.
Measured on the redesigned flows in usability testing.
Often the first security hire, technically proficient, and protective of a small team’s time. Wonders whether the tool fits a team of one and wants to know exactly what happens when you connect. “I’m the only person on the team, I would love to have something like this but it is not for a team of one.”
Lives deep in the tooling and moves fast, but hit friction at the edges: payment options and unclear permissions. “I granted access and I don’t know what I did.”
Evaluates the product through cost and outcomes rather than deep configuration, and needs the pricing model to make sense. “Why do some of the outputs cost more than others?”
Make a brand-new category
Vectrix did not fit an existing category, and its buyers ranged from very advanced engineers to less technical analysts. The redesign had to teach a new model to a wide range of fluency without dumbing the product down.
3 principlesWe framed Vectrix as an à la carte cloud-security marketplace and designed the flows so first-time users could grasp that model instead of guessing at it.
Pricing and permissions were where users hesitated, so we made cost transparent and explained exactly what access each connection granted, before asking anyone to commit.
Buyers spanned engineers, managers, and analysts, so the redesign used plain language and progressive detail that worked whether or not you lived in security tooling.
Research to prototype in about
Define the buyer, redesign the core flows, test with real users, then polish and hand off.
What the work set in
The engagement closed with a complete handoff package: page designs across 20+ unique templates, research documentation, a trust architecture framework, a design system, and an implementation plan ordered by impact.
Figures from qualitative user testing conducted during the engagement. In-market performance validation sits with MPL's internal team post-handoff.
WANDR played a critical role in shaping our product at a pivotal time. Their team brought clarity, speed, and senior-level thinking when we needed it most.
