What we build
Marketplace MVP development
A two-sided marketplace with listings, search and enquiries — deployed in 48 hours for a fixed $3,500 AUD, with payments added once you have supply.
Short answer
A two-sided marketplace with listings, search and enquiries — deployed in 48 hours for a fixed $3,500 AUD, with payments added once you have supply.
Marketplaces fail for one reason far more often than any other: nobody solves the cold-start problem. You can have flawless software and no liquidity, and the product is worthless. So the honest advice for a marketplace MVP is to build the smallest thing that lets you hand-recruit one side of the market and prove the other side turns up.
In practice that means listings, search, and a way for a buyer to contact a seller. It does not mean escrow payments, ratings, messaging threads, dispute resolution and a commission engine, all of which only matter after you have transactions to protect.
The version that ships in 48 hours is deliberately manual behind the scenes. You approve listings yourself. You may even take the first bookings by phone. That is not a shortcut, it is how nearly every large marketplace actually started.
The three features worth starting with
- 1
Listings with a create flow
Sellers submit a listing with photos and details. You approve it before it appears.
- 2
Browse, search and filter
Category, location and keyword search that works on a phone, which is where most buyers are.
- 3
Enquiry or booking request
A buyer contacts a seller, both sides get an email, and you get a copy so you can see every transaction.
Deliberately left out of version one
- In-platform payments, escrow and commission splits (add once you have supply)
- Real-time chat between buyers and sellers
- Ratings, reviews and reputation systems
- Automated identity or licence verification
Technical decisions for this kind of product
- PostgreSQL, because a marketplace is relational from day one
- Image uploads to object storage with automatic resizing, so listings load fast on mobile data
- Server-rendered listing pages so Google can index every listing — this is how marketplaces get free traffic
- Stripe Connect deferred to version two, not because it is hard but because it is premature
A worked example
A marketplace for mobile mechanics
Mechanics create a profile with suburbs served and services offered. Car owners search by suburb and send a job request. Both sides get an email. No payments, no ratings. Once 30 mechanics are listed and jobs are flowing, payments become worth building.
The mistake to avoid
Launching both sides at once to an empty site. Recruit the supply side by hand first, then point demand at something that already looks alive.
Common questions
- Can you build a marketplace in 48 hours?
- A two-sided marketplace with listings, search and enquiries — deployed in 48 hours for a fixed $3,500 AUD, with payments added once you have supply.
- What features should a marketplace MVP start with?
- Listings with a create flow: Sellers submit a listing with photos and details. You approve it before it appears. Browse, search and filter: Category, location and keyword search that works on a phone, which is where most buyers are. Enquiry or booking request: A buyer contacts a seller, both sides get an email, and you get a copy so you can see every transaction.
- What is left out of a marketplace MVP?
- In-platform payments, escrow and commission splits (add once you have supply); Real-time chat between buyers and sellers; Ratings, reviews and reputation systems; Automated identity or licence verification. Each of these is deliberately deferred to a later build rather than half-finished in the first one.
- What is the most common mistake when building a marketplace?
- Launching both sides at once to an empty site. Recruit the supply side by hand first, then point demand at something that already looks alive.
Related reading
- How many features should an MVP have?
- How to scope an MVP so it can actually ship
- What the $3,500 AUD covers