What is Artist Coordination?
Artist Coordination gives music teams one shared record of which profiles and releases are really an artist's, who approved each version, and every platform fix, tracked until someone checks it.
Frequently asked questions
What the product does, what stays with your distributor and the platforms, who can open an artist's file, and how the pilot works.
Artist Coordination gives music teams one shared record of which profiles and releases are really an artist's, who approved each version, and every platform fix, tracked until someone checks it.
Managers and independent labels use it to coordinate profile claims, release approvals, and platform corrections across the artists they represent. Artists use it to approve exact versions, grant representatives specific permissions, and keep a portable record of every decision.
In four steps: confirm identity, approve exact versions, track each fix, and carry the proof. Identity, proof, approvals, and corrections belong to the same record.
The demo runs in your browser on fictional records. Play the correction story as the artist, representative, operator, and reviewer each take their step, then export the case history. Reloading the page resets it.
Your existing distributor stays in place. Approving a release version records the decision in the artist's file, and delivery keeps running through the distributor you already use.
A person submits each request through the platform's own correction process. Artist Coordination prepares the packet, records the submission and each reply, and keeps the case open until the change is checked.
A case holds one request per platform, and you name the platform on each request. Each request is tracked from Draft through Ready, Sent and Waiting for reply to Checked.
Confirming a profile records that the page is the artist's and that a second person reviewed the proof. Payments, licensing, and legal assignments stay with external providers and agreements.
They are optional. An existing public registry record on Base or Avalanche C-Chain can be linked in the artist's file as a reference, and linking it leaves the private case private.
A representative acts only within the permissions the artist grants: releases, cases, and reading the proof. Approving a release version for the artist also needs reviewed proof of the representative's authority.
Yes, at any time. Revoking access prevents future actions, and previous actions remain in the activity history.
Only when the artist turns on Suede staff access and selects the named operators and reviewers. The artist can turn it off at any time.
The selected proof, the requester's authority, the approved version, the platform requests, and the history, exported as printable HTML or structured JSON. Each export is logged in the activity history.
The proposed first pilot is three to five management or label teams. The private workspace is built and tested: confirmed-email sign-in with a second factor for privileged access, recipient-bound invitations, scanned evidence files, recorded exports, and an audit history. Private pilot access opens after activation and operating acceptance.
Email info@suedeai.ai with the subject Artist Coordination pilot. The public demo shows the connected workflow on fictional records today.
Rights and royalties: scoped rights claims with supporting evidence, versioned royalty recipients and shares recorded as instructions only, and transfer proposals with consent evidence and independent review.
Keep reading
Confirm identity, approve exact versions, track each fix, and carry the proof.
Play the correction story on fictional records, then export the case history.
The product, the team it is built around, and where it stands.
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