Label Admin

The exact path you follow.

1. 01

   Foundation

   Before any of this works, you need Claude Code installed, an Anthropic key, and one project folder you trust. Most label ops folks have never opened a terminal. We do it together in 30 minutes, including the part where you connect Claude to your Drive so it can read the same CSVs you read. No coding background assumed. The setup is a one-time cost that everything else compounds on.

   Example output

   A live Claude Code session reading a sample royalty CSV out of your Downloads folder and explaining what the columns mean.

2. 02

   Stack inventory

   Most label admins lose 6 hours a week to tool sprawl. Curve, Reprtoir, the distributor portal, the publisher dashboard, 4 different DSP backends, a Google Sheet someone built in 2021. We map every tool, every data source, every recurring report, and rank by hours-per-month-bleeding. That ranked list becomes your route through the next 8 modules.

   Example output

   A one-page stack map with 14 tools, 9 recurring reports, and the 3 highest-bleed workflows circled.

3. 04

   Royalty audit and variance analysis

   Statements come in monthly and nobody actually checks them. We build a Claude script that ingests last month and this month, flags any line where variance is over 15%, and writes you a one-page summary in plain English. Works on Curve exports, Reprtoir exports, and raw DSP statements. The version Bruce uses at DSTRO7 catches roughly $2K to $9K per month in misallocations.

   Example output

   A monthly variance PDF showing the 7 tracks where Spotify reported less than projected, with the suspected cause for each.

4. 05

   Catalog reconciliation and valuation

   Your catalog lives in 5 systems and none of them agree. CatalogIQ bridge plus Beatdapp fraud flags plus a Claude reconciler gives you one source of truth, a value estimate per asset, and a fraud risk score. This is the report buyers ask for in due diligence. Most labels can't produce it without 2 weeks of consultant time.

   Example output

   A catalog reconciliation sheet covering 412 tracks, with valuation range and 11 fraud-flagged streams flagged for follow-up.

5. 10

   MCP fundamentals

   MCP is how you give Claude direct access to your tools without re-uploading CSVs every session. Module 10 walks you through your first MCP server, a small one that connects Claude to your royalty database read-only. After this you stop pasting data and start asking questions of live data. The TypeScript is 40 lines, walked through line by line.

   Example output

   A working local MCP server that lets you ask Claude 'show me top 10 earners last quarter' and get an answer from your live database.

The 2026 stack for this seat.

3 deliverables that go on your LinkedIn.

Every route grad finishes with working automations they can demo on a call. Not certificates, working software.

12 to 16 hours total, self-paced over 2 to 3 weeks.

Self-paced means you start today and finish whenever the workflow ships. No cohort, no webinar, no scheduled call.

This route runs deepest on Pro. You also unlock the other 6.

Adjacent seats most route grads also pick up.