Valeria Shulakova · Senior product designer
Under NDA · no product visuals by designMusic CMS · NDA · B2B · Web · 2022 — 2024

From spreadsheets to one system for a music service's content and payouts

An internal CMS for a mobile operator's music service. It replaced spreadsheets and a half-working legacy tool with one catalogue shared by content, legal and finance teams.

Before
Content sheetTracks and metadata
Rights sheetAuthors and shares
Legacy CMSHalf of it no longer worked
Payouts sheetReconciled by finance
→
After
Content
Legal
Finance
One catalogueTrack, rights, playlists, reports
A simplified picture of the process, not the product's interface.
Role
Product designer
Team
Product manager, analysts, developers
Timeline
2022 — 2024, at Kvantera
Domain
Music content, rights and royalties
Status
Released to production · internal tool
Context

A catalogue kept alive in spreadsheets

Kvantera builds software for telecom and was later acquired by a top-3 mobile operator with 70M+ subscribers. Behind the operator's music service sits a catalogue of tracks, each with its authors, rights holders and royalties to pay.

An earlier CMS existed, but much of it no longer worked, and teams kept the catalogue alive in separate spreadsheets. The task was a new system, built from scratch, that would hold the whole process.

Before and after

What changed for the teams

Before
After
Track details, rights and payouts in separate spreadsheets
One record per track: file, cover, metadata, authorship and rights
Rights checked by hand, outside the catalogue
A track stays published only while its rights add up to 100%
Playlists assembled by hand from exports
Playlists built inside the system from the catalogue
Finance reconciled sheets to calculate royalties
Royalty reports generated from the same data
Three hard problems

Where the complexity lived

Content managersDifferent access levels
Legal
Finance
→
Scenarios on shared screens
Tracks and coversRights holdersRightsPlaylistsRoyalty reports
100+
use cases, each with its states and edge cases
Roles and scenarios as described in the brief, not the product's permission model.
01

Rights decide what is published

Challenge

A track can only be offered when its authorship and neighbouring rights are fully covered; a gap means a legal risk and a wrong payout.

Approach

With lawyers and analysts, I made rights part of the track record. Shares must add up to 100%; if they drop below, the track is taken off publication automatically.

Result

Content and legal teams work on the same record, and an incomplete track cannot stay live.

02

One catalogue, three teams

Challenge

Content managers with different access levels, lawyers and accountants need different slices of the same data.

Approach

I mapped tasks to roles and designed role-based dashboards and permissions on a shared set of screens.

Result

Each team sees its own work without a separate tool.

03

From catalogue to payout

Challenge

Royalty payouts depended on data spread across spreadsheets.

Approach

I designed royalty reports and financial dashboards that draw on the catalogue itself.

Result

Finance works from the same source as content and legal.

How I worked

From interviews to release

  1. 1

    Interviews with internal users about their tasks, workarounds and errors

  2. 2

    Specifications and legal requirements, worked through with analysts and lawyers

  3. 3

    100+ use cases, each with its states and edge cases

  4. 4

    Usability tests on key flows

  5. 5

    Design support through development

Next case
Turning visa and tax-residency rules into a calm daily tracker
Expatly · Own product · Deep case
→