Raven is a marketplace connecting ski instructors with clients on the mountain. I designed the side most marketplaces ignore: the tools that let an instructor run their entire livelihood from a phone.

The Problem




Research
We started with the instructors, not the screens
UX Plan
deep dive 01
The availability and pricing engine
Availability



Instructors sell slots, not single lessons. The slot setup mirrors how they actually teach.
Availability shifts through the season, so it has to flex without getting fiddly.
Pricing


There is no single price. Rates move with time of day, sport and season.
The base rate cascades down, so a rate is set once and only overridden where it differs.
deep dive 02
Adding a second instructor:




The handoff that used to happen over text now lives in one thread, logged and visible to the instructor, the stand in and the client.
Raven turns it into a structured job offer, with counter offers, accept or decline, and the client kept in the loop.
deep dive 03
Instructor Dashboard


Projected earnings for the month, on a trend line, up top.
The week ahead, then the next booking as a card.
Quick modules into every deeper flow: availability and rates, Stripe payouts, bookings and requests, profile, referrals.
consistency
Design System Creation
behind the build
Measuring and Tracking
I built this analytics dashboard myself with Claude Code, then used it to understand retention and gaps in our onboarding flows. It tracks how the user base grows and who signs up over time, how instructors set their availability down to the day and the time of day, and how complete their profiles are.
