The problem
Small jobs, like a cook for a family party, a gardener for the weekend, or an electrician for a quick repair, are usually found through word of mouth or a Facebook post. Clients can't easily check who they're letting into their home, rates are negotiated from scratch every time, and nothing protects either side if the job falls through.
Workers have the opposite problem: no steady place to find gigs, no way to show their track record, and no guarantee they'll be paid for the work they do.
Designing for trust
In a marketplace like this, the real problem isn't finding a worker. It's deciding to trust a stranger with your home, or trusting a stranger to pay you. So every screen was judged on one question: what does this person need to see before they feel safe taking the next step? That shaped three principles:
Verify before you show. Workers are checked before clients can book them, and a verified badge sits on their profile photo.
Put the deciding facts on the first screen. Distance, experience and hourly rate appear in the list itself, so clients can compare without opening every profile.
Make money predictable. Rates, fees and payment stages are visible up front, never added at the end.
Two sides, one app
TrabaWHO serves two people with different goals: clients who need a job done, and service providers looking for work. Instead of making one interface do both, a single question after onboarding splits the app in two: find a job, or find someone for the job. Each side then only shows what that person needs.
Sign-up includes a profile setup with document uploads (a valid government ID, CV, and police clearance). It adds steps for workers, but it's the step that makes the whole marketplace believable for clients, so it's placed at sign-up instead of being optional later.

Hiring a worker
Clients browse job profiles sorted by distance, because for on-demand work, nearby usually means available today. Each card leads with the role in large type, then the location with distance in kilometres, a few highlights and the hourly rate, so the list doubles as a comparison table. Search, with voice input, and sort and filter controls sit above the list for clients who know exactly what they want.
A worker's profile is ordered like a short interview: who they are and their rating, then highlights such as certificates and awards, then skills, experience, a portfolio and feedback from past clients. Chat and Report sit right under the name, so a client can ask a question, or flag a problem, before committing.
Booking fits on one screen: pick the dates on a calendar, set start and end times, name the job, and set an offered rate. Letting the client propose the rate matches how small jobs are negotiated locally, while the worker's listed rate stays visible as the reference point.

Paying and tracking the job
Payment is split into a 50% down payment and the remaining balance, with the commission shown in the invoice so there are no surprises. Clients can pay with the TrabaWHO wallet, GCash, Maya, bank transfer, or card. A three-step tracker (job accepted, down payment, job completed) shows where the job stands, and the final payment is released when the work is done.
The split protects both sides. The down payment shows a worker that the client is committed before they show up, and holding the balance until the job is done gives the client confidence the work will be finished. Showing the 4% commission on the invoice up front avoids the surprise fees that break trust in a new platform.

The service provider side
Workers think about the app differently: their questions are where the next job is, and how much they've earned. Their home shows nearby listings with an Apply Now button, and their dashboard puts earnings, the current job's progress and a calendar together. Boosts, a subscription for more job slots, give workers a way to grow and give the platform a business model that doesn't depend on raising fees for clients.
A carabao mascot appears in confirmations and empty moments. A financial, verification-heavy app can feel cold, and the mascot keeps the tone friendly and local without getting in the way of the task.

Outcome
A high-fidelity interactive prototype in Figma covering both sides of the marketplace, from onboarding and verification to booking, payment, job tracking, and rating. Building the full flow as a prototype let us validate the workflows before development, and the reusable components kept dozens of screens consistent across the client and worker apps.
Next, I'd test the booking and payment flow with real workers and clients, especially whether the down payment step feels reassuring or like a barrier, and whether a client-proposed rate leads to lowball offers. If it does, a suggested rate range based on the worker's listed rate would keep negotiation fair.
