Two sided marketplaces where both sides get a product worth opening.

JobIQ is a customer app in Flutter, a vendor portal in Next.js and an admin console, all on a NestJS and MongoDB API. Bookings, technicians, the catalogue, chat and reporting live in one place, so a job booked on a phone appears on the vendor's board and in the admin's numbers at the same moment. Per job, the customer and the vendor see the same chat, map and status.

Vendors manage their own plans and reporting from the console, which is the difference between a marketplace that scales and one that runs on the founder's inbox. Teachers Lunch follows the same shape with two Flutter apps, customers and riders, restaurant and admin web, and a NestJS API with Stripe, Twilio SMS and push.

Gloss & Hammer sits between restaurants that need something fixed, cleaned or installed and the providers who do it. Providers are verified before they are listed, owners post a job and see verified providers respond, and both sides share one dashboard. The landing page had to sell two journeys without confusing either.

Lynxnet carries reputation as badges on profiles and gives both sides a dispute form inside the app with a dispute desk in the admin, so when something goes wrong there is a process rather than an argument. Skills Sync lets providers earn badges, tiers, achievements and rewards from real bookings. In every case the trust signal is produced by the system from actual behaviour.

Skills Sync books a customer into a provider's availability calendar and takes payment with a saved card through Stripe setup intents, so a repeat booking never asks for the card again. Teachers Lunch confirms card payments by webhook and sends SMS and push updates while the rider's map moves. Nothing in the product trusts the client's word that money changed hands; the provider's webhook is the record.

Disputes, refunds and payouts are designed with the same seriousness as checkout. A marketplace that gets payment right earns the second booking, and the second booking is the business.

Every marketplace here has a Next.js admin that the operator actually uses: Lynxnet's dispute desk, JobIQ's reporting, Teachers Lunch's analytics and broadcasts, Skills Sync's marketplace management. Reports, bans, categories and payouts are handled there rather than in a database console.

We scope the admin from the first sprint because it is where the founder spends their day once the apps are live. A marketplace with a thin admin is a marketplace that will need a rebuild at the first thousand users.