Product Design: A Marketplace App for One-of-a-Kind Antiques

You are a product manager building a new app where people buy and sell antiques. Design it: decide whom it should serve first, which problems it should solve for them, what the first version includes, and how you would know it is working. ```hint What makes antiques different Compare an antique with any other secondhand item: each piece is one of a kind, and its value rests on details a buyer cannot easily check from a photo. Let that difference drive which side of the marketplace and which pain points you start with. ``` ### Clarifying Questions - Is this a standalone startup or a product inside an existing company, and which country does it launch in? - Does "antiques" include lower-priced vintage furniture and decor, or only high-value pieces where authenticity and appraisal matter most? - Should the app handle shipping for large or fragile items such as furniture, or can I assume local pickup for those? - Is the business goal to maximize the number of transactions, or to become the trusted venue for higher-value sales? ### What a Strong Answer Covers - A deliberate choice of which side and which segment to serve first, justified by how the marketplace gains liquidity - Pain points specific to one-of-a-kind items, on both the buying and the selling side - A prioritized first version, with a clear reason for what is left out - A business model and success metrics, with guardrails for fraud and disputes - Risks such as reproductions, stolen or restricted goods, shipping damage, and deals moving off the app ### Follow-up Questions - How would you attract the first sellers and buyers in a single city, given that buyers will not come without inventory? - After delivery, a buyer says an expensive piece is a modern reproduction. How should the product and its policies handle that? - How would you stop buyers and sellers from finishing the deal off the app once they have connected?