One file for each artist
An artist's file holds their profiles, proof, releases and cases: everything needed to fix a wrong artist page, in one place.
For managers & independent labels
Coordinate profile claims, release approvals, and platform corrections across the artists you represent. Keep the proof and the follow-up with the work.
Built around the team
An artist's file holds their profiles, proof, releases and cases: everything needed to fix a wrong artist page, in one place.
Managers and independent labels handle multiple artists, profiles, and release versions. The record keeps each handoff attached to the work.
Keep authority, proof, approvals, and correction history connected across existing distributor and platform processes.
Identity, proof, approvals, and corrections belong to the same record. Make the next decision with the record in front of you.
Your role in the file
A representative is a manager or label person acting with the artist's permission.
The artist invites your confirmed account email with the permissions selected. You sign in and explicitly accept.
With the releases permission, add songs, recordings and release versions. With reviewed proof of your authority, approve a version for the artist.
With the cases permission, open cases, pick proof, and mark requests ready, then follow each platform request to a checked result.
With the cases and proof permissions, export one case's packet for the next handoff.
In the demo, on fictional records
The demo follows Theo Park, manager of the fictional artist Mara Vale, after her single Paper Lanterns lands on the wrong artist's page on Example Music.
Example Music answers the request. Theo can only do what Mara allows here, and he adds the reply to the case as proof.
An independent reviewer who didn't open the case checks the reply against the request before anyone relies on it.
With reviewed proof in hand, the Suede operator who filed the request checks Example Music's page against it and marks the request fixed.
Each change adds a dated line saying who did it and in which role. Exporting a copy adds a line too.
Pilot
The proposed first pilot is three to five management or label teams.
Confirmed-email sign-in with a second factor for privileged access, recipient-bound invitations, scanned evidence files, recorded exports, and an audit history.
Keep reading
Representatives with scoped, revocable permissions.
Correction cases with per-platform requests and replies.
Exact release-version approvals and destinations.
Take it through a real product flow
Open the fictional artist file. Play the correction story as the artist, representative, operator, and reviewer each take their step, then export the case history.
Public demo · Fictional records · Your existing distributor stays in place