Marketplace and gig apps

// The problem

A founder wants to launch a services marketplace that connects customers with independent providers, with bookings, payments and payouts handled properly from day one.

// What we would build

A web and iOS and Android marketplace: provider onboarding with identity checks, listings and search, bookings and payments, split payouts to providers through Stripe Connect, ratings and an operations back office.

// What is in it

// Stack

• Next.js
• React Native
• PostgreSQL
• Stripe Connect
• Identity verification interface
• AWS

// The problem

An on-demand delivery platform dispatches jobs by group chat, workers cannot see their earnings until payday, and customers have no idea where their order is.

// What we would build

A worker app and a customer app with live dispatch: jobs offered to nearby workers who accept in the app, live status for the customer, earnings and payouts the worker can see, and a dispatch board for operations.

// What is in it

// Stack

• Next.js
• React Native
• PostgreSQL
• Redis
• Stripe Connect
• AWS

// The problem

A second-hand marketplace's moderators cannot read every new listing, so fake listings and banned items sit live for hours before someone reports them.

// What we would build

A moderation assistant that reads every new listing and its photos, scores it against the marketplace's own rules, and sends doubtful ones to a person's review queue, with the reasons attached. It runs on an open-source model in the marketplace's own cloud account, because volume is high and listings include personal details; people make every final decision.

// What is in it

// Stack

• Open-source model
• Next.js
• PostgreSQL
• Queue
• AWS

// The problem

A marketplace's founders track supply, demand and take rate in spreadsheets, and cannot tell which cities or categories are healthy until revenue drops.

// What we would build

A dashboard that reads orders, listings, payouts and support into one model, so founders see liquidity, fill rate, take rate and repeat buyers by city and category, from one source of numbers.

// What is in it

// Stack

• PostgreSQL
• dbt
• Next.js
• Stripe interface
• AWS

// The problem

A gig platform's team copies payout reports from the payment provider into accounting, re-checks identity results by hand and chases failed payouts by email.

// What we would build

An integration hub between the marketplace, the payment provider, the identity check service, the CRM and accounting, so payouts, verifications and refunds flow to the right place once and failures are flagged at once.

// What is in it

// Stack

• Node.js
• PostgreSQL
• OpenAPI
• Stripe Connect
• Identity verification interface
• AWS

// The problem

Freelancers on a niche skills marketplace lose their ratings when they move between platforms, and new sellers struggle to prove their track record.

// What we would build

Completed jobs and ratings issued to sellers as verifiable records on a public chain, which they can show anywhere and which no platform can quietly delete. Buyers check a seller's record without a wallet. If your sellers only ever work on your marketplace, a database is simpler, and we will say so.

// What is in it

// Stack

• Next.js
• Solidity
• Base
• PostgreSQL
• AWS

// The problem

A rentals marketplace built its first version fast, and launching a second city made search slow, double bookings appear and the database fall over at weekends.

// What we would build

We review the code, data and hosting, fix the faults that cause double bookings first, rebuild search and the slowest parts, add the languages and currencies the next markets need, and run it on hosting sized for weekends.

// What is in it

// Stack

• Next.js
• PostgreSQL
• OpenSearch
• AWS
• Terraform