Pick
Pick
Designing an MVP for ride-share drivers with 13+ documents to upload
Designing an MVP for ride-share drivers with 13+ documents to upload
Designing an MVP for ride-share drivers with 13+ documents to upload
How we redesigned the MVP onboarding for a ride-share driver fintech, turning a regulatory paperwork stack into a flow drivers could complete on their own.
How we redesigned the MVP onboarding for a ride-share driver fintech, turning a regulatory paperwork stack into a flow drivers could complete on their own.
How we redesigned the MVP onboarding for a ride-share driver fintech, turning a regulatory paperwork stack into a flow drivers could complete on their own.
Industry
Industry
Ride-sharing
Mobility
Growth stage
Growth stage
Bootstrapped
Bootstrapped
Services
Services
Strategy & Discovery
MVP Definition
User Testing
Product Design
Strategy & Discovery
MVP Definition
User Testing
Product Design
Most of our work starts with a product that's already shipping. This one didn't. Pick came to us with a hard problem: ride-share drivers in Romania need to upload 13+ regulated documents to get licensed. We had five weeks to define an MVP that wouldn't drown them in paperwork, and to test it before development started.
Most of our work starts with a product that's already shipping. This one didn't. Pick came to us with a hard problem: ride-share drivers in Romania need to upload 13+ regulated documents to get licensed. We had five weeks to define an MVP that wouldn't drown them in paperwork, and to test it before development started.
Most of our work starts with a product that's already shipping. This one didn't. Pick came to us with a hard problem: ride-share drivers in Romania need to upload 13+ regulated documents to get licensed. We had five weeks to define an MVP that wouldn't drown them in paperwork, and to test it before development started.
5 weeks
5 weeks
5 weeks
Discovery to dev-ready
Discovery to dev-ready
Discovery to dev-ready
13+ docs
13+ docs
13+ docs
Compressed into one flow
Compressed into one flow
Compressed into one flow
5 drivers
5 drivers
5 drivers
Tested before any code
Tested before any code
Tested before any code
the situation
A regulated, high-friction signup that had to feel simple
Pick is a personal assistant for ride-share drivers in Romania. From the moment a driver opens the app, it guides them through getting licensed for Bolt and Uber. Then it sticks around as a hub for financial tracking, exclusive discounts, and the small operational decisions drivers make every day.
Pick is a personal assistant for ride-share drivers in Romania. From the moment a driver opens the app, it guides them through getting licensed for Bolt and Uber. Then it sticks around as a hub for financial tracking, exclusive discounts, and the small operational decisions drivers make every day.
The hard part: getting licensed in Romania means submitting 13+ different documents. Identity papers, vehicle papers, insurance, regulatory forms. Most drivers are not particularly tech-savvy, and most have already given up on at least one app that asked too much of them.
The hard part: getting licensed in Romania means submitting 13+ different documents. Identity papers, vehicle papers, insurance, regulatory forms. Most drivers are not particularly tech-savvy, and most have already given up on at least one app that asked too much of them.
So Pick had a real problem before they had a single user. If the onboarding flow felt overwhelming, drivers would abandon it, and Pick would never get a chance to prove the rest of the product. This had to be designed and validated before any code was written, not after.
So Pick had a real problem before they had a single user. If the onboarding flow felt overwhelming, drivers would abandon it, and Pick would never get a chance to prove the rest of the product. This had to be designed and validated before any code was written, not after.
13+ documents to upload before day one
Identity, vehicle registration, insurance, regulatory paperwork. Every driver had to clear all of it before they could earn a single fare.
A user base that's not the typical app user
Ride-share drivers don't read tutorials. The flow had to be obvious enough that someone could complete it the first time, on a phone, between fares.
No product to learn from yet
No analytics, no support tickets, no behaviour data. Every assumption had to be tested with real drivers, not pulled from product instinct.
Engineering capacity that couldn't be wasted
A small team building from zero. Every flow that shipped had to be the right one. There was no budget to ship and rebuild.
the situation
the situation
Powerful features that nobody could find
Powerful features that nobody could find
Powerful features that nobody could find
Bliro is an on-device AI meeting assistant that integrates with all meeting tools without relying on bots. It's highly customizable, users can create different AI notes for various meetings and automatically send them to Salesforce, HubSpot, Slack, and more.
Bliro is an on-device AI meeting assistant that integrates with all meeting tools without relying on bots. It's highly customizable, users can create different AI notes for various meetings and automatically send them to Salesforce, HubSpot, Slack, and more.
Bliro is an on-device AI meeting assistant that integrates with all meeting tools without relying on bots. It's highly customizable, users can create different AI notes for various meetings and automatically send them to Salesforce, HubSpot, Slack, and more.
The product grew organically over time. Features were added in an 80/20 fashion, which left many powerful capabilities hidden in the platform. Users didn't know they existed or couldn't figure out how to use them.
The product grew organically over time. Features were added in an 80/20 fashion, which left many powerful capabilities hidden in the platform. Users didn't know they existed or couldn't figure out how to use them.
The product grew organically over time. Features were added in an 80/20 fashion, which left many powerful capabilities hidden in the platform. Users didn't know they existed or couldn't figure out how to use them.
In some cases, users couldn't even find their way around the platform after being personally onboarded. The design itself didn't look professional, and there was no unified design language across web, mobile, and desktop.
In some cases, users couldn't even find their way around the platform after being personally onboarded. The design itself didn't look professional, and there was no unified design language across web, mobile, and desktop.
In some cases, users couldn't even find their way around the platform after being personally onboarded. The design itself didn't look professional, and there was no unified design language across web, mobile, and desktop.
Product didn't match the team's ambition
13+ documents to upload before day one
Bliro had just raised a €2.8m seed round and needed a product that reflected the quality of the technology behind it.
Identity, vehicle registration, insurance, regulatory paperwork. Every driver had to clear all of it before they could earn a single fare.
Identity, vehicle registration, insurance, regulatory paperwork. Every driver had to clear all of it before they could earn a single fare.
Product didn't match the team's ambition
A user base that's not the typical app user
Bliro had just raised a €2.8m seed round and needed a product that reflected the quality of the technology behind it.
Ride-share drivers don't read tutorials. The flow had to be obvious enough that someone could complete it the first time, on a phone, between fares.
Ride-share drivers don't read tutorials. The flow had to be obvious enough that someone could complete it the first time, on a phone, between fares.
Product didn't match the team's ambition
No product to learn from yet
Bliro had just raised a €2.8m seed round and needed a product that reflected the quality of the technology behind it.
No analytics, no support tickets, no behaviour data. Every assumption had to be tested with real drivers, not pulled from product instinct.
No analytics, no support tickets, no behaviour data. Every assumption had to be tested with real drivers, not pulled from product instinct.
Product didn't match the team's ambition
Engineering capacity that couldn't be wasted
Bliro had just raised a €2.8m seed round and needed a product that reflected the quality of the technology behind it.
A small team building from zero. Every flow that shipped had to be the right one. There was no budget to ship and rebuild.
A small team building from zero. Every flow that shipped had to be the right one. There was no budget to ship and rebuild.
"We engaged with Durran to help us create a smooth onboarding flow for our customers while navigating the data that needed to be uploaded."
"We engaged with Durran to help us create a smooth onboarding flow for our customers while navigating the data that needed to be uploaded."
"We engaged with Durran to help us create a smooth onboarding flow for our customers while navigating the data that needed to be uploaded."
Tudor Beiu
Tudor Beiu
CEO, Pick
CEO, Pick
the results
the results
What changed before a single user signed up
What changed before a single user signed up
What changed before a single user signed up
When the framework runs at the pre-launch stage, the outcome is confidence. Pick walked into development knowing the flow worked, knowing where it broke, and knowing what the design system looked like.
When the framework runs at the pre-launch stage, the outcome is confidence. Pick walked into development knowing the flow worked, knowing where it broke, and knowing what the design system looked like.
When the framework runs at the pre-launch stage, the outcome is confidence. Pick walked into development knowing the flow worked, knowing where it broke, and knowing what the design system looked like.
MVP validated with drivers
MVP validated with drivers
MVP validated with drivers
Onboarding flow tested
Onboarding flow tested
Onboarding flow tested
5 weeks
5 weeks
5 weeks
Dev-ready
Dev-ready
Dev-ready
"We identified and addressed process issues, leading to smoother user experiences and valuable early feedback on our product. We're delighted with the meticulous approach throughout the project."
"We identified and addressed process issues, leading to smoother user experiences and valuable early feedback on our product. We're delighted with the meticulous approach throughout the project."
"We identified and addressed process issues, leading to smoother user experiences and valuable early feedback on our product. We're delighted with the meticulous approach throughout the project."
Tudor Beiu
Tudor Beiu
CEO
CEO
how we got there
how we got there
Three phases. Five weeks.
A signup tested before launch.
Three phases. Five weeks. A signup tested before launch.
diagnose
diagnose
diagnose
What's the actual job a driver needs to get done?
What's the actual job a driver needs to get done?
What's the actual job a driver needs to get done?
We ran a discovery workshop with the founding team. Mapped the competitor landscape, defined the user persona, sketched the customer journey, and surfaced the assumptions baked into the original product idea. The goal: agree on what we were really designing for before anyone opened Figma.
We ran a discovery workshop with the founding team. Mapped the competitor landscape, defined the user persona, sketched the customer journey, and surfaced the assumptions baked into the original product idea. The goal: agree on what we were really designing for before anyone opened Figma.
We ran a discovery workshop with the founding team. Mapped the competitor landscape, defined the user persona, sketched the customer journey, and surfaced the assumptions baked into the original product idea. The goal: agree on what we were really designing for before anyone opened Figma.
define
define
define
What's the smallest version of this that's worth testing?
What's the smallest version of this that's worth testing?
What's the smallest version of this that's worth testing?
Researched and sketched concepts with the founding and development teams, balancing user needs with business model and the legal constraints of Romanian licensing. Built a prototype, then tested it with five real ride-share drivers, focusing on the document upload flow where things were most likely to break.
Researched and sketched concepts with the founding and development teams, balancing user needs with business model and the legal constraints of Romanian licensing. Built a prototype, then tested it with five real ride-share drivers, focusing on the document upload flow where things were most likely to break.
Researched and sketched concepts with the founding and development teams, balancing user needs with business model and the legal constraints of Romanian licensing. Built a prototype, then tested it with five real ride-share drivers, focusing on the document upload flow where things were most likely to break.
refine
refine
refine
What do engineers need to ship without ambiguity?
What do engineers need to ship without ambiguity?
What do engineers need to ship without ambiguity?
Translated validated flows into the production design and a component library Pick could build on. Prepared development-ready assets so the engineering team could move from concept to implementation without re-litigating decisions that had already been made.
Translated validated flows into the production design and a component library Pick could build on. Prepared development-ready assets so the engineering team could move from concept to implementation without re-litigating decisions that had already been made.
Translated validated flows into the production design and a component library Pick could build on. Prepared development-ready assets so the engineering team could move from concept to implementation without re-litigating decisions that had already been made.
where we start
where we start
Let's find out where users get stuck, and what to fix first.
Let's find out where users get stuck,
and what to fix first.
Let's find out where users get stuck,
and what to fix first.
We'll look at how users experience your product, identify the biggest friction points, and outline what to fix first.
We'll look at how users experience your product, identify the biggest friction points, and outline what to fix first.
We'll look at how users experience your product, identify the biggest friction points, and outline what to fix first.
more case studies
more case studies
Different products.
Same pattern of outcomes.
Different products.
Same pattern of outcomes.
Different products.
Same pattern of outcomes.
Product Design Studio
for growth-stage SaaS teams
© Durran 2026
Product Design Studio
for growth-stage SaaS teams
© Durran 2026
Product Design Studio
for growth-stage SaaS teams
© Durran 2026
Product Design Studio
for growth-stage SaaS teams
© Durran 2026