FindSparrow

The Problem

FindSparrow needed to solve a two-sided trust problem, and honestly, that's the hard part of any local marketplace. How do you let students earn money doing babysitting, tutoring, gardening, or pet care, while giving families real confidence in who's about to show up? Before Netrex got involved, that trust problem lived entirely in word of mouth. There was no shared place where a parent could check a tutor's track record. There was no way for a student to build a reputation across gigs and clients. What the founders actually needed wasn't a listings board. It was a real marketplace: verified accounts on both sides, live job postings, in-platform messaging so nobody has to hand out a phone number blind, and reviews that make trust visible instead of assumed.

Our Approach

In my experience, the biggest risk in a two-sided marketplace is rarely the tech. It's getting people to that first successful match before they give up and go back to word of mouth. So we mapped the student journey and the family journey before writing a line of code. If either side has to work too hard for the first payoff, they leave, and the network effect never gets going. From there we built identity verification for students, a job-posting flow for families that takes under two minutes, and real-time feeds so new postings reach nearby students right away. In-app messaging keeps phone numbers private until both sides choose to share them. A two-way review system locks in once a job's marked complete. We shipped in stages too. The core booking flow launched first, and we layered messaging and reviews on top once there was real usage to design against, not guesses.

Architecture & Tech Stack

The platform runs on a Laravel backend for the core business logic, authentication, and job data, paired with a Node.js and Express.js service that handles real-time messaging and notifications on its own. Keeping that messaging layer separate was a deliberate call. A busy chat thread should never be able to slow down someone posting a job. On the frontend we combined React and Next.js, which gets us fast, SEO-friendly rendering for public job listings and a smooth single-page experience once someone's logged in, all styled with Tailwind CSS. Firebase handles real-time presence and push notifications. MySQL stays the system of record for users, jobs, and reviews. The whole thing runs on AWS, with GitHub covering version control and CI.

Results

• Successfully onboarded 1000+ student users to the platform.
• Reduced job posting time by 50%, enabling clients to find best matched students faster.
• Improved retention with a 90% return rate for task posters
• Achieved a 95% satisfaction rate from users through feedback surveys.