The full library. Pick a route, follow the modules, ship a workflow.
Each module is a working playbook with prompts, templates, and a downloadable artifact you can use in production the same day.
modules in the library
role routes through the library
start today, finish when you finish
12 modules. Routes order them. You ship from any of them on day one.
- 01
Foundation
all routesno code requiredClaude Code setup for music professionals. We start from a blank machine. By the end of this module Claude Code is installed, logged in, configured for the music industry voice, and connected to your first project folder.
Most of the course assumes you can drop a CSV, a PDF, or a folder of stems into a chat and ask Claude to do real work. This module makes sure that part is boring before we get to the interesting parts.
/ What you ship- Claude Code installed on macOS or Windows with permissions configured
- Three working folders set up for label ops, A&R, and release admin
- First prompt template saved, tested, and version controlled
- MCP server scaffolding ready for module 10
/ Tool stackClaude CodeiTerm or TerminalVS Code or CursorGitHub Desktop/ Downloadable artifact01-foundation-starter.zip (CLAUDE.md template, folder skeleton, 5 baseline prompts) - 02
Stack inventory
all routesdiagnosticMap every tool, data source, and recurring time sink in your current week. This is the only module with a worksheet. You finish with a one page diagram of where your hours go and which 3 workflows the rest of the course should target first.
Operators who skip this module ship random automations that save 4 minutes a week. Operators who do this module ship the right 3 automations and recover 6 to 12 hours.
/ What you ship- Time sink audit across 1 representative week
- Tool inventory with API access status flagged
- 3 candidate workflows ranked by hours saved per month
- Route confirmation (you may switch routes after this module)
/ Tool stackNotion or LinearClaude (chat)Toggl or Rize (optional)/ Downloadable artifact02-stack-inventory-worksheet.pdf + claude-prompts.md - 03
Playlist pitch automation
artistsmanagersmarketingSubmithub, Groover, and a Claude pitch generator that writes 12 platform-specific pitches from one release brief. Includes the curator response triage workflow that flags real curators vs payola.
Output is a pitch pack ready to paste into 5 platforms plus a tracking sheet that updates from your inbox.
/ What you ship- Pitch generator prompt that produces 12 platform-specific variants
- Curator triage filter that scores responses
- Tracking sheet that auto-updates from Gmail labels
- First 10 pitches sent during the module
/ Tool stackSubmithubGrooverClaudeGmail filtersGoogle Sheets/ Downloadable artifact03-pitch-pack-template.zip (pitch generator, response triage prompt, tracker) - 04
Royalty audit and variance analysis
label opsadminCurve or Reprtoir export plus Claude on the CSVs. You learn the 7 variance patterns that account for 90% of label statement disputes (DSP rate change, takedown reversal, ISRC duplication, splits misroute, advance recoup miscalc, FX timing, missing territories).
By the end you have a 20 minute monthly sanity check that flags the bad rows before you send statements out.
/ What you ship- Monthly statement sanity check that runs in 20 to 45 minutes
- 7 variance pattern detectors as named Claude prompts
- Outlier flag report with sample dispute language
- Reconciliation log that survives an audit
/ Tool stackCurve or ReprtoirClaudeExcel or NumbersStripe (for advances)/ Downloadable artifact04-royalty-audit-pack.zip (7 variance prompts, sanity check script, dispute templates) - 05
Catalog reconciliation and valuation
label opsA&RCatalogIQ bridge plus Beatdapp fraud flag. You learn how a catalog gets valued for a sale, a loan, or an internal forecast. We walk a real Latin catalog through reconciliation, fraud flag, and a 5 year NPV model in the same session.
End state: you can quote a defensible valuation range on a 200 track catalog in under 2 hours.
/ What you ship- Catalog reconciliation across DSP, distributor, and society reports
- Fraud flag pass via Beatdapp methodology
- 5 year NPV model with 3 decay assumptions
- Valuation memo template ready for buyer or lender
/ Tool stackCatalogIQBeatdapp methodologyClaudeExcel/ Downloadable artifact05-catalog-valuation-pack.zip (recon prompts, NPV model, memo template) - 06
Contract review with AI
managerstour mgrlabel opsSpellbook, Juro, and Claude playbook prompts. You build a 12 point review checklist that catches the issues that actually matter (term, territory, recoupment, controlled comp, audit rights, SoundExchange, sample clearance, key person, MFN, sunset, change of control, dispute venue).
By the end you can turn around a deal memo in 20 minutes that used to take 4 hours.
/ What you ship- 12 point review checklist as a Claude playbook prompt
- Deal memo template that copy pastes into Notion or email
- Red flag heat map for new contracts
- Counterparty playbook (label, manager, publisher, sync agent)
/ Tool stackSpellbook or JuroClaudeNotion or Linear/ Downloadable artifact06-contract-review-playbook.zip (12 point prompt, memo template, redlines library) - 07
A&R signals from socials and DSPs
A&RChartmetric MCP plus Viberate. You build a scout agent that watches a genre, a region, or a label cohort and DMs you a weekly 5 artist Slack digest with the data that justifies a meeting.
Includes the Beatdapp style fraud filter so you do not chase fake numbers.
/ What you ship- Genre-specific scout agent that posts to Slack weekly
- Fraud filter that drops bot-inflated tracks
- Deal-ready brief generator (one click, 1 page output)
- Watchlist that promotes from radar to meeting
/ Tool stackChartmetric (MCP)ViberateSlackClaudeBeatdapp methodology/ Downloadable artifact07-scout-agent-pack.zip (agent config, fraud filter, brief generator) - 08
Fan analytics and content cuts
marketingartistsproducersSpotify for Artists API, Descript, and Opus Clip. You build the loop that turns a single release into 20 platform-ready cuts plus a weekly fan health dashboard.
End state: release week content stops being a 3 day scramble.
/ What you ship- 20 cut auto-generation from one master video or audio file
- Fan health dashboard that updates from S4A API
- Top market alert that fires when a new city crosses a threshold
- Caption pack in EN and ES for each cut
/ Tool stackSpotify for Artists APIDescriptOpus ClipClaude/ Downloadable artifact08-content-loop-pack.zip (cut generator, dashboard template, caption prompts) - 09
Release planning and asset packs
artistsproducersmanagersFreebeat, Neural Frames, and ElevenLabs dubbing. You build the release-day asset pack workflow that produces visuals, vertical cuts, and a dubbed teaser in the time it used to take to write the email announcing the release.
By the end you have a single command that takes a stereo master plus a press shot and returns a launch folder.
/ What you ship- Release-day asset pack in 90 minutes (was 2 days)
- Vertical, square, and 16:9 cuts with brand-safe color
- ElevenLabs dubbed teaser in EN plus your target market language
- Launch checklist that survives a chaotic Friday
/ Tool stackFreebeatNeural FramesElevenLabsCapCut or Descript/ Downloadable artifact09-release-day-pack.zip (asset pack workflow, dub prompts, launch checklist) - 10
MCP fundamentals
A&Rmarketinglabel opscapstone prepBuild your own music agent. This is the first capstone module and the only one with a small bit of TypeScript, walked through step by step. You ship a working MCP server that connects Claude to a music data source you actually care about (Chartmetric, Spotify for Artists, your own catalog DB).
By the end you understand why MCP changes the game for music ops and you have a server you can extend on your own.
/ What you ship- First working MCP server deployed locally
- Connection from Claude Desktop or Claude Code verified
- 3 tools exposed (search artist, pull metrics, generate brief)
- Deploy path documented (Cloudflare Workers walkthrough)
/ Tool stackClaude CodeMCP TypeScript SDKCloudflare Workers (optional)GitHub/ Downloadable artifact10-mcp-starter.zip (server scaffold, deploy guide, 3 example tools) - 11
Tour ops automation
tour mgrmanagerMaster Tour, Claude PDF read, and advance sheet auto-generation. You build the workflow that takes a venue tech pack PDF and returns a filled advance sheet, a hospitality rider gap report, and a settlement template tied to the contract.
End state: a 15 minute prep block replaces a 3 hour panic on show day.
/ What you ship- PDF tech pack to advance sheet in 15 minutes
- Hospitality rider gap report that compares contract vs venue offer
- Settlement template prefilled from contract terms
- Day-of manifest that prints to phone
/ Tool stackMaster TourClaude PDF readGoogle SheetsAdobe Acrobat/ Downloadable artifact11-tour-ops-pack.zip (advance workflow, settlement template, manifest generator) - 12
Capstone
all routesship requirementShip one workflow, document it, submit it. You pick one workflow from your route, take it from prototype to a thing you actually run weekly, and submit a 1 page write up plus a short Loom.
Capstone submissions get featured in the next monthly drop with attribution. This is where the course becomes a portfolio asset.
/ What you ship- 1 production workflow you run weekly without thinking
- 1 page write up that explains the workflow to a non technical operator
- Loom or screen recording walking through the workflow
- Capstone certificate of completion
/ Tool stackLoom or DescriptNotion or Google DocsYour route stack/ Downloadable artifact12-capstone-template.zip (write up template, Loom script, submission checklist)