My case: building a one-person AI music label — part 1, from zero to an album on streaming
A live build-in-public log: I'm testing the AI-music 'studio' model myself — a small digital label run by one person. Part 1: the setup — how the catalog gets made, the legal structure that owns it, distribution to streaming, and the YouTube strategy. No revenue claims yet; results get logged here as they land.
Solo operator · one-person venture studio in Europe (SEO · affiliate · micro-SaaS) · 25 August 2026 · updated 25 August 2026 · 3 min read
I wrote the honest breakdown of whether a solo can make money with AI music — the artist path versus the studio path, the economics, the spam purges. Fair question back: would I run it myself? I am. This is the live log of that experiment: a one-person AI music label, built the same way I build everything else — structure first, minimal ritual, real results or an honestly logged failure.
Part 1 — what’s built (the setup stage)
- The catalog. Produced with AI music tools on a paid plan — the paid tier is what carries commercial rights to the output — with my own concepts and lyrics as the creative layer, and every draft archived as authorship proof. Multiple genres and artist personas rather than one act: this is deliberately the studio model — breadth as inventory, not one name chasing luck. (I’m keeping persona names out of this log for now; results first, branding later.)
- An album, assembled and shipped. The first full album (blues) went through a standard digital distributor to Spotify and the other stores — real releases, real catalog, not files in a folder.
- The legal spine. My company owns the rights; the label is its imprint; songwriter credits use my real name. Same clean-setup discipline as any business: the asset is ownable and defensible before it earns.
- The YouTube layer. Channels built around long-form mood compilations — because watch-hours are YouTube’s real currency, and streaming’s fractions-of-a-cent make Spotify presence, not income. There’s a clock on this: YouTube’s partner thresholds are set to roughly double in early 2027, so channels started now have a window to qualify under the current bar.
- Two royalty pipes, one deferred. Master royalties flow from the distributor now; publishing/songwriter royalties need a collecting-society or publishing-admin registration that only pays off at scale — so it’s deliberately deferred until a real trigger (meaningful streams, or someone covering a track). Minimum machinery, added only when the numbers justify it.
Why this maps to everything else on this site
Strip the music out and it’s the same solo playbook: one owned asset (the catalog), boring compounding distribution (long-plays ≈ SEO), structure before revenue, and no invented numbers. It’s the studio path from the AI-music breakdown executed for real — and the same “craft, not spam” line: a focused catalog with human intent, not 500 generic uploads that platforms delete.
The log — results as they land
- 2026-08 (part 1, this post): catalog in production across several genres and personas; first full album (blues) live on streaming via a distributor; legal structure done (company → label imprint → personas); YouTube long-play channels launched and warming. Revenue so far: nothing worth reporting — as expected at this stage. Next checkpoints: first distributor royalty reports, channel watch-hour trajectory.
Updates get appended here with dates as real numbers arrive — wins and failures both.
Part of the personal log. The framework this case tests: can a solo make money with AI music?
Frequently asked questions
What exactly is this case testing?
How is the catalog actually made and who owns it?
Why YouTube long-plays instead of chasing Shorts or virality?
When will there be actual numbers?
Keep reading
My case: 40 game ideas → a playable portfolio, solo — part 1, the vibecoding assembly line
A live build-in-public log: I collected ~40 game ideas, shortlisted half, and I'm building the best into full production games — alone, with AI doing the heavy lifting. At one point 12 playable MVPs got built in half a day. Part 1: the funnel (idea → MVP → production), the distribution channels, and why this is a case study, not a jackpot bet.
My case: how a fleet of AI-built projects watches itself while I work on one thing
I'm not a strong developer, and I run a lot of AI-built projects — which used to mean silent failures piling up wherever I wasn't looking. So I built a self-reporting system: every project checks itself daily (or several times a day, by importance), surfaces errors from its logs the moment they appear, and I only switch over when something actually needs me. No more week-long silent outages, no more quietly lost conversions.
Three years of vibecoding: building a one-person portfolio with AI (2026)
What actually changed after three years of building with AI — not the code, but the mindset: treating your own effort as capital, running a portfolio of solo projects, and discovering the real bottleneck was never building.