Building a continuous user research practice in a fast-changing scaleup

In less than a year I built Ramp’s first research engine, turning instinct-led decisions into a shared understanding of user behavior across product, growth and leadership teams.

In less than a year I built Ramp’s first research engine, turning instinct-led decisions into a shared understanding of user behavior across product, growth and leadership teams.

Company

Ramp Network

INDUSTRY

Crypto fintech

MY ROLE

Head of Design

PROJECT TIMELINE

2024 - 2025

COMPANY SIZE

Series B scaleup

User research artifacts presented on a canvas with a post it with a lightbulb in the middle
User research artifacts presented on a canvas with a post it with a lightbulb in the middle
User research artifacts presented on a canvas with a post it with a lightbulb in the middle

Executive Summary

Executive Summary

Executive Summary

As Ramp scaled, instinct stopped being enough. Continuous research helped us find new opportunities and avoid costly missteps.

As Ramp scaled, instinct stopped being enough. Continuous research helped us find new opportunities and avoid costly missteps.

As Ramp scaled, instinct stopped being enough. Continuous research helped us find new opportunities and avoid costly missteps.

In a year I built Ramp’s first user research function to replace gut feeling decisions with user-driven insights

In a year I built Ramp’s first user research function to replace gut feeling decisions with user-driven insights

In a year I built Ramp’s first user research function to replace gut feeling decisions with user-driven insights

In a year I built Ramp’s first user research function to replace gut feeling decisions with user-driven insights

In a year I built Ramp’s first user research function to replace gut feeling decisions with user-driven insights

Designed a hybrid model of continuous and project-based research tailored to a high-speed startup environment

Designed a hybrid model of continuous and project-based research tailored to a high-speed startup environment

Designed a hybrid model of continuous and project-based research tailored to a high-speed startup environment

Designed a hybrid model of continuous and project-based research tailored to a high-speed startup environment

Designed a hybrid model of continuous and project-based research tailored to a high-speed startup environment

Stopped teams from shipping the wrong features by validating ideas before build

Stopped teams from shipping the wrong features by validating ideas before build

Stopped teams from shipping the wrong features by validating ideas before build

Stopped teams from shipping the wrong features by validating ideas before build

Stopped teams from shipping the wrong features by validating ideas before build

Uncovered usability blockers that were hurting conversion and trust

Uncovered usability blockers that were hurting conversion and trust

Uncovered usability blockers that were hurting conversion and trust

Uncovered usability blockers that were hurting conversion and trust

Uncovered usability blockers that were hurting conversion and trust

Influenced OKRs, roadmap priorities, and copy with evidence instead of opinions

Influenced OKRs, roadmap priorities, and copy with evidence instead of opinions

Influenced OKRs, roadmap priorities, and copy with evidence instead of opinions

Influenced OKRs, roadmap priorities, and copy with evidence instead of opinions

Influenced OKRs, roadmap priorities, and copy with evidence instead of opinions

Made research a habit inside squads—fast, visible, and impossible to ignore

Made research a habit inside squads—fast, visible, and impossible to ignore

Made research a habit inside squads—fast, visible, and impossible to ignore

Made research a habit inside squads—fast, visible, and impossible to ignore

Made research a habit inside squads—fast, visible, and impossible to ignore

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.

A graph presenting sources of product insights, research hub as a place which transforms them into reasearch driven outputs
A graph presenting sources of product insights, research hub as a place which transforms them into reasearch driven outputs
A graph presenting sources of product insights, research hub as a place which transforms them into reasearch driven outputs

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

In Ramp’s early days, strong instincts from the founders led to solid product decisions. But as the company grew, the intuition didn't stretch to every team or user journey. We needed a systematic way to understand users, not just rely on gut feeling.

At that point, Ramp had no structured user research. I knew building a full program would require trust and quick wins, so I started small with onboarding interviews.

Many new employees had never used Ramp before joining. Some, even after months on the job, still didn’t fully understand the product. That alone revealed a deeper issue. I teamed up with the People team and added live research sessions to onboarding. New hires completed their first transaction while thinking out loud. It was simple, but the patterns we uncovered got leadership’s attention and opened the door to a proper research practice.

At the same time, I started reviewing hundreds of session recordings using Hotjar. There was some early resistance, especially from engineering and early team members, who were concerned about performance and user privacy. But once they saw the insights, the hesitation disappeared. We uncovered dozens of edge cases we didn’t even know existed. On their own, these issues seemed small. But stacked together, they had a serious impact on conversion. Fixing them led to the most successful quarter in the company’s history in terms of conversion gains.

In Ramp’s early days, strong instincts from the founders led to solid product decisions. But as the company grew, the intuition didn't stretch to every team or user journey. We needed a systematic way to understand users, not just rely on gut feeling.

At that point, Ramp had no structured user research. I knew building a full program would require trust and quick wins, so I started small with onboarding interviews.

