MVSSIVE
Industry
MusicTech
Product
Music collaboration platform (SaaS)
Year
2025
Role
Product Designer
About The Project
Organizing musical collaboration from the first session
MVSSIVE is a SaaS platform for the music industry. This case focuses on the design of a feature that didn't exist yet: a structured space for music sessions, where producers could centralize participants, files, and context from the start — instead of coordinating everything across WhatsApp, Dropbox, and voice messages.
The challenge was strategic: MVSSIVE only intervened at the end of the creative process. This feature moved the product upstream, making it part of the workflow from the very beginning — with direct impact on retention, adoption, and conversion.
Product Designer
2025
UX Strategy
UX UI Design
Industry
MusicTech
Product
Music collaboration platform (SaaS)
Year
2025
Role
Product Designer
Usage Context
The Moment Music Is Created
A music session is not an isolated moment but a complex environment where multiple dynamics coexist simultaneously. These dimensions define how music is created and why the context in which it happens is so relevant to the creative process.
Collaborative Work
Multiple people participate, working together in real time.
Creative and Technical Decisions
Decisions made during the session directly impact the final song.
Multiple Versions
Ideas are tested, others discarded, and different versions of the same song are generated.
Focus and Continuity
The flow of exchange and coordination influence the outcome of the creative process.
CORE INSIGHT
Working on real music sessions, we began to notice a pattern repeating over and over. Important information from each session—schedules, files, versions, feedback—was scattered across multiple conversations and channels. Nothing was "lost," but it wasn’t where it needed to be. The problem wasn’t a lack of tools, but a lack of structure.
CORE INSIGHT
The problem
Was there a problem worth solving?
When music producers coordinate collaborative sessions, the information ends up scattered across multiple places:
- A WhatsApp group to coordinate the day
- Dropbox for the files
- Voice messages for feedback
- External links for the versions.
Nothing is lost, but nothing is where it should be.
The result is a music producer who spends more energy managing the chaos than focusing on the music. And when handling multiple sessions simultaneously, that burden multiplies.
The problem wasn't the lack of tools. It was the lack of structure.
Impact of the problem on the user
Who suffers from this problem?
Tech Savviness: Intermediate–High.
Fernando
Independent music producer
When I'm managing a session with multiple artists, I need to have everything organized from the start so I can focus on the music without chaos taking control.
OBJECTIVES
- Maintain session control
- Avoid delays in launches
- Protect the quality of the final result
- Appear professional to the artists
PAIN POINTS
- Simultaneous messages from multiple sessions
- Feeling that a version was lost
- Having to resend files and update information
- Fragmented information across multiple tools
NEEDS
- Centralize information from the start
- Structure participants and versions
- Reduce dependence on multiple tools
- Maintain clarity even when managing multiple sessions
JTBD — Job To Be Done
As the session owner..
FUNCTIONAL JTBD
When I'm managing a music session with multiple artists
I want to keep all the session information organized in one place
So that I can focus on the creative process without interruptions or stress
EMOTIONAL JTBD
When information from multiple sessions overlaps
I want to feel in control and clear-headed
So that the chaos doesn't interfere with my creative focus
SOCIAL JTBD
When other people depend on me during a session
I want to respond with clarity and speed
So that the collaboration flows without friction or confusion
Business opportunity
Why did this problem matter to the business?
Until that point, MVSSIVE only intervened in the final stage of the music process: when the song was finished and ready to be published. Its role was to centralize files, metadata, and contributors.
MVSSIVE
The problem was that it came in late. Much of the value, decisions, and versions that define a song are created much earlier, during the music sessions. By not being present at that moment, the product relied on external tools at key stages and didn't capture the context from the start.
MVSSIVE was limited to a closing tool, when it could have become the official source of truth from the beginning.
The strategic opportunity
Integrating the session as a structured entity within the system meant supporting the creative process from the start, preserving the context from the origin, and connecting creation and publication within the same ecosystem.
OPORTUNIDAD
CREATIVE PROCESS / SESSION
UPLOAD FILE
COLLABORATIVE PUBLISHING
No support
OPPORTUNITY
MVSSIVE
MVSSIVE
Business objective
Make MVSSIVE a structural part of the creative process from the beginning, increasing retention, adoption, and conversion within the subscription model.
HMW
How can we preserve the context of each session without disrupting the producer's creative flow?
Solution
The session as a structured entity
The solution was to give each music session its own dedicated space within the system: an independent container that groups participants, files, versions, and context in one place. Each session has its own identity, separate from the rest and accessible from the start.
Experience Design
The experience of creating a session
The entry point
From their profile, the owner has a centralized view of all their sessions with real-time status — upcoming, in progress, completed. Creating a new session is an action available from the same place where all their activity lives. There's no need to leave the system or open another tool.
The session takes shape
When creating a session, the owner defines from the start all the information that was previously scattered: name, date, study, location, publisher. This act of creation is not just a form — it's the moment the session becomes an entity with its own identity within the system.
The session as a structured container
Once created, the session exists as its own space: it centralizes participants, roles, statuses, and contextual information in one place. The owner can see who is inside, who has a pending invitation, and how long each collaborator has been present — without needing to ask on WhatsApp.
As is scenario
BEFORE
The producer coordinates everything externally: a WhatsApp group for the date, Dropbox for the files, voice messages for feedback. Before the music starts, they are already managing the chaos.
To be experience
AFTER
The producer creates the session in MVSSIVE and all the information is centralized from that moment: name, date, studio, participants. The context exists before the session begins.
The session stops being a scattered conversation and becomes an entity with its own structure.
UX Outcomes
How would we know it worked?
Objective
Metric
The owner spends less time coordinating
Collaborators are more autonomous
Information is no longer fragmented
Reduction of manual forwards per session
Session accesses without owner intervention
Percentage of files uploaded directly to MVSSIVE vs external links
Business Outcomes
How would we know the business benefits?
Objective
Metric
MVSSIVE becomes part of the creative flow
The feature drives conversion
90-day retention vs users without sessions
Upgrade rate upon reaching free plan limit
Validating the direction
To confirm that the solution was aligned with both user needs and business goals, I mapped the value proposition against the customer segment. The fit was clear: the user's core pains and jobs connected directly to what the product needed to offer.
Persona
Fernando
Status:
Mid-career independent producer.
Gender:
Male
BACK TO HOME
Next Case Study
MVSSIVE
Industry
MusicTech
Product
Music collaboration platform (SaaS)
Year
2025
Role
Product Designer
About The Project
Organizing musical collaboration from the first session
MVSSIVE is a SaaS platform for the music industry. This case focuses on the design of a feature that didn't exist yet: a structured space for music sessions, where producers could centralize participants, files, and context from the start — instead of coordinating everything across WhatsApp, Dropbox, and voice messages.
The challenge was strategic: MVSSIVE only intervened at the end of the creative process. This feature moved the product upstream, making it part of the workflow from the very beginning — with direct impact on retention, adoption, and conversion.
Product Designer
2025
UX Strategy
UX UI Design
Industry
MusicTech
Product
Music collaboration platform (SaaS)
Year
2025
Role
Product Designer
Usage Context
The Moment Music Is Created
A music session is not an isolated moment but a complex environment where multiple dynamics coexist simultaneously. These dimensions define how music is created and why the context in which it happens is so relevant to the creative process.
Collaborative Work
Multiple people participate, working together in real time.
Creative and Technical Decisions
Decisions made during the session directly impact the final song.
Multiple Versions
Ideas are tested, others discarded, and different versions of the same song are generated.
Focus and Continuity
The flow of exchange and coordination influence the outcome of the creative process.
CORE INSIGHT
Working on real music sessions, we began to notice a pattern repeating over and over. Important information from each session—schedules, files, versions, feedback—was scattered across multiple conversations and channels. Nothing was "lost," but it wasn’t where it needed to be. The problem wasn’t a lack of tools, but a lack of structure.
CORE INSIGHT
The problem
Was there a problem worth solving?
When music producers coordinate collaborative sessions, the information ends up scattered across multiple places:
- A WhatsApp group to coordinate the day
- Dropbox for the files
- Voice messages for feedback
- External links for the versions.
Nothing is lost, but nothing is where it should be.
The result is a music producer who spends more energy managing the chaos than focusing on the music. And when handling multiple sessions simultaneously, that burden multiplies.
The problem wasn't the lack of tools. It was the lack of structure.
Impact of the problem on the user
Who suffers from this problem?
Tech Savviness: Intermediate–High.
Fernando
Independent music producer
When I'm managing a session with multiple artists, I need to have everything organized from the start so I can focus on the music without chaos taking control.
OBJECTIVES
- Maintain session control
- Avoid delays in launches
- Protect the quality of the final result
- Appear professional to the artists
PAIN POINTS
- Simultaneous messages from multiple sessions
- Feeling that a version was lost
- Having to resend files and update information
- Fragmented information across multiple tools
NEEDS
- Centralize information from the start
- Structure participants and versions
- Reduce dependence on multiple tools
- Maintain clarity even when managing multiple sessions
JTBD — Job To Be Done
As the session owner..
FUNCTIONAL JTBD
When I'm managing a music session with multiple artists
+
I want to keep all the session information organized in one place
+
So that I can focus on the creative process without interruptions or stress
EMOTIONAL JTBD
When information from multiple sessions overlaps
+
I want to feel in control and clear-headed
+
So that the chaos doesn't interfere with my creative focus
SOCIAL JTBD
When other people depend on me during a session
+
I want to respond with clarity and speed
+
So that the collaboration flows without friction or confusion
Business opportunity
Why did this problem matter to the business?
Until that point, MVSSIVE only intervened in the final stage of the music process: when the song was finished and ready to be published. Its role was to centralize files, metadata, and contributors.
MVSSIVE
The problem was that it came in late. Much of the value, decisions, and versions that define a song are created much earlier, during the music sessions. By not being present at that moment, the product relied on external tools at key stages and didn't capture the context from the start.
MVSSIVE was limited to a closing tool, when it could have become the official source of truth from the beginning.
The strategic opportunity
Integrating the session as a structured entity within the system meant supporting the creative process from the start, preserving the context from the origin, and connecting creation and publication within the same ecosystem.
OPORTUNIDAD
CREATIVE PROCESS / SESSION
UPLOAD FILE
COLLABORATIVE PUBLISHING
No support
OPPORTUNITY
MVSSIVE
MVSSIVE
Business objective
Make MVSSIVE a structural part of the creative process from the beginning, increasing retention, adoption, and conversion within the subscription model.
HMW
How can we preserve the context of each session without disrupting the producer's creative flow?
Solution
The session as a structured entity
The solution was to give each music session its own dedicated space within the system: an independent container that groups participants, files, versions, and context in one place. Each session has its own identity, separate from the rest and accessible from the start.
Experience Design
The experience of creating a session
The entry point
From their profile, the owner has a centralized view of all their sessions with real-time status — upcoming, in progress, completed. Creating a new session is an action available from the same place where all their activity lives. There's no need to leave the system or open another tool.
The session takes shape
When creating a session, the owner defines from the start all the information that was previously scattered: name, date, study, location, publisher. This act of creation is not just a form — it's the moment the session becomes an entity with its own identity within the system.
The session as a structured container
Once created, the session exists as its own space: it centralizes participants, roles, statuses, and contextual information in one place. The owner can see who is inside, who has a pending invitation, and how long each collaborator has been present — without needing to ask on WhatsApp.
[M]
Scanning this QR will take contributors directly to the session join form.
As is scenario
BEFORE
The producer coordinates everything externally: a WhatsApp group for the date, Dropbox for the files, voice messages for feedback. Before the music starts, they are already managing the chaos.
To be experience
AFTER
The producer creates the session in MVSSIVE and all the information is centralized from that moment: name, date, studio, participants. The context exists before the session begins.
The session stops being a scattered conversation and becomes an entity with its own structure.
UX Outcomes
How would we know it worked?
Objective
Metric
The owner spends less time coordinating
Collaborators are more autonomous
Information is no longer fragmented
Reduction of manual forwards per session
Session accesses without owner intervention
Percentage of files uploaded directly to MVSSIVE vs external links
Business Outcomes
How would we know the business benefits?
Objective
Metric
MVSSIVE becomes part of the creative flow
The feature drives conversion
90-day retention vs users without sessions
Upgrade rate upon reaching free plan limit
Validating the direction
To confirm that the solution was aligned with both user needs and business goals, I mapped the value proposition against the customer segment. The fit was clear: the user's core pains and jobs connected directly to what the product needed to offer.
Persona
Fernando
Status:
Mid-career independent producer.
Gender:
Male
Value Proposition
Customer Segment
Pains
Gains
Jobs
FIT
Products and Services
Pain Relievers
Gain Creators
Frustration from not being able to focus on the creative aspects
Fear that disorder will affect the final outcome
Information scattered across multiple tools
Fear of not fulfilling their role as host properly
Time lost answering repeated questions
Shared visibility for all participants
Reduction of manual forwards
Quick access to relevant information
Visual clarity about participants and versions
Simple start that reduces friction
Centralization that lowers operational stress
Reduce manual steps
Having all information centralized from the start
Strengthen reputation as a reliable producer
Decrease dependence on multiple tools
A structured session within the system that centralizes participants, files, and context from its creation.
The canvas confirmed the direction: the user's core pains and jobs pointed to a structural solution, not a feature fix. That led us to ask:
Automatic centralization of information in one space
Manage a musical session with multiple artists
Peace of mind that nothing important will be lost
BACK TO HOME
Next Case Study
MVSSIVE
Industry
MusicTech
Product
Music collaboration platform (SaaS)
Year
2025
Role
Product Designer
Project Summary
Organizing musical collaboration from the first session
MVSSIVE is a SaaS platform for the music industry. This case focuses on the design of a feature that didn't exist yet: a structured space for music sessions, where producers could centralize participants, files, and context from the start — instead of coordinating everything across WhatsApp, Dropbox, and voice messages.
The challenge was strategic: MVSSIVE only intervened at the end of the creative process. This feature moved the product upstream, making it part of the workflow from the very beginning — with direct impact on retention, adoption, and conversion.
Product Designer
2025
UX Strategy
UX UI Design
Industry
MusicTech
Product
Music collaboration platform (SaaS)
Year
2025
Role
Product Designer
Usage Context
The Moment Music Is Created
A music session is not an isolated moment but a complex environment where multiple dynamics coexist simultaneously. These dimensions define how music is created and why the context in which it happens is so relevant to the creative process.
Collaborative Work
Multiple people participate, working together in real time.
Creative and Technical Decisions
Decisions made during the session directly impact the final song.
Multiple Versions
Ideas are tested, others discarded, and different versions of the same song are generated.
Focus and Continuity
The flow of exchange and coordination influence the outcome of the creative process.
CORE INSIGHT
Working on real music sessions, we began to notice a pattern repeating over and over. Important information from each session—schedules, files, versions, feedback—was scattered across multiple conversations and channels. Nothing was "lost," but it wasn’t where it needed to be. The problem wasn’t a lack of tools, but a lack of structure.
CORE INSIGHT
The problem
Was there a problem worth solving?
When music producers coordinate collaborative sessions, the information ends up scattered across multiple places:
- A WhatsApp group to coordinate the day
- Dropbox for the files
- Voice messages for feedback
- External links for the versions.
Nothing is lost, but nothing is where it should be.
The result is a music producer who spends more energy managing the chaos than focusing on the music. And when handling multiple sessions simultaneously, that burden multiplies.
The problem wasn't the lack of tools. It was the lack of structure.
Impact of the problem on the user
Who suffers from this problem?
Tech Savviness: Intermediate–High.
Fernando
Independent music producer
When I'm managing a session with multiple artists, I need to have everything organized from the start so I can focus on the music without chaos taking control.
OBJECTIVES
- Maintain session control
- Avoid delays in launches
- Protect the quality of the final result
- Appear professional to the artists
PAIN POINTS
- Simultaneous messages from multiple sessions
- Feeling that a version was lost
- Having to resend files and update information
- Fragmented information across multiple tools
NEEDS
- Centralize information from the start
- Structure participants and versions
- Reduce dependence on multiple tools
- Maintain clarity even when managing multiple sessions
JTBD — Job To Be Done
As the session owner..
FUNCTIONAL JTBD
When I'm managing a music session with multiple artists
+
I want to keep all the session information organized in one place
+
So that I can focus on the creative process without interruptions or stress
EMOTIONAL JTBD
When information from multiple sessions overlaps
+
I want to feel in control and clear-headed
+
So that the chaos doesn't interfere with my creative focus
SOCIAL JTBD
When other people depend on me during a session
+
I want to respond with clarity and speed
+
So that the collaboration flows without friction or confusion
Business opportunity
Why did this problem matter to the business?
Until that point, MVSSIVE only intervened in the final stage of the music process: when the song was finished and ready to be published. Its role was to centralize files, metadata, and contributors.
MVSSIVE
The problem was that it came in late. Much of the value, decisions, and versions that define a song are created much earlier, during the music sessions. By not being present at that moment, the product relied on external tools at key stages and didn't capture the context from the start.
MVSSIVE was limited to a closing tool, when it could have become the official source of truth from the beginning.
The strategic opportunity
Integrating the session as a structured entity within the system meant supporting the creative process from the start, preserving the context from the origin, and connecting creation and publication within the same ecosystem.
OPORTUNIDAD
CREATIVE PROCESS / SESSION
UPLOAD FILE
COLLABORATIVE PUBLISHING
No support
OPPORTUNITY
MVSSIVE
MVSSIVE
Business objective
Make MVSSIVE a structural part of the creative process from the beginning, increasing retention, adoption, and conversion within the subscription model.
HMW
How can we preserve the context of each session without disrupting the producer's creative flow?
Solution
The session as a structured entity
The solution was to give each music session its own dedicated space within the system: an independent container that groups participants, files, versions, and context in one place. Each session has its own identity, separate from the rest and accessible from the start.
Experience Design
The experience of creating a session
The entry point
From their profile, the owner has a centralized view of all their sessions with real-time status — upcoming, in progress, completed. Creating a new session is an action available from the same place where all their activity lives. There's no need to leave the system or open another tool.
The session takes shape
When creating a session, the owner defines from the start all the information that was previously scattered: name, date, study, location, publisher. This act of creation is not just a form — it's the moment the session becomes an entity with its own identity within the system.
The session as a structured container
Once created, the session exists as its own space: it centralizes participants, roles, statuses, and contextual information in one place. The owner can see who is inside, who has a pending invitation, and how long each collaborator has been present — without needing to ask on WhatsApp.
[M]
Scanning this QR will take contributors directly to the session join form.
As is scenario
BEFORE
The producer coordinates everything externally: a WhatsApp group for the date, Dropbox for the files, voice messages for feedback. Before the music starts, they are already managing the chaos.
To be experience
AFTER
The producer creates the session in MVSSIVE and all the information is centralized from that moment: name, date, studio, participants. The context exists before the session begins.
The session stops being a scattered conversation and becomes an entity with its own structure.
UX Outcomes
How would we know it worked?
Objective
Metric
The owner spends less time coordinating
Collaborators are more autonomous
Information is no longer fragmented
Reduction of manual forwards per session
Session accesses without owner intervention
Percentage of files uploaded directly to MVSSIVE vs external links
Business Outcomes
How would we know the business benefits?
Objective
Metric
MVSSIVE becomes part of the creative flow
The feature drives conversion
90-day retention vs users without sessions
Upgrade rate upon reaching free plan limit
Validating the direction
To confirm that the solution was aligned with both user needs and business goals, I mapped the value proposition against the customer segment. The fit was clear: the user's core pains and jobs connected directly to what the product needed to offer.
Persona
Fernando
Status:
Mid-career independent producer.
Gender:
Male
Value Proposition
Customer Segment
Pains
Gains
Jobs
FIT
Products and Services
Pain Relievers
Gain Creators
Frustration from not being able to focus on the creative aspects
Fear that disorder will affect the final outcome
Information scattered across multiple tools
Fear of not fulfilling their role as host properly
Time lost answering repeated questions
Shared visibility for all participants
Reduction of manual forwards
Quick access to relevant information
Visual clarity about participants and versions
Simple start that reduces friction
Centralization that lowers operational stress
Reduce manual steps
Having all information centralized from the start
Strengthen reputation as a reliable producer
Decrease dependence on multiple tools
The canvas confirmed the direction: the user's core pains and jobs pointed to a structural solution, not a feature fix. That led us to ask:
Automatic centralization of information in one space
A structured session within the system that centralizes participants, files, and context from its creation.
Manage a musical session with multiple artists
Peace of mind that nothing important will be lost
BACK TO HOME
Next Case Study