Designing launch-critical conversion flows for a two-sided service marketplace

Servidos was preparing a marketplace launch where conversion depended on clear request creation, trustworthy provider participation, and a protected offer-to-payment flow.

The product needed to reduce setup friction without weakening trust, clarify what each side needed to do next, and protect long provider flows from losing progress.

I focused on launch-critical flows across the customer and provider journey.

• Customer request creation and preview
• Provider job discovery and proposal creation
• Offer comparison and acceptance
• Payment authorization and post-acceptance communication
• Autosave and draft recovery for long provider flows

The marketplace did not only need cleaner screens. It needed better timing: asking for effort at the moment users had enough motivation, enough context, or enough trust to continue.

That meant moving some friction later, making high-trust moments more explicit, and preserving momentum through long mobile flows.

I prioritized decisions that directly affected whether users could complete the marketplace loop at launch.

The work centered on reducing unnecessary early friction, clarifying the offer system, making payment states safer to understand, and protecting provider progress across long forms.

Customers should not have to create an account before they understand the request they are about to submit.

I moved account creation later in the request flow, after customers had described and previewed their need. For providers, verification moved closer to the moment they were ready to submit offers, so the investment felt better connected to visible marketplace demand.

The offer comparison moment needed to make scope, pricing, provider identity, and trust signals easier to scan before the customer made a high-impact decision.

I structured the offer card around clear regions so customers could understand who was offering, what was included, what it would cost, and what actions were available next.

Accepting an offer was a high-trust conversion moment.

Users needed clearer expectations around what happens next: when the job is confirmed, how payment is handled, when the provider is notified, and what happens if the job is cancelled or disputed.

I recommended clearer microcopy and state communication so accepting an offer felt like a protected next step, not a loss of control.

Suggested microcopy:

The provider will not be paid until the job is confirmed.

Provider setup and proposal creation required detailed mobile forms. Losing progress during these flows could hurt provider activation.

I proposed autosave and draft recovery across long provider-side flows so providers could continue where they left off instead of losing work.

Key states included:

Saving...

Saved automatically

Draft restored

Continue where you left off

A full redesign would have improved the ideal product experience, but it risked delaying beta launch.

I helped separate the work into what needed to be solved before launch, what could improve after beta, and what should wait until the marketplace had more usage data.

This made shipping part of the design constraint.

The work created a clearer launch path for the marketplace by reducing friction at the wrong moments, clarifying high-trust states, and making provider effort safer to invest.

The resulting system gave Servidos a more deliberate foundation for request creation, offer comparison, payment authorization, and provider proposal flows.

Servidos reinforced that marketplace UX depends on sequencing as much as interface clarity.

The most important design decisions were not about adding more screens. They were about asking for effort at the right moment, protecting progress, and making trust visible when users needed it most.