of the last 100 jobs received at least one quote
Live productImproving and iterating a live two-sided services marketplaceImproving a live two-sided marketplace
I work on product design across customer and provider journeys for Servidos, a live services marketplace in Argentina — shipping core flows, usability checks and post-launch improvements.I work on customer and provider journeys for Servidos — from core marketplace flows to post-launch improvements.
Servidos was already a live product when I joined. I did not create the original product or brand; my role has been to improve UX and product design across customer and provider journeys, working directly with the founder.
Platform traction · Sep 2026
Google Analytics + Servidos data dashboardquotes on a typical job
monthly visits
approved tradespeople
Platform metrics provide product context and are not attributed solely to my design work.
Flow changes
Moving friction closer to user intent
The customer and provider journeys raised the same question: when should we ask users to commit? I explored moving registration and verification closer to moments of intent, balancing early conversion with lead capture, trust and marketplace quality.
Product screens
Designing across both sides of the marketplace
Representative customer and provider interface explorations spanning discovery, quotes, conversations and job management.
Payment journey
Making payment states understandable
Payment authorization and payment release are different decisions. The interface needs to explain what the customer is agreeing to, when money moves and what happens after work is completed.
Post-launch
The product was live.
That changed the job.
Much of the first product was built quickly through AI-assisted coding. My work shifted toward auditing the live experience, finding production friction and working directly with the founder to ship fixes.
01 · Navigation continuity
Preserve the task the user came from.
- Problem
- Navigation sometimes removed users from the task they were already completing.
- Decision
- Keep “back” inside the active workflow rather than treating it as generic navigation.
- Concrete changes
- In the quote flow, back returns one step instead of exiting.
- From a provider profile opened from chat, back returns to that conversation rather than the message list.
- Why
- When someone is already mid-task, navigation should preserve that context instead of making them reconstruct where they were.
02 · Account state
One account can hold both marketplace roles.
- Problem
- A signed-in customer becoming a provider could be pushed into another registration path.
- Decision
- Recognize the existing account, reuse known information and add provider capability to the same account instead of creating a duplicate identity.
- Concrete changes
- Recognize the signed-in account
- Prefill known details
- Add provider mode to the same account
- Remove redundant customer/login registration paths
- Why
- The user had already established their identity. Making them start again added effort and created unnecessary account-state ambiguity.
Other shipped improvements
Transaction states
Problem: Quote, booking and completion states became visually noisy or unclear.
Changes
- Smaller quote and final-price cards
- Clearer confirm / decline hierarchy
- Accepted bookings no longer lead to a dead page
- Clearer completion actions / success states
Provider workflows
Problem: Provider agenda and job cards carried too much visual weight.
Changes
- More compact cards
- Clearer urgency / status treatment
- Normalized actions and icons
- Shorter urgent-booking settings
- Cleaner notification behaviour
- Redundant top-level navigation removed