Solopreneurship.eu
Behind the Scenes

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.

EU-focused
Konstantin Filatov

Solo operator · one-person venture studio in Europe (SEO · affiliate · micro-SaaS) · 25 August 2026 · updated 25 August 2026 · 3 min read

My case: building a one-person AI music label — part 1, from zero to an album on streaming

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?
The 'studio' model of AI music: not one artist chasing fame, but a one-person digital label producing a varied catalog across genres and artist personas, distributed to streaming, with YouTube as the audience layer — run with minimal manual effort, as a test of whether an AI-era catalog can become a small passive-income asset. I'm a producer testing a niche, not a musician seeking a career — that framing decides every choice below. Results (streams, payouts, what worked) get appended to this log as real numbers arrive; nothing here is projected.
How is the catalog actually made and who owns it?
Tracks are produced with AI music tools on a paid plan (which is what grants commercial rights to the output — the free tiers don't), with my own creative input on concepts and lyrics; drafts and working files are archived as proof of authorship. Ownership sits with my company, the label is its imprint, and distribution runs through a standard digital distributor to Spotify and the other stores. Songwriter credits use my real name. It's the same clean-setup logic I apply to everything else: structure first, so the asset is ownable and defensible before it earns a cent.
Why YouTube long-plays instead of chasing Shorts or virality?
Because the economics point that way. Streaming pays fractions of a cent, so the plan treats Spotify as presence and YouTube as the audience machine — and on YouTube, watch-hours are the currency: long-form mood compilations (a 40-minute focus or blues playlist) accumulate hours while a viral Short pays almost nothing without massive volume. There's also a deadline built in: YouTube's partner-program thresholds are set to double in early 2027, so channels started now have a window to qualify under the current, lower bar. Slow, evergreen, compounding — the same logic as SEO.
When will there be actual numbers?
When they're real. The catalog and channels are live and growing; streaming royalties report with a lag, and YouTube monetization has thresholds to clear first. As real figures land — streams, payouts, channel stats, what flopped — they get appended to the log below with dates. I don't publish projections or borrowed screenshots: this site's whole standard is verifiable reality, and this case follows it. If the model fails, the failure gets logged too.
Was this useful?

Keep reading