The problem
Flipvo’s owner had a clear picture of the marketplace they wanted to run and a thin patience for the off-the-shelf options. SaaS marketplace platforms wanted a cut of every sale, a per-seat fee, and a roadmap that wasn’t theirs. The shop the owner had in mind needed onboarding, payouts, listings, search, and a back office that fit the way they actually worked — not the way a vendor wanted them to work.
We came in to build it from scratch. Owned code, owned data, owned roadmap.
What we built
A multi-vendor marketplace on Laravel and Livewire, with Stripe Connect handling onboarding and split payouts. Vendors register, verify, list inventory, and ship — the platform takes care of identity, money, and the audit trail behind both. Customers browse a single storefront and check out across vendors in one cart.
The back office is the part that usually gets left out of marketplace tutorials and was the part the owner cared about most. Order routing, dispute flow, refund mechanics, payout reconciliation — all wired into the same admin so a single operator can run the whole shop without bouncing between dashboards.
We kept the front-end on plain Livewire. No SPA, no client-side state machine to babysit. Pages render on the server, hydrate the bits that need to be interactive, and stay fast on a basic phone.
How we shipped it
Weekly check-ins with the owner. Real software shipping every Friday. Each week we cut one slice end-to-end — onboarding one week, listings the next, checkout the week after — so the project always had something the owner could click through and react to.
Stripe Connect was the riskiest piece, so we wired it up first. By the time the storefront started taking shape, payouts had already been running on a sandbox for weeks. Same for SES on transactional email and S3 on uploads — boring infrastructure, locked down early, never revisited.
Outcome
Flipvo went live with a working marketplace, a real vendor pipeline, and zero recurring SaaS fees on top of Stripe and AWS. The owner has the source, the server, and the keys.
[OWNER TO CONFIRM — sentence about post-launch traction: vendors signed up, GMV processed, time saved per week, whatever number the owner wants on the record.]