Case Study 1: The Four-Week Runway

What follows is a composite — June Okada isn't a real person, and her numbers aren't data. They're assembled from the documented anatomy of many small independent releases into one honest, typical story, because "typical" is exactly what the internet refuses to show you: release case studies online are survivor stories with six zeroes. The numbers below are illustrative of scale, not statistics — and the point of the study isn't the numbers anyway. It's the sequence. The sequence is the part you can copy.

June Okada makes bedroom indie-pop in a rented room in Portland — voice, thrifted nylon-string guitar, soft synths, drum machine. Two singles out, released the way most first singles get released: finished Thursday, uploaded Friday, live the following Wednesday at whatever hour the stores got around to it. Combined lifetime streams of both: a number she stopped checking. Total pre-release activity: one excited post.

For single three — "Porch Light," two minutes and forty-one seconds of dusk-colored electric piano and close-miked vocal — she decides to run the release the way the books say to run it. Four weeks of runway, every gate passed in order. What follows is her calendar, week by week, including the parts that didn't work. Especially those.

Week -4: Upload Day

Monday. The master has been finished for nine days, which has been agony, and the agony is the test: June has learned that the gap between "the master is finished" and "the release is finished" is precisely the gap this runway exists to fill.

She fills her metadata card before she opens the upload form — title, artist string (she triple-checks it against her existing artist page: June Okada, no middle initial, the way releases one and two established it), writers (her legal name, plus her roommate Theo's — different Theo; the world is full of them — who co-wrote the bridge and whose name nearly didn't make it onto single two until an awkward conversation fixed it), genre. Genre takes her twenty minutes, and the reference-playlist test earns its keep: her instinct says Singer/Songwriter because she sings and writes; her three reference tracks — the records "Porch Light" honestly sits between — all shelve under Indie Pop. The router wins. Indie Pop.

The upload itself takes eleven minutes. The distributor assigns the ISRC and UPC; she logs both in a spreadsheet that now has three rows and a grand title: OKADA CATALOG. Release date: Friday, twenty-nine days out. The dashboard accepts it without ceremony, which feels anticlimactic until she remembers that anticlimax is the point — drama on upload day means something's wrong.

Wednesday. The release clears distributor review and shows "delivered" — and now the pitch portal inside her claimed artist profile can see it. She writes the editorial pitch the way the form invites: what the song is (genre, mood, instrumentation tags), the one-paragraph story (the porch is real; the light is her grandmother's), her plans for the release (the honest, modest list). She resists the urge to write "this is the one" because every pitch in the pile says that. Submitted, twenty-seven days out — weeks past the stated minimum, which is the only relationship with a deadline she can control.

Friday. Pre-save link generated and tested on her own phone, both major platforms. It works. She doesn't share it yet. Nothing announces this week. The runway has a shape: this week was for the machine.

Week -3: The Storefront and the Announcement

Monday. Profile pass. Her artist pages were claimed back at single one (one verification took four days — the reason this chapter says weeks early, not days), but claimed isn't dressed: she swaps the bio for one that reads like a person, uploads photos that survive thumbnail size, pins the pre-save where the platform allows an upcoming-release feature. Then she runs the storefront audit against three artists one shelf up from her — and steals, in the legitimate way: their photo crops are intentional, their bios lead with sound instead of biography, their catalogs read as a sequence. Two hours of fixes.

Wednesday. Announcement. One post, three platforms, the artwork and the date and the pre-save link. The content drip starts behind it — she has process material from making the track (a voice memo of the original chorus idea; her hands on the electric piano; the rain that's audible in the vocal take if you know where to listen), and she schedules a trickle of it across the next three weeks. (The craft of that — what to post, how often, why process material works — is its own discipline and another chapter's business. For this study, what matters is that the drip exists and points at one link.)

Pre-saves by Sunday: 19. Almost all of them people she could name. This is normal, and June has decided in advance not to be insulted by normal.

Week -2: The Push and the Catch

Tuesday. The verification pass — the gate everyone skips. She checks the release in the dashboard: scheduled, correct date, correct artwork. Then she proofreads the metadata against her card and catches it: the writer field lists her legal name and Theo's artist alias, not his legal name. Her stomach drops the familiar half-inch; then she remembers this is precisely why the pass exists, two weeks out, while corrections are a form instead of a crisis. Fixed through the distributor in a day.

The rest of the week is the pre-save push: a second ask, phrased differently (the first post announced; this one invites — "it's three weeks of patience or one tap now"), plus direct messages to the dozen people who actually share her stuff, plus Theo-the-roommate sending it to his people, because a featured writer is a second warm audience. Pre-saves by Sunday: 56.

Week -1: Staging

Quiet week by design. She confirms the release shows as "upcoming" on the platforms that support it. She builds her release-day checklist from the chapter's table, with her own additions (her grandmother gets the first text, before any platform does). She stages the link page so one switch flips it from pre-save to listen now. The last content posts are scheduled through the weekend. She sleeps badly, which isn't on the checklist but is on every real one.

Pre-saves by Thursday: 88.

Day Zero: Friday

12:04 a.m. New Zealand has it. She watches "Porch Light" dawn westward across the planet's midnights, store by store, which no one warned her is the single most science-fictional feeling in independent music.

7:00 a.m. her time. Live everywhere she checks. The checklist runs: full playthrough from the store (correct master, no truncation, the encode survives the cymbal wash in the bridge); credits render — both legal names; artist-page mapping correct; link page flipped; looping visual live; the warm-audience messages go out in the order that matters (grandmother, group chats, mailing list of 71 people, then the public posts).

End of day one: 412 streams. 96 saves. 88 pre-saves converted to library adds at midnight, which is most of why the save number looks like that. Three user playlists she's never heard of add it — eleven, forty, and two hundred followers respectively. The editorial pitch: nothing. No placement, no rejection, no signal at all, which is the usual shape of that silence and worth knowing in advance.

She logs the numbers in the ledger and closes the dashboard, per the checklist, on the first try, which she considers her largest single achievement of the week.

The Week After: The Second Friday

Saturday through Thursday drift along at 60–90 streams a day — her own audience finishing its first listens, the drip posts converting stragglers. Then Friday +7 happens: the follower-feed cycle. The platforms' new-release features pick the track up for people who follow her but missed launch week, and the day posts 341 streams — nearly a second release day she didn't lift a finger for, except that she lifted every finger four weeks earlier, because a release that isn't in the system on time doesn't ride that cycle at all.

Thirty days out: about 3,900 streams, 380 saves, five user playlists, eleven new followers per week against three per week before. Not a hit. Not trying to be. Roughly eight times what either earlier single did in its first month — same artist, same genre, frankly similar songs.

What Actually Moved the Numbers

This is the part to read twice, because it's the part the survivor stories get backwards.

The pre-save campaign didn't add listeners; it concentrated them. Nearly everyone who pre-saved would have streamed the song eventually. The campaign's work was temporal: it moved "eventually" to midnight, and the resulting day-one density — saves, adds, completions in a tight window — is the signal the discovery systems can actually see. Same love, sharper spike.

The editorial pitch "failed" and was still worth two hours. No placement — the overwhelmingly common outcome, worth saying plainly. But the pitch form's structured data (genre, mood, instrumentation) rode along with the release as metadata seasoning, and the pitch exists at all only because the runway did. A lottery ticket whose form improves your routing is a strange but real bargain.

The second Friday was the quiet winner. The follower-feed cycle delivered the biggest non-launch day for free. Day-of releases skip it; June's two earlier singles never saw it. This single feature of the system probably accounts for more of her eight-times improvement than anything she posted.

The verification pass paid for the whole month. One writer-credit error, caught at Week -2 as paperwork instead of at release as a live mistake attached to someone else's name. Every gate in the runway is really insurance, and insurance is invisible when it works.

And the honest null result: the content drip's direct numbers were modest — a few dozen link taps. Its real function was keeping the warm audience warm enough to act in the same week. Distribution can concentrate attention; it cannot manufacture it. That's the other chapter's work, and June's next campaign starts there.

One footnote on Friday itself. June released on the default day and shared it with every major-label drop on the planet. For her — a playlist-and-feed artist whose listeners arrive through the platforms' own rhythms — the default was right. But she logged the alternative in her notes for a future experiment: an artist whose audience comes from her own channels could test a quieter weekday and trade the platform rhythm for empty shelf space. Default Friday; deviate on purpose; either way, decide — don't drift.

The Template

Copy the sequence, not the numbers:

WEEK -4   □ metadata card final → upload → date locked (Friday, 4+ wks)
          □ codes logged in catalog ledger
          □ editorial pitch submitted (claimed profile)
          □ pre-save link generated + tested. Tell no one yet.
WEEK -3   □ profiles dressed; storefront audit vs 3 reference artists
          □ announce once; pre-save live; content drip begins
WEEK -2   □ VERIFICATION PASS: dashboard vs metadata card (fix now,
            not later) □ second pre-save ask □ collaborators activated
WEEK -1   □ "upcoming" visible □ checklist staged □ link page ready
DAY 0     □ store-side playthrough □ credits render □ mapping correct
          □ flip links □ warm audience first □ log numbers, close tab
WEEK +1   □ ride the second Friday □ thank-yous □ next song begins

June's runway, reduced to the part that transfers. The numbers were hers; the sequence is yours.

The four weeks didn't make "Porch Light" a better record. They made sure that every person likely to love it found out in the same seven days — and that the machine was watching when they did.