Building a continuous user research practice in a fast-changing scaleup
Company
Ramp Network
INDUSTRY
Crypto fintech
MY ROLE
Head of Design
PROJECT TIMELINE
2024 - 2025
COMPANY SIZE
Series B scaleup
THE CONTEXT
Journey from developer-led startup to user-centered Web3 organization
When I joined Ramp, the company was focused on one thing: building a crypto on-ramp and off-ramp that worked reliably. In crypto, on-ramping means moving from fiat to crypto; off-ramping is the reverse.
Given the technical and regulatory challenges—licenses, compliance, payment integrations—the early product was naturally developer-driven. Shipping was the priority. Experience came second.
As Ramp scaled, the cracks showed. Conversion rates plateaued. Drop-offs appeared deep inside the user journey. We had all the quantitative data, but little understanding of why it happens.
I saw the need for a shift: to move from infrastructure-first thinking to real user insights. I made the case to leadership and led the creation of Ramp’s first dedicated user research practice.
The operating system behind the research practice
The Research Hub processed signals from across the company and turned them into decisions.
chapter 1: Building the first research muscle
Making invisible friction visible
Common quotes we heard again and again in exploratory user interviews.
Chapter 2: Scaling to continuous discovery
From assumptions to organized knowledge
A turning point came when Ramp brought in a new Chief Product Officer. With a background in leading top fintech products, he understood the value of user research from day one. Combined with the momentum from early interviews and Hotjar session insights, I had all the ammunition needed to secure budget and expand our efforts.
First, I hired Ramp’s first full-time User Researcher. Then, I invested in Dscout.com, a platform that gave us fast access to hundreds of crypto users for interviews and usability studies.
With the researcher on board, we launched a continuous research process:
✦ Bi-weekly exploratory interviews with Ramp users and crypto-curious testers
✦ Targeted surveys embedded into ongoing product cycles
✦ Just-in-time project based research to answer urgent business questions
✦ Falsification of ongoing product decisions by testing early ideas, wireframes, and designs before teams committed to them
Crucially, every insight was made public. We shared summaries and short video clips directly in Slack channels visible to the whole company. Research didn’t stay trapped in decks. It shaped everyday decisions across teams.
Chapter 3: Embedding research into Ramp’s DNA
From a side project to a strategic advantage
With continuous discovery in place, we focused on making insights permanent, scalable, and truly embedded across Ramp. First, we synthesized everything we had learned into five real, validated customer personas—built from over 100 interviews and nearly 1,000 survey responses.
At the same time, launched a centralized research hub in Notion, making:
✦ Interview transcriptions
✦ Survey results
✦ Insight summaries
…accessible to everyone from product managers to C-level executives.
Research wasn’t a one-off project anymore. It became a core capability—used in sprint planning, roadmap prioritization, and de-risking major product bets.
THE RESULTS
Research became a system, not just a side project
Growing a research practice at Ramp wasn’t just about running interviews, it was about changing how product decisions got made across the company.
Early on, securing budget and headcount wasn’t easy. We had to show fast wins, teach teams when and how to use research, and embed lightweight practices into their sprint cycles. Most importantly, we made user insight a shared responsibility across PMs, engineers, and leadership—not just something designers cared about.
Over 18 months, Ramp’s relationship with users fundamentally changed:
✦ Research became a standard input for sprint planning, roadmaps, and feature scoping.
✦ Personas and insights shaped strategic bets, not just UX improvements.
✦ Continuous discovery kept teams grounded in real user needs—not assumptions.
Instead of building from technical ambition outward, Ramp began building from real user problems inward, making user research a core strategic advantage.
testimonial

Michał Mazur
Research Lead at Ramp NEtwork