Hostshare

What the engagement looked like.

Hostshare arrived with an idea, a founder, and no product. The brief: take a novel real-estate primitive — shared short-term property management between multiple hosts — and ship something beta-worthy in under a quarter.

The problem on arrival.

No existing design system, no engineering patterns, no product surface — just a business model and a waitlist building in the background.

The marketplace side had two distinct user types (hosts and landlords) with overlapping but asymmetric needs, and any UI would need to read as trustworthy for a category where money and property trade hands.

How it came together.

4 phases, each one trying to prove a single thing before the next could start.

1. Week 0–2
   System first

   Typography, token primitives, and a component catalogue scoped to likely product needs, before touching a single screen.

2. Week 2–6
   Flows as wireframes

   End-to-end host and landlord journeys as low-fidelity wires. Validated against the founder weekly; iterated.

3. Week 6–12
   Build in vertical slices

   Each slice shipped a working screen backed by real endpoints, not mocked data. Design and code moved together.

4. Week 12–16
   Beta polish

   Onboarding, empty states, responsive pass, motion pass. Flipped the switch for the waitlist at week 16.

What shipped.

Public beta shipped on schedule with 1,000 active accounts drawn from a 10,000-deep waitlist. The design system built in weeks 0–2 has absorbed every feature added since without a rewrite.