ClassPass:
Schedules Redesign
Role
Industry
Duration
About Classpass
ClassPass is a global subscription-based marketplace that gives consumers access to thousands of fitness studios, gyms, spas, and wellness venues through a unified credit system. Instead of paying for a single gym membership, users purchase monthly credit packages to book local group classes (like yoga, cycling, or Pilates), gym time, and wellness services (massage, beauty, saunas) through one app.
ClassPass Partner Dashboard is the B2B management portal designed for venue owners, studio managers, and wellness providers listed on the ClassPass network. It serves as the primary operational hub where business partners manage schedules, track class rosters, adjust inventory, view real-time revenue payouts, and analyze customer acquisition analytics.
Schedules flow Redesign
As the most heavily utilized feature on the Partner Dashboard, the Schedule UI accounts for over 70% of unique daily visits. However, without a major refresh in over five years, incremental feature additions had left the experience feeling cluttered, fragmented, and disjointed. This project aimed to deliver a modern, cohesive UI that reduced cognitive load and streamlined high-frequency operational tasks for partners.

👩🏽💻 Front Desk:
This user has a operational role on the venue, focusing on the managing class flow, guest safety, and communication.
👨🏻💼 Manager & Owner:
This user has a strategic role on the venue, focusing in Maximizing revenue, managing inventory, and trusting automation.
I led end-to-end design for this project as the main designer on the Partners squad. I owned the complete strategy and execution, from crafting the research plan and conducting user interviews to synthesizing data and building the final interface powered by modern AI workflows.
Discovery
At beginning of the project we used claude to run benchmark analysis and Claude Cowork to automate the research output from the interviews and user testings based on our research plan and interview script, which made the whole process way faster, because without the AI we would need to finish the discovery process and only them analyses the data and consolidate the outputs, with claude the output and insights were updating in real-time while we were on the discovery process.
Execution
Claude Design was used to run multiple layout options for the same features and validate them with quick prototypes. After we had a consolidated UI design Claude Code allowed me to prototype directly inside our staging environment, shipping functional code rather than static Figma frames. This meant complex interactions could be tested in the browser before engineering build started. By committing production-ready component code locally, design handoff shifted became a faster process.
1
Research and planning
We began by evaluating our existing schedule experience through user interviews and usability testing. Our goal was to map out core user workflows, pinpoint daily tasks, and identify the primary friction points partners face in their day-to-day platform management.
2
Consolidating data and strategy
With the aggregated data we could set our goals, product requirements, acceptance criteria and priorities for the new design for the schedules journey.
3
Design exploration
Following ours requirements, we used figma and Claude Design as a partner to test quickly different layouts for different personas, creating variations and quick prototypes to validate the ideas.
4
Design Execution and implementation
With the design direction already validated in Figma and since our design system and visual identity were already fully established in code, we worked with streamlined workflow with Claude Code → Code Review → Implement. By connecting Claude Code directly to our staging environment, we rapidly accelerated our shipping velocity. Figma was reserved for high-level ideation and exploratory visual work that was faster to draw than to prompt.
Older Design
With a mix of different features done with different goals along the time, the past experience has no clear hierarchy, being visually crowded and disjointed.

Redesigned experience
The redesigned experience surface-level prioritizes high-frequency daily data at a glance. By introducing a dedicated detail view, secondary information that previously cluttered the main interface now lives in a structured, contextual space, allowing operators to drill into specific schedules only when in-depth analysis is required.
Default view
This view allows partners to quickly scan and compare critical schedule data, execute rapid inline actions, and use advanced filtering to surface specific schedules instantaneously.


Detail view
The detail view enables partners to perform deep-dive data analysis, execute secondary schedule actions, and inspect individual class rosters on demand.

