2
1 Comment

Building an AI music channel that adapts to what phase of the build you're in

I've been running a faceless YouTube channel (Builder Protocol) that generates long-form instrumental music for founders and developers, split into three modes depending on what part of the grind you're in: morning execution, late-night coding, dead-silent deep work.

Started from a dumb annoyance — most "focus music" playlists don't know what kind of focus you're in. 6am execution energy isn't 1am debugging energy, and neither is the kind of silence you need when you're stuck on a hard problem and just need the noise gone.

Just shipped the latest Lock In session — four hours of cold, rhythmic, late-night coding music, generated with Suno and assembled by hand (chapters, pacing, visual sequencing — no autopilot template).

Still early, building in public, figuring out what actually keeps people locked in versus what just plays in the background. If you code past midnight, curious what you'd want from something like this: https://youtu.be/5JPwwM5MyT8

on August 17, 2026
  1. 1

    "Focus music doesn't know what kind of focus you're in" is a genuinely sharp wedge, it separates you from the ten thousand other Suno focus channels. 6am execution vs 1am debugging vs stuck-and-need-silence are real different states nobody else segments by. Lead with that, it's the only thing making you not a commodity.

    And match the trigger not the vibe: people don't search "focus music," they search the moment, "late night coding," "music for when you're stuck." Each mode is a different search intent, a different thumbnail, three doors not one channel.

    Past midnight I'd want zero variation that pulls attention, no drop, no build, nothing that makes me look up. Late-night music fails the instant it gets interesting. Is Lock In flat by design, or does it still have dynamics?