Many new employees had never used Ramp before joining. Some, even after months on the job, still didn’t fully understand the product. That alone revealed a deeper issue. I teamed up with the People team and added live research sessions to onboarding. New hires completed their first transaction while thinking out loud. It was simple, but the patterns we uncovered got leadership’s attention and opened the door to a proper research practice.

At the same time, I started reviewing hundreds of session recordings using Hotjar. There was some early resistance, especially from engineering and early team members, who were concerned about performance and user privacy. But once they saw the insights, the hesitation disappeared.

We uncovered dozens of edge cases we didn’t even know existed. On their own, these issues seemed small. But stacked together, they had a serious impact on conversion. Fixing them led to the most successful quarter in the company’s history in terms of conversion gains.

USER INSIGHT #1

New users were overwhelmed by wallets

Less technical users didn’t know how to set up a crypto
wallet or which one to choose from the dozens available
on the market. This was a major barrier to even starting
a transaction.

USER INSIGHT #1

New users were overwhelmed by wallets

Less technical users didn’t know how to set up a crypto
wallet or which one to choose from the dozens available
on the market. This was a major barrier to even starting
a transaction.

USER INSIGHT #1

New users were overwhelmed by wallets

Less technical users didn’t know how to set up a crypto
wallet or which one to choose from the dozens available
on the market. This was a major barrier to even starting
a transaction.

USER INSIGHT #1

New users were overwhelmed by wallets

Less technical users didn’t know how to set up a crypto
wallet or which one to choose from the dozens available
on the market. This was a major barrier to even starting
a transaction.

USER INSIGHT #1

New users were overwhelmed by wallets

Less technical users didn’t know how to set up a crypto
wallet or which one to choose from the dozens available
on the market. This was a major barrier to even starting
a transaction.

USER INSIGHT #2

Users were getting stuck in edge cases we didn’t know existed

In some risk profiles or wallet flows, users would land on the Order Summary screen with the “Buy” button completely inactive, without explanation. What looked like drop-off in the data was actually frustration and confusion caused by broken logic or silent blockers. Fixing these edge cases significantly boosted conversions.

USER INSIGHT #2

Users were getting stuck in edge cases we didn’t know existed

In some risk profiles or wallet flows, users would land on the Order Summary screen with the “Buy” button completely inactive, without explanation. What looked like drop-off in the data was actually frustration and confusion caused by broken logic or silent blockers. Fixing these edge cases significantly boosted conversions.

USER INSIGHT #2

Users were getting stuck in edge cases we didn’t know existed

In some risk profiles or wallet flows, users would land on the Order Summary screen with the “Buy” button completely inactive, without explanation. What looked like drop-off in the data was actually frustration and confusion caused by broken logic or silent blockers. Fixing these edge cases significantly boosted conversions.

USER INSIGHT #2

Users were getting stuck in edge cases we didn’t know existed

In some risk profiles or wallet flows, users would land on the Order Summary screen with the “Buy” button completely inactive, without explanation. What looked like drop-off in the data was actually frustration and confusion caused by broken logic or silent blockers. Fixing these edge cases significantly boosted conversions.

USER INSIGHT #2

Users were getting stuck in edge cases we didn’t know existed

In some risk profiles or wallet flows, users would land on the Order Summary screen with the “Buy” button completely inactive, without explanation. What looked like drop-off in the data was actually frustration and confusion caused by broken logic or silent blockers. Fixing these edge cases significantly boosted conversions.

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.

USER INSIGHT #3

Payments were failing silently

Users with wallets expected to pay by card, but many crypto transactions were blocked by their banks. They weren’t always informed why—which created confusion and mistrust.

USER INSIGHT #3

Payments were failing silently

Users with wallets expected to pay by card, but many crypto transactions were blocked by their banks. They weren’t always informed why—which created confusion and mistrust.

USER INSIGHT #3

Payments were failing silently

Users with wallets expected to pay by card, but many crypto transactions were blocked by their banks. They weren’t always informed why—which created confusion and mistrust.

USER INSIGHT #3

Payments were failing silently

Users with wallets expected to pay by card, but many crypto transactions were blocked by their banks. They weren’t always informed why—which created confusion and mistrust.

USER INSIGHT #3

Payments were failing silently

Users with wallets expected to pay by card, but many crypto transactions were blocked by their banks. They weren’t always informed why—which created confusion and mistrust.

USER INSIGHT #4

Trust meant very different things
to different users

Newcomers trusted clean branding, mobile apps, and known institutions. Crypto natives trusted Discord groups, wallet UX, and peer validation. Interestingly, beginners often perceived native mobile apps as more secure than web-based experiences.

USER INSIGHT #4

Trust meant very different things
to different users

Newcomers trusted clean branding, mobile apps, and known institutions. Crypto natives trusted Discord groups, wallet UX, and peer validation. Interestingly, beginners often perceived native mobile apps as more secure than web-based experiences.

