PROJECT OVERVIEW
I designed a role-based MVP for brands, influencers, agents, and agencies through Plexable. One shared architecture gave each audience the information and actions it needed without turning the platform into four separate products.
CLIENT
Amplifidor
MY ROLE
Product and experience design, via Plexable
SCOPE
Product architecture, four role-based workflows, onboarding, Programs, Analytics, Wallet, Groups, design system, and usability testing
VALIDATION
Usability testing across core role-based flows
TIMELINE
2025 engagement
TEAM
I designed the role-based product architecture with Amplifidor’s founder and the Plexable team, then carried its rules across the wider experience.
The context
Amplifidor needed one professional network to support four groups with different goals, permissions, and measures of success. Brands needed campaign control. Influencers needed clarity on active work. Agents and agencies needed portfolio-level visibility.
My responsibility
I translated those operating models into one role-based system. My work covered the navigation model, dashboard logic, onboarding, core product areas, and the reusable interface patterns that kept the experience coherent.
Designing one product for four operating models
CONSTRAINTS & TRADE-OFFS
Different priorities. Shared product logic.
● RESEARCH & CONTEXT
Testing the system, not just the screens
Usability testing focused on whether people could identify their next action, move between active work and supporting tools, and understand financial status without learning a new pattern for every module.
● PRODUCT DECISIONS
Three decisions that made four roles feel coherent
● PROCESS & EVIDENCE
Four-role maps, dashboard hierarchies, Smart Card rules, and onboarding states show how the product logic became interface decisions.
OUTCOMES
Measured usability outcomes
88%
Task success
Recorded across the tested core role-based flows.
70%
Financial-tracking efficiency
Improvement recorded during the validated workflow comparison.
3×
Faster onboarding
Equivalent to a 70% acceleration to active status in the canon record.
WHAT I’D IMPROVE
What improved
Four role-based journeys now share one understandable product model.
Onboarding and financial visibility became materially more efficient in testing.
WHAT I LEARNED
What I learned
Adaptive hierarchy can create relevance without duplicating an entire product.
Activation improves when onboarding ends inside meaningful work, not at a generic dashboard.
More work
WHAT'S NEXT STARTS WITH A CONVERSATION.