Skip to content

Product sense & design · Hard

Design a product that helps households in a tier-2 city find reliable plumbers and electricians.

Short answer

Clarify whether you are building for households, tradespeople or both: this is a two-sided marketplace, so supply and trust matter as much as demand. Focus first on the household's core fear of unreliable workers and unclear pricing. Propose verified profiles, upfront price ranges and booking through a familiar messaging channel, then measure completed jobs and repeat bookings.

Detailed answer

Framework

For marketplaces, run the usual product-sense steps twice, once per side, then decide which side to solve first.

  1. Goal: liquidity (jobs reliably matched) in one city.
  2. Users: households (demand) and independent tradespeople (supply).
  3. Pain points for each side.
  4. Solutions, prioritised for the constrained side.
  5. Metrics and risks.

Worked example

Households worry about no-shows, being overcharged and letting a stranger into the home. Today they rely on word of mouth and a neighbour's phone number.

Tradespeople want steady work close by and dislike haggling and unpaid site visits.

In a tier-2 city, supply is likely to be the constraint early, because good tradespeople are already busy through referrals. So the product must give them something they value: fewer wasted trips and faster payment.

Prioritised solutions:

  • Verified profiles with ID checks and reviews from completed jobs only.
  • Price ranges for common jobs (fixing a tap, replacing a switch) shown before booking, to reduce haggling.
  • Booking via a messaging app the household already uses, rather than forcing a new app download.
  • Visit fee credited against the job if the household proceeds.

Metrics: completed jobs per week, share of requests matched within a set time, repeat bookings by households, and active tradespeople retained month on month. Guardrail: complaints per hundred jobs.

Common pitfalls

  • Designing only for the household and assuming supply will appear.
  • Ignoring offline behaviour and trust norms in smaller cities.
  • Proposing complex features (live tracking, in-app chat) before solving the basics of trust and price.