Alpen
An e-bike rental kiosk I launched with Breckenridge Grand Vacations, and the dashboard that ran it.

- Role
- Product Strategist & UI/UX Lead
- Timeline
- September 2024 to February 2026
- Platform
- On-site kiosk, guest mobile app, web operations dashboard
- Tools
- Figma, FigJam, HTML/CSS, Claude Code
- Problem
- Alpen rented e-bikes through resorts, and its first dashboard couldn't keep up as properties were added.
- My role
- I owned the product and ran the resort partnerships. I launched the kiosks on-site and supported them day to day.
- What I built
- A new operations dashboard with 20+ screens, the design system behind it, and the guest booking flows.
- Result
- 6 locations live across two resort clients, Breckenridge Grand Vacations and Marriott.
- What I'd change
- Don't own the bikes.
- 6 locations (5 in Breckenridge, 1 in San Diego)
- 20+ dashboard screens
- 2 resort clients
Overview
Alpen put e-bike rental kiosks at resorts. Guests booked in an app and picked up a bike on property. Resort staff and our ops team ran everything from a web dashboard. Breckenridge Grand Vacations was our main client, with five locations in Breckenridge. Marriott was our second, in San Diego.
I owned the product. I also worked the partnerships directly, and I was on-site to launch the kiosks and keep them running. Being there in person taught me more than any research doc could. I could watch a guest get confused at the kiosk and fix it that week.
Problem
The first dashboard was built as the company grew, and it was running out of room. Adding a property meant re-entering everything by hand. There was no way to group properties under one resort client, and no admin permissions. Fleet management and daily operations lived in separate places.
It also looked cheaper than the brand. Resort managers judge a vendor partly by the software their staff will use every day, and the old tool wasn't helping us in those conversations.
What I did
I worked with two designers and two developers, and we built the design system before any screens. It's an ops tool, so every visual choice had to make resort staff faster.
Then I mapped how the work actually happened, with leadership on the requirements and with resort staff on the day to day. That gave us the structure: properties, fleet, pricing, maintenance, staff, guest operations, and admin permissions by role.

What I built
- Pricing. Corporate sets the catalog of bike types and passes. Each property opts in and sets its own prices.
- Clone everything. Every setup screen has a clone button. Copy an existing property and change only what's different.
- Operations dashboard. Every property's bikes by status, plus active rentals with battery, time left, and a one-click swap.
- Revenue and utilization. Revenue by property, and an hourly heatmap across the week for deciding where bikes should go.
- Bike details. Specs, lock, GPS, maintenance log, and status history on one screen.





Results
We got 5 properties online in about 3 weeks. Cloning and templates took property setup from hours of manual entry down to minutes. Grouping properties under a client let us manage a resort company as one account instead of property by property. And when resort managers looked at Alpen, the software backed up the premium pitch.