Client
FindTalents
← Back to Case Studies
Software
FindTalents
A two-sided local-services marketplace where customers can search verified pros, book with escrow protection, and build trust from reviews tied to completed jobs.
A live marketplace platform spanning search, bookings, verification, escrow payouts, disputes, and dual-role reputations.
Duration
Ongoing product development
Technology stack
- Next.js
- React
- TypeScript
- PostgreSQL
- Prisma
- Stripe
- Redis
- Expo
Quick client profile
- Industry
- Local services marketplace
- Location
- U.S. local markets
- Scale
- Two-sided marketplace with web and mobile clients
- Engagement
- Product strategy, UX, marketplace architecture, payments, and development
Project Context
Why this engagement mattered
Hiring local help often fails on trust. Customers need a practical way to find nearby electricians, plumbers, cleaners, and other pros without guessing from incomplete profiles. Professionals need bookings, payouts, and reputation tools that reward completed work rather than vanity reviews.
FindTalents is built around that exchange. Visitors can search by trade and location without an account, then create free accounts to message, book, post jobs, or save talent. Bookings hold payment in escrow until the customer confirms completion or an auto-release window ends. Disputes can freeze funds for admin review, refund, release, or split.
Trust is treated as product infrastructure. Talent onboarding covers services, rates, service area, portfolio, agreements, verification, and payouts. Identity, insurance, license, and related signals help customers compare options. Reviews are tied to completed jobs, with separate customer and talent reputation tracks.
Under the surface, the platform combines a Next.js web product, Expo mobile app, PostgreSQL data model, Redis/BullMQ workers, Stripe Connect escrow flows, and object storage for sensitive verification files. The current public experience still marks testing-mode payment simulation where applicable, so the case study focuses on product capability rather than unverified traction claims.
Project Images
A closer view of the platform and delivery context
Before And After
What changed through the engagement
Before
- Local hiring needed clearer trust signals than generic listings and unverified reviews
- Payments had to protect both customers and talent through completion, not just checkout
- One account needed to support customer and talent roles without mixing reputations
- Verification, disputes, payouts, and messaging needed shared backend infrastructure
After
- ✓Search-first discovery with map results, badges, rates, and service-area context
- ✓Escrow-protected bookings with confirmation, auto-release, refund, and dispute paths
- ✓Progressive talent onboarding, verification signals, and job-tied reviews
- ✓Shared web and mobile API with workers for reminders, payouts, and reputation jobs
Implementation Approach
How the work moved from strategy into execution
Step 1
Define the marketplace around escrow, verification, and completed-job trust
Step 2
Design dual-role journeys for customers, talent, and administrators
Step 3
Build booking, payout, dispute, and reputation systems on Stripe Connect and workers
Step 4
Ship the web marketplace and Expo mobile client against one API and data model
Measured Outcomes
Escrow-protected
Booking model
Verification · job-tied reviews
Trust signals
Web + mobile
Clients
Next Step
Ready for similar results?
Let’s discuss your goals and build a roadmap that delivers measurable outcomes with stronger messaging, cleaner systems, and a more accountable delivery process.