Website
Website
Website
Community Saas
Community Saas
Community Saas
Flexxxa
Flexxxa
Flexxxa
Designing the infrastructure behind a platform where people discover experiences and get rewarded for showing up.
Designing the infrastructure behind a platform where people discover experiences and get rewarded for showing up.
Designing the infrastructure behind a platform where people discover experiences and get rewarded for showing up.
Flexxxa connects people with events and experiences while giving hosts tools to attract attendees,
manage participation and reward engagement.
Flexxxa connects people with events and experiences while giving hosts tools to attract attendees,
manage participation and reward engagement.
Flexxxa connects people with events and experiences while giving hosts tools to attract attendees,
manage participation and reward engagement.
Role
Role
Role
Product Designer · UX Research
Product Designer · UX Research
Product Designer · UX Research
Status
Status
Status
Live · 5,000+ users
Live · 5,000+ users
Live · 5,000+ users
Timeline
Timeline
Timeline
Jan 2025 - June 2025
Jan 2025 - June 2025
Jan 2025 - June 2025
Tools
Tools
Tools
Figma, ChatGPT
Figma, ChatGPT
Figma, ChatGPT
Platform
Platform
Platform
Mobile Application
Mobile Application
Mobile Application
Overview
Overview
Overview
Why this Product
exists
Why this Product
exists
Why this Product
exists
Getting people to attend an event is often harder than creating the event itself.
Hosts need visibility, attendees and reliable ways to manage participation.
At the same time, people are constantly looking for interesting things to do but don't always know where to find them.
Flexxxa connects both sides.
Hosts create opportunities and request the type of attendees they need.
Flexrs discover opportunities, receive invitations and can earn rewards for participating.
The platform has since expanded beyond events into a broader discovery and rewards ecosystem involving venues, restaurants, accommodation, travel services and lifestyle experiences. Its product documentation reflects this multi-sided model.
Getting people to attend an event is often harder than creating the event itself.
Hosts need visibility, attendees and reliable ways to manage participation.
At the same time, people are constantly looking for interesting things to do but don't always know where to find them.
Flexxxa connects both sides.
Hosts create opportunities and request the type of attendees they need.
Flexrs discover opportunities, receive invitations and can earn rewards for participating.
The platform has since expanded beyond events into a broader discovery and rewards ecosystem involving venues, restaurants, accommodation, travel services and lifestyle experiences. Its product documentation reflects this multi-sided model.
Getting people to attend an event is often harder than creating the event itself.
Hosts need visibility, attendees and reliable ways to manage participation.
At the same time, people are constantly looking for interesting things to do but don't always know where to find them.
Flexxxa connects both sides.
Hosts create opportunities and request the type of attendees they need.
Flexrs discover opportunities, receive invitations and can earn rewards for participating.
The platform has since expanded beyond events into a broader discovery and rewards ecosystem involving venues, restaurants, accommodation, travel services and lifestyle experiences. Its product documentation reflects this multi-sided model.
My Role
My Role
My Role
I worked collaboratively with the product owner and contributed across the core user and host experiences.
I worked collaboratively with the product owner and contributed across the core user and host experiences.
I worked collaboratively with the product owner and contributed across the core user and host experiences.
My responsibilities included:
My responsibilities included:
My responsibilities included:
Research
Existing flow analysis
UX improvements
User onboarding
Audience flows
Host onboarding
Event creation
Event details
Community Hub
Attendee selection
Check-in / check-out
Wallet
Verification
Leaderboard
Payouts
Identifying missing states and edge cases
Research
Existing flow analysis
UX improvements
User onboarding
Audience flows
Host onboarding
Event creation
Event details
Community Hub
Attendee selection
Check-in / check-out
Wallet
Verification
Leaderboard
Payouts
Identifying missing states and edge cases
Research
Existing flow analysis
UX improvements
User onboarding
Audience flows
Host onboarding
Event creation
Event details
Community Hub
Attendee selection
Check-in / check-out
Wallet
Verification
Leaderboard
Payouts
Identifying missing states and edge cases
I also reviewed existing flows and made additions where I noticed gaps in the experience.
I also reviewed existing flows and made additions where I noticed gaps in the experience.
I also reviewed existing flows and made additions where I noticed gaps in the experience.
Problem & Solution
Problem & Solution
Problem & Solution
What we were
solving
What we were
solving
What we were
solving
The Problem
The Problem
The Problem
The product had to solve multiple problems simultaneously.
For Flexrs
Discover relevant events
Complete onboarding
Find suitable opportunities
Accept or decline invitations
Check in and out
Earn rewards
Track earnings
Receive payouts
For Hosts
Create events
Define attendee requirements
Review potential attendees
Select participants
Track attendance
Manage event performance
This created a complex multi-sided experience with very different user needs.
The product had to solve multiple problems simultaneously.
For Flexrs
Discover relevant events
Complete onboarding
Find suitable opportunities
Accept or decline invitations
Check in and out
Earn rewards
Track earnings
Receive payouts
For Hosts
Create events
Define attendee requirements
Review potential attendees
Select participants
Track attendance
Manage event performance
This created a complex multi-sided experience with very different user needs.
The product had to solve multiple problems simultaneously.
For Flexrs
Discover relevant events
Complete onboarding
Find suitable opportunities
Accept or decline invitations
Check in and out
Earn rewards
Track earnings
Receive payouts
For Hosts
Create events
Define attendee requirements
Review potential attendees
Select participants
Track attendance
Manage event performance
This created a complex multi-sided experience with very different user needs.
Defining The Product
Defining The Product
Defining The Product
The core product model became:
Host creates opportunity → Flexxxa matches people → Flexrs participate → Attendance is verified → Rewards are processed
This simple model hid a lot of complexity.
The product needed to handle onboarding, matching, verification, attendance, rewards, wallets and payouts without making the experience feel like an administrative platform.
The core product model became:
Host creates opportunity → Flexxxa matches people → Flexrs participate → Attendance is verified → Rewards are processed
This simple model hid a lot of complexity.
The product needed to handle onboarding, matching, verification, attendance, rewards, wallets and payouts without making the experience feel like an administrative platform.
The core product model became:
Host creates opportunity → Flexxxa matches people → Flexrs participate → Attendance is verified → Rewards are processed
This simple model hid a lot of complexity.
The product needed to handle onboarding, matching, verification, attendance, rewards, wallets and payouts without making the experience feel like an administrative platform.
Design Process
Design Process
Design Process
Key product
decisons
Key product
decisons
Key product
decisons
Matching needed to feel simple.
Matching needed to feel simple.
Matching needed to feel simple.
Hosts shouldn't have to manually coordinate hundreds of potential attendees.
The selection experience was designed around a swipe-based interaction, allowing hosts to quickly review and select people.
Hosts shouldn't have to manually coordinate hundreds of potential attendees.
The selection experience was designed around a swipe-based interaction, allowing hosts to quickly review and select people.
Hosts shouldn't have to manually coordinate hundreds of potential attendees.
The selection experience was designed around a swipe-based interaction, allowing hosts to quickly review and select people.
Attendance needed to become a measurable action.
Attendance needed to become a measurable action.
Attendance needed to become a measurable action.
Because rewards depended on participation, simply accepting an invitation wasn't enough.
Check-in and check-out became important product states for verifying attendance and supporting reward calculations.
Because rewards depended on participation, simply accepting an invitation wasn't enough.
Check-in and check-out became important product states for verifying attendance and supporting reward calculations.
Because rewards depended on participation, simply accepting an invitation wasn't enough.
Check-in and check-out became important product states for verifying attendance and supporting reward calculations.
Rewards needed a home.
Rewards needed a home.
Rewards needed a home.
The wallet became the central place for users to understand what they had earned and manage their payouts.
The wallet became the central place for users to understand what they had earned and manage their payouts.
The wallet became the central place for users to understand what they had earned and manage their payouts.
Gamification supported participation.
Gamification supported participation.
Gamification supported participation.
The leaderboard gave users another reason to stay active.
Instead of treating attendance as a one-off action, Flexxxa could turn participation into an ongoing progression.
The leaderboard gave users another reason to stay active.
Instead of treating attendance as a one-off action, Flexxxa could turn participation into an ongoing progression.
The leaderboard gave users another reason to stay active.
Instead of treating attendance as a one-off action, Flexxxa could turn participation into an ongoing progression.
Impact
Impact
Impact
What the
work achieved
What the
work achieved
What the
work achieved
Flexxxa is live and has acquired over 5,000 users.
The product launched with its MVP and has continued evolving as adoption grows.
The work helped establish experiences across:
Flexxxa is live and has acquired over 5,000 users.
The product launched with its MVP and has continued evolving as adoption grows.
The work helped establish experiences across:
Flexxxa is live and has acquired over 5,000 users.
The product launched with its MVP and has continued evolving as adoption grows.
The work helped establish experiences across:
User onboarding, Host workflows, Event creation
User onboarding, Host workflows, Event creation
User onboarding, Host workflows, Event creation
Matching, Attendance, Rewards, Wallet
Matching, Attendance, Rewards, Wallet
Matching, Attendance, Rewards, Wallet
Verification, Payouts, Community experiences
Verification, Payouts, Community experiences
Verification, Payouts, Community experiences
Reflection
Reflection
Reflection
Key learnings
Key learnings
Key learnings
Flexxxa taught me how different product experiences can be interconnected by one underlying system.
A simple user action like "attend an event" can affect matching, verification, rewards, wallets and payouts.
It made me much more conscious of designing states and edge cases, rather than designing screens in isolation.
Flexxxa taught me how different product experiences can be interconnected by one underlying system.
A simple user action like "attend an event" can affect matching, verification, rewards, wallets and payouts.
It made me much more conscious of designing states and edge cases, rather than designing screens in isolation.
Flexxxa taught me how different product experiences can be interconnected by one underlying system.
A simple user action like "attend an event" can affect matching, verification, rewards, wallets and payouts.
It made me much more conscious of designing states and edge cases, rather than designing screens in isolation.
Next Project
Next Project
