Luxury marketplace / Ongoing

House of Watches

Turn a collector-led idea into a marketplace people can actually operate.

A luxury marketplace cannot borrow trust from a generic commerce template. Its product model has to make evidence, ownership, and the next action visible at every stage.

LiveProduction marketplace
End-to-endBuyer to back office
OngoingProduct partnership
House of Watches mobile marketplace shown beside a branded card
Product field / House of WatchesPublic engagement
EngagementLuxury marketplace / Ongoing
Product surfacePublic engagement
Technical foundationNext.js · TypeScript · PostgreSQL · Stripe Connect
01 / The ambition

Not another watch shop—a working marketplace for considered transactions.

The initial idea was driven by collector knowledge and a clear gap in the market, but premium watches introduce more than catalog and checkout. Buyers need confidence in the object and the seller. Sellers need a credible route to market. The operating team needs to see and move every transaction without losing its history.

That meant the real product crossed several boundaries at once: editorial discovery, listings, authentication, auctions, services, conversation, payment, and post-sale operations. A beautiful storefront could only be the visible edge of a much larger system.

02 / The operating model

Design around trust and transaction state.

We mapped each important object—listing, conversation, bid, order, payment, handoff—through the states it could occupy and the people allowed to move it. That gave design and engineering one shared language for permissions, exceptions, and the next action.

The same model shaped the customer experience. Instead of exposing back-office complexity, the interface surfaces the evidence and actions relevant to that moment: what is known, what happens next, and who currently owns the decision.

03 / The platform

Build the storefront and the business behind it together.

The live platform combines a bilingual marketplace with seller and administrator systems, search, rich media, messaging, authentication, service requests, promotional tooling, payments, and auction lifecycles.

Operational tooling was treated as product work, not a secondary admin task. The team needed enough context to answer questions, resolve exceptions, and understand the state of the market without reconstructing it from messages and disconnected dashboards.

04 / The partnership

Launch was the beginning of the useful information.

House of Watches is a continuing product partnership. New behaviors in production expose different priorities than a roadmap can predict, especially when transactions involve high consideration, multiple parties, and operational handoffs.

The platform now changes with that evidence. Search, media, payments, seller operations, auctions, and promotional surfaces can keep improving around one stable principle: make the transaction more trustworthy and the next action easier to own.

The storefront attracts attention. The operating model earns the transaction.

Spicy Coconut / Product principle
The foundation left behind

A product model that can keep learning.

House of Watches continues to evolve as the team learns where trust is won, where operations slow down, and which states need more visibility. The platform is designed to absorb those lessons rather than resist them.

Next case study / Medical operations / End-to-end buildElitemed
Start with the problem

Bring us the
messy version.

No polished brief required. A rough email about what is getting harder as the business grows is enough.

hello@spicycoconut.dev