USER INSIGHT #4

Trust meant very different things
to different users

Newcomers trusted clean branding, mobile apps, and known institutions. Crypto natives trusted Discord groups, wallet UX, and peer validation. Interestingly, beginners often perceived native mobile apps as more secure than web-based experiences.

USER INSIGHT #4

Trust meant very different things
to different users

Newcomers trusted clean branding, mobile apps, and known institutions. Crypto natives trusted Discord groups, wallet UX, and peer validation. Interestingly, beginners often perceived native mobile apps as more secure than web-based experiences.

USER INSIGHT #4

Trust meant very different things
to different users

Newcomers trusted clean branding, mobile apps, and known institutions. Crypto natives trusted Discord groups, wallet UX, and peer validation. Interestingly, beginners often perceived native mobile apps as more secure than web-based experiences.

We adapted our research to the stage of the product,
always focused on answering the next most important question.

We adapted our research to the stage of the product, always focused on answering the next most important question.

A table which present which research methods were used, when they were used and what was the benefit of using them
A table which present which research methods were used, when they were used and what was the benefit of using them
A table which present which research methods were used, when they were used and what was the benefit of using them
A table which present which research methods were used, when they were used and what was the benefit of using them

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.

Customer personas based on user resaerch
Customer personas based on user resaerch
Customer personas based on user resaerch
Customer personas based on user resaerch
Customer personas based on user resaerch
Customer personas based on user resaerch
Customer personas based on user resaerch
Customer personas based on user resaerch
Customer personas based on user resaerch
Customer personas based on user resaerch
Customer personas based on user resaerch
Customer personas based on user resaerch
Customer personas based on user resaerch
Customer personas based on user resaerch
Customer personas based on user resaerch
Customer personas based on user resaerch
Customer personas based on user resaerch
Customer personas based on user resaerch
Customer personas based on user resaerch
Customer personas based on user resaerch

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 result was more than satisfactory.

The result was more than satisfactory.

The result was more than satisfactory.

Research shifted from a nice-to-have to a strategic layer of Ramp’s product development process, fueling decisions across every team 💪

Research shifted from a nice-to-have to a strategic layer of Ramp’s product development process, fueling decisions across every team 💪

Research shifted from a nice-to-have to a strategic layer of Ramp’s product development process, fueling decisions across every team 💪

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.

Organizational change in Ramp Network
Organizational change in Ramp Network
Organizational change in Ramp Network
Organizational change in Ramp Network
Organizational change in Ramp Network
Research adoption in Ramp Network
Research adoption in Ramp Network
Research adoption in Ramp Network
Research adoption in Ramp Network
Research adoption in Ramp Network
What Ramp Network avoided thanks to the research
What Ramp Network avoided thanks to the research
What Ramp Network avoided thanks to the research
What Ramp Network avoided thanks to the research
What Ramp Network avoided thanks to the research

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

“Working with Peter was a once-in-a-career opportunity. We built a research practice from scratch that transformed how the company made decisions.

 Peter gave me the trust and structure to build Ramp’s first research function from the ground up. He made research visible, actionable, and core to how teams worked.”

“Working with Peter was a once-in-a-career opportunity. We built a research practice from scratch that transformed how the company made decisions.

 Peter gave me the trust and structure to build Ramp’s first research function from the ground up. He made research visible, actionable, and core to how teams worked.”

“Working with Peter was a once-in-a-career opportunity. We built a research practice from scratch that transformed how the company made decisions.

 Peter gave me the trust and structure to build Ramp’s first research function from the ground up. He made research visible, actionable, and core to how teams worked.”

“Working with Peter was a once-in-a-career opportunity. We built a research practice from scratch that transformed how the company made decisions.

 Peter gave me the trust and structure to build Ramp’s first research function from the ground up. He made research visible, actionable, and core to how teams worked.”

Michał Mazur portrait

Michał Mazur

Research Lead at Ramp NEtwork

0 → 1 → 100

I bet we can build
great things together

Whether you’re building your first product or scaling your team,
I’d love to hear what you’re working on.

Portrait of Peter Kmita

Copyrights © 2025 Peter Kmita

Located in Warsaw, Poland

0 → 1 → 100

I bet we can build
great things together

Whether you’re building your first product or scaling your team, I’d love to hear what you’re working on.

Portrait of Peter Kmita

Copyrights © 2025 Peter Kmita

Located in Warsaw, Poland

0 → 1 → 100

I bet we can build
great things together

Whether you’re building your first product or scaling your team,
I’d love to hear what you’re working on.

Portrait of Peter Kmita

Copyrights © 2025 Peter Kmita

Located in Warsaw, Poland

0 → 1 → 100

I bet we can build
great things together

Whether you’re building your first product or scaling your team,
I’d love to hear what you’re working on.

Portrait of Peter Kmita

Copyrights © 2025 Peter Kmita

Located in Warsaw, Poland