The Brief
Homeowners across Portugal looking for a plumber, electrician or carpenter mostly rely on word of mouth or scattered local ads — there's no single place to describe a job once and have it reach the right nearby specialist. Fixbro set out to close that gap: a submitted request should turn into a matched tradesperson, not a directory to scroll through alone.
What Was Built
1. A two-sided marketplace, not a directory
The platform pairs two flows: homeowners submit a request describing the job, location and urgency, while registered specialists — plumbers, electricians, carpenters and other trades — receive requests that match their trade and service area. A nationwide trade directory sits alongside the request flow, so a homeowner who wants to browse can, and one who just wants the job done can go straight to a request.
2. Matching logic that reads a request, not a category
Requests aren't broadcast to everyone in a trade — location and service area narrow the match before a specialist ever sees it, so what lands in a tradesperson's queue is relevant work, not a flood of unrelated jobs from across the country.
3. Directus as the data layer behind Next.js
Directus runs headless behind the Next.js frontend: trades, specialists, service areas and requests are all modeled there, keeping the matching rules and the specialist directory editable without redeploying the frontend.
Where It Stands
The core request-and-match flow and the nationwide trade directory structure are built and running, with testing and refinement ongoing ahead of public launch.
- Two-sided request/match flow: built.
- Nationwide trade directory: structured and in place.
- Public launch: in progress.
Stack: Next.js on the frontend, Directus as the headless CMS and data layer.