The Release Cycle

What you'll be able to do

• Map any release onto the four-phase cycle and aim ads at each phase's actual job
• Price what a pre-save is really worth and campaign for it accordingly
• Run the sustain phase most artists skip - where catalog quietly becomes a career

The short version: The modern single cycle has four ad phases: announce (build the pool), pre-save (convert attention into release-day automation + owned data), release week (the surge), and sustain (the $5-10/day phase almost everyone skips, where songs outlive their algorithm bump). It's DAS 201's event lifecycle with one glorious difference: the product never expires. A song isn't inventory that dies at midnight - it's catalog forever, which changes the math on everything after week one. This module is the cycle; the streaming measurement problem it creates gets its own module next.

The lifecycle, but the product is immortal

If you took DAS 201, this structure will feel familiar - announce, convert, surge, sustain is the event lifecycle wearing a different jacket. The difference is profound though: the event's product expires at midnight; the song never does. Which means:

• The urgency levers are weaker (no honest "almost gone" exists for a stream - scarcity theater around an infinite good reads false instantly)
• The sustain phase is INFINITELY long if the song earns it - and the compounding thesis (DAS 201 Module 10) applies to catalog even harder than to shows
• Release DAY matters less than release MONTH, and release month matters less than whether the song is still finding people in month six

Phase 1 - Announce (the pool, again)

DAS 201 Module 3's doctrine transfers almost verbatim: the announce's product is the retargeting pool, not the likes. Teaser content (the hook snippet, the studio moment, the cover-art reveal) runs across the Module 1 node network - each identity teasing in its own voice - building video-viewer and engager audiences that release week will fire at. The multi-node version has a bonus: the fan node can "leak" enthusiasm ("he played an unreleased one and I haven't recovered") that the artist canon can't post without spoiling the reveal.

Phase 2 - Pre-save (the honest appraisal)

What a pre-save actually IS: permission for the DSP to auto-add the song to a listener's library/playlist at release. What it's WORTH, honestly:

• Directly: a guaranteed day-one stream and library placement - modest but real algorithmic kindling, in whatever way DSP systems weigh early engagement (the systems are black boxes; we don't pretend otherwise)
• More valuably: the smart-link signup flow captures email and data on the way through - a pre-save campaign is a DATA campaign wearing a streaming costume (DAS 201's presale logic, exactly)
• Most valuably: it's a cheap conversion event your budget can learn on (DAS 100 Module 5's math: smart-link pre-save conversions are affordable enough to hit 50/week at indie budgets)

Campaign accordingly: pre-save ads to the warm pool, optimized on the smart-link conversion event where your link provider supports pixel/CAPI passback (next module's territory), with the fan and HQ nodes doing testimony-and-news duty alongside the artist's canon announce.

Phase 3 - Release week (the surge)

The DAS 201 Module 4 run sheet, translated: everything approved as dark posts days early · warm surge at 00:01 ("it's out" to every pool audience + the pre-save list via email/SMS, same hour) · cold behind it carrying the strongest creative · all four identities firing their registers (canon announce, fan testimony, HQ "out now" news, meme native angle). One release-week honesty note: the first 48 hours' numbers are the pool converting, not the world discovering - judge the SONG by week three, not day two (DAS 100 Module 8's judge-weekly doctrine, plus patience).

›Go deeper: aligning with DSP editorial timelines

The non-ad deadline that shapes the ad calendar: DSP editorial playlist consideration (e.g., Spotify's pitch flow) requires submission ahead of release - which effectively sets your minimum announce-to-release runway. The ads don't influence editorial decisions directly, and anyone selling you otherwise is selling you something; what ads CAN do is make the release look alive during the window when it's being algorithmically and humanly evaluated - real engagement, real saves, real follows. Build the calendar backward from the pitch deadline, and treat editorial as a lottery ticket you buy with a good release, not a plan.

Phase 4 - Sustain (where careers actually accrue)

The phase almost everyone skips, and the track's biggest genuinely-contrarian doctrine: after the release-week spike fades, a song that showed ANY life earns a $5-10/day sustain ad - the strongest creative from release week, running to cold audiences, indefinitely, judged monthly on blended results. Why this works: the song is now catalog (immortal, remember), the creative is proven, the learning is accumulated, and $200/month keeping a good song finding new people is the cheapest fan acquisition an artist can buy. Multiply across a catalog and this becomes the label-scale doctrine DAS 203 is built on. The fan who finds the six-month-old song today experiences it as new - because for them, it is.

From the field

An artist's team ran the standard pattern: heavy release week, silence by week three, on to the next single. We kept one prior single - a mid-performer, not even the hit - on an $7/day sustain with its best release-week creative. Four months later it had quietly outstreamed the "bigger" singles' launch spikes combined, and its listener-to-follower conversion seeded the next release's warm pool. The next announce launched to a measurably larger owned audience than any before it. Nothing viral happened. Nothing viral NEEDED to happen - that's the point of the phase.

Common mistakes

• Scarcity theater around an infinite good ("last chance to stream"?? it's a song, it lives there)
• Treating the pre-save as the goal instead of the data-capture flow it rides on
• Judging the song on day-two numbers (that's the pool converting, not the verdict)
• The silence-by-week-three pattern - killing sustain exactly when the compounding starts
• Announce runway shorter than the editorial pitch window (calendar built forward instead of backward)

Take-home

Release Cycle Ad Calendar - the four phases mapped week by week against the editorial pitch deadline, per-phase identity assignments from the routing table, the pre-save campaign spec, and the sustain-phase decision rule + monthly review ritual.

Sources & dates

DSP editorial pitch mechanics per public platform documentation (accessed July 2026) · DAS 100 + DAS 201 cross-references as cited · cycle model is Darkroom practice, presented as such

Learn more

Optional extra credit. Nothing below is required for the quiz, the certificate, or the job - the full lesson is above. This is for the sickos who want more.

• Spotify for Artists documentation: the editorial pitch flow and its deadlines - the calendar anchor, from the source