Chasing Reverbs
How Claude Supports My Music Project
Solo project,
side gig, five years deep
Instrumental guitar music out of Cologne. Started in 2021 during the pandemic, released consistently ever since. Full-time day job, one kid — so whatever I build has to almost run on autopilot.
Five platforms,
zero spare time
My data lives in five different places, and none of them talk to each other. I needed one hub to consolidate it all — a single view I can open on the first of the month and know where things stand.
Nothing exotic
You probably have most of this already. What changes the game isn't the tools — it's having Claude as the glue between them.
Streamlit
Analytics Hub
A personal dashboard that runs locally on my machine. Drop in monthly CSV exports, open the browser, make decisions. Five views, one source of truth.
Discovery Mode — Campaign Analytics
Who does what
- Writes Python & Streamlit code
- Parses messy platform CSVs
- Builds Plotly charts from scratch
- Debugs errors & fixes edge cases
- Documents everything it writes
- Decide what to track & why
- Drop in fresh CSVs once a month
- Interpret the patterns I see
- Make the actual release decisions
- Keep the knowledge base updated
SmartLink
A single landing page linking to every platform — like Linkfire or Linktree, but on my own domain, fully under my control. Built in one evening.
Three reasons
to build your own
not theirs
forever
no surprises
Three free tools.
One evening.
Live demo next — link.chasingreverbs.com
EPK
Electronic Press Kit — the one-pager with all your information for labels, playlist curators, sync supervisors, and blog writers. Two versions, same source: a PDF to attach, and a web page to link.
From knowledge base
to professional deliverable
- Two pages, email-ready
- Attach to pitch emails & sync outreach
- Works offline, prints well
- Same content, every time
- Live on its own subdomain
- Share a link instead of a file
- Always current, easy to update
- Branded & matches my covers
The trick: I keep a markdown knowledge base of everything about the project. Claude + that base = a polished EPK in one session.
Minimum viable
analytics stack
Don't build everything at once. Build the one view that answers your most urgent question — then grow from there.
Collect your CSVs in one folder
DistroKid, Spotify for Artists, Meta Ads — whatever exports you already have. Don't reformat them.
Ask Claude to build one chart
Pick the single question that bugs you most. "Is my ad spend paying off?" — that's a first chart.
Iterate when you need more
Every new question becomes a new view. In a year you'll have what I have — without planning it upfront.