Referral marketplace processing 300+ leads a month — Laravel & Flutter case study
RestorePartnerPro connects people who refer restoration work with the companies that do it. I designed and built the whole product on my own: the API, the web platform, and the iOS and Android apps. More than two years later, I still run it.
- Client
- Restoration-industry referral network
- Timeline
- Mar 2024 — present (2+ years)
- Role
- Sole developer: architecture, backend, web and mobile
- Headline result
- 300+ leads processed monthly
- Stack
- PHPLaravelMySQLREST APIFlutteriOSAndroid
The problem
In the restoration industry, a lot of work starts with a referral. Someone sees the damage first and passes the job along to a restoration company. Without a dedicated system, that hand-off is easy to lose track of: the referrer doesn’t know what happened to the job, and the company has no single place to see where its work is coming from.
RestorePartnerPro turns those hand-offs into a marketplace that connects referrers with restoration companies. It had to work on the web for people at a desk, and on iOS and Android for people out on site. And because it was going to be built and run by one developer, it had to stay simple enough to maintain for years, not months.
What I built
- A PHP/Laravel REST API that is the single backend for the web platform and both mobile apps
- A web frontend for referrers and restoration companies
- iOS and Android apps built from one Flutter codebase
- The referral marketplace itself, connecting 100+ referrers and restoration companies
- Ongoing feature development, maintenance and support as the sole developer since launch
One API for every client
Web, iOS and Android all talk to the same Laravel API. Business rules live in one place, so a lead behaves the same no matter which screen it came from, and a new feature is built once on the backend before any client uses it. That is what makes three front ends manageable for a single developer.
Flutter for both mobile platforms
A single Flutter codebase ships to both iOS and Android. For a product run by one person, that is the difference between maintaining one mobile app and maintaining two, with twice the bugs and twice the release work.
Challenges and how they were solved
Two sides of the same marketplace
Referrers and restoration companies look at the same leads from opposite ends. Referrers care about what they sent and what became of it; companies care about the work coming in. The data model and permissions are built around that split, so each side sees exactly its own part of every lead.
Owning the whole product, every day
Being the only developer means architecture, new features, app releases and support all land on the same desk. Keeping the backend as the single source of truth, and keeping the codebase conventional Laravel and Flutter, is what lets the product keep growing without slowing down.
Results
- 300+ leads processed every month
- 100+ referrers and restoration companies on the marketplace
- Shipped on web, iOS and Android from one backend
- Still retained after 2+ years as the sole developer
Let's talk about yours.
Book a free 30-minute call. Within 48 hours you'll have a written plan with scope, timeline and a fixed price.