Building Scalable Two-Sided Marketplaces: Lessons from Workili & ServBook

Introduction

Two-sided marketplaces present complex engineering challenges: balancing demand from consumers with supply from verified service professionals. Platforms like Workili (USA) and ServBook (Singapore) require real-time job bidding, payment escrow holds, and location-based search engines.

In this guide, we break down the key system architecture components required to build high-converting service marketplaces.

Key Marketplace Components

1. Geo-Spatial Provider Search Matrix

Using PostgreSQL PostGIS or Google Maps Geocoding API to query service pros within a dynamic radius (e.g. 15 miles):

-- Query active pros within 20km radius using PostGIS ST_DWithin
SELECT id, name, rating, ST_Distance(location, ST_MakePoint($1, $2)::geography) AS distance
FROM service_providers
WHERE is_verified = true 
  AND is_active = true 
  AND ST_DWithin(location, ST_MakePoint($1, $2)::geography, 20000)
ORDER BY distance ASC;

2. Escrow Payment Logic with Stripe Connect

To build trust, customer funds must be held safely until job completion:

• Customer posts job → Payment authorized & captured into Stripe Escrow.
• Pro completes job → Customer verifies satisfaction → Stripe release trigger transfers payout minus platform commission fee.

Conclusion

Architecting a two-sided marketplace requires robust database design, escrow safety, and instant notification loops. When built correctly, these platforms scale effortlessly across nationwide markets.