Chapter 37 Exercises

This set produces real deliverables: by the end of the Desk Lab you'll have an artifact inventory, a four-week campaign calendar, a submitted-or-submittable playlist pitch, a funnel design, and a live owned-audience channel — the actual launch infrastructure for your track, not homework about one. Work Part A first to load the frameworks, then do the Listening Lab before the Desk Lab: an hour spent deconstructing how working artists actually deploy their production artifacts will make your own calendar dramatically less generic. Two standing rules for the whole set. First, no invented numbers — where an exercise asks you to predict or evaluate growth, your answers stay qualitative or honestly hedged, exactly like the chapter. Second, everything you build obeys the platform-agnostic doctrine: if a plan item would stop making sense the next time a platform changes its rules, rewrite it until it's a principle wearing today's clothes. Exercises marked ★ have worked answers in the back of the book (Answers to Selected Exercises).

Part A: Conceptual Understanding

A1. The asset argument. ★ (10 min) A bandmate says marketing is beneath you both: "Good music finds its audience. We should spend every hour on the songs." Write the three-sentence reply that takes the objection seriously — the songs are the foundation, and the catalog term of the career equation is real — but explains what an audience is in asset terms, why it compounds while gear depreciates, and what specifically happens to a great record released to zero infrastructure. Then concede the kernel of truth: name the one funnel transition that genuinely cannot be fixed by marketing.

A2. Kelly, honestly. ★ (10 min) Summarize Kevin Kelly's "1,000 True Fans" argument in two sentences, being careful to attribute the arithmetic to him rather than to physics. Then answer: why does the chapter insist the durable part is the shape of the insight rather than the numbers? Name two ways your situation could differ from his model (price points, costs, genre economics, anything real) without breaking the shape.

A3. Flywheel vs. treadmill. (10 min) Define both terms in one sentence each. Then classify each of the following as flywheel or treadmill behavior, with one clause of justification: (a) screen-recording your sound-design session because you were doing it anyway; (b) spending Saturday filming a skit about producer stereotypes; (c) posting the v0.3-versus-final A/B of your single; (d) staging a fake "first listen reaction" to your own song; (e) photographing the split-sheet signing. One of these is genuinely debatable — say which, and give the honest case for each side.

A4. The announcement fallacy. ★ (10 min) Explain why "MY EP. 28 DAYS. 🔥" reliably fails, in terms of what a stranger's attention needs in the first seconds. Then rewrite the same announcement as an artifact-led post: describe (don't design — describe) what's on screen for the first three seconds, what the caption says, and where the date goes. State the principle in one line.

A5. Owned vs. rented, with teeth. (15 min) A friend with a large following on one platform and no email list says, "Why would I collect emails like it's 2009? Everyone I need sees my posts." Write the rebuttal in three parts: (1) the landlord mechanics — three distinct ways the rented relationship can degrade without the friend doing anything wrong; (2) the honest concession — the one thing the platform does that the email list never will; (3) the doctrine that resolves the tradeoff, plus the bridge mechanism that implements it.

A6. Funnel diagnosis. ★ (15 min) For each symptom, name the failing funnel transition and prescribe the chapter's fix: (a) clips routinely get strong engagement from strangers, but the profile gains almost no followers; (b) a healthy follower count, but release day produced barely any streams; (c) solid streams on every release, but saves-per-listener is consistently weak; (d) plenty of saves and repeat listeners, but nobody has ever signed up, bought, or shown up. For (c), give both the marketing explanation and the harder non-marketing one, and say which chapter handles the second.

A7. The scam detector. (10 min) You receive three DMs: (1) "We guarantee placement on playlists totaling 500K followers — $60"; (2) a curator whose playlist you actually follow says they'd consider your track if you send a private link; (3) a service offers to pitch your track to a list of independent curators for a fee, no outcomes promised. Rank them by legitimacy, explain the economic tell that separates the first from the third, and describe what bought streams do to the one playlist species you can't pitch directly.

Part B: 🎧 Listening Lab

Ears first, as always — but this lab listens to careers as well as mixes. You'll be using the Chapter 4 deconstruction discipline on content: same method, new material. Keep the listening journal open; these entries become direct inputs to your Desk Lab calendar.

B1. The reference-artist teardown. ★ (45 min) Pick three reference artists — one or two steps ahead of you, close enough in sound that their audience could plausibly be yours (T4: not your heroes; your compass). For each, document: (1) the one-sentence file — complete "this is ___ for ___" from their profile alone, and note how long it took you; (2) their last nine posts, classified — announcement / process artifact / story / teaching / ask / other — with a tally; (3) which two posts are visibly carrying the load, and what their first three seconds contain; (4) where they send people (pre-save? email? nothing?) — walk their funnel as a stranger and note where it leaks. Close with the gap list: three things their staircase has that yours doesn't. That list is your to-do list, exactly as it was for mixes.

B2. Production artifacts in the wild. (30 min) Find five pieces of artist content built from production artifacts — a before/after, a stem or layer solo, a session screen capture, a sound-design origin story, a craft confession. For each, log: which artifact type from the chapter's taxonomy it is, what production stage it came from (use this book's chapter vocabulary — comping, the mute test, the color pass), and what it made you feel about the finished song. Then the synthesis question: which artifact types appear most in your genre, and which appear rarely — and is the rare one an opportunity or a genre mismatch?

B3. The hook autopsy. ★ (25 min) Scroll any feed for ten minutes as a civilian, then audit yourself: log the first five things that stopped you for more than a few seconds. For each, write exactly what occupied the first moment — motion, a claim, a question, a sound, a face, text — and what the implied promise was. Then the producer's translation: for each of the five, name the analogous move in arrangement terms (the cold open, the transient, the dropped-out bar before the chorus). You're building the same instinct Chapter 16 built, pointed at a different timeline.

B4. The snippet decision. (25 min) Take three songs you know deeply — one of yours if possible, two from your reference tracks. For each, choose the fifteen seconds you'd post to stop a stranger, and defend the choice in journal language: what enters, what's the motion, where's the payoff relative to second one? Now the discipline check: for your own song, compare the section you want to show (the one that took longest to mix, the clever bit) against the section a stranger would save. If they differ, write one sentence about why — that sentence is the whole lesson.

B5. Walk your own funnel. (20 min) Trace, from memory, how you became a superfan of one artist — the actual sequence: what stopped you, what you checked, when you followed, what made you go deep, what you eventually gave back (money, attendance, evangelism). Timestamp it roughly (days? months? years?). Then annotate each step with the funnel tier it represents and what the artist had in place that caught you. Finish with the uncomfortable audit: at which of those steps would a stranger arriving at your presence tonight fall through? Be specific.

Part C: 🎛️ Desk Lab

The deliverables lab. Everything here feeds the Project Checkpoint; budget two sittings and treat the outputs as session files — versioned, named properly, kept.

C1. The artifact mine. ★ (60–90 min) One full pass through your project folder(s) for the track or EP you're releasing, spreadsheet open, four columns: artifact, chapter/stage it came from, content genre it maps to (use the chapter's taxonomy table), and the one-line story it tells. Log everything — version bounces, voice memos, screen recordings, comp sheets, rejected mute-test parts, the patch you built, reference A/Bs. Target: at least fifteen candidates. Then cut to the ten strongest (T2 — the cut list is part of the deliverable; note why each casualty lost). If you found fewer than ten, that's a capture-habit diagnosis, not a failure: write the three capture habits you'll install for the next project (version saves, screen-record toggle, voice memos), and mine an older project to fill the gap.

C2. The four-week calendar. ★ (45 min) Drop your ten artifacts into the chapter's grid: three posts a week across four weeks, each week doing its narrative job (announce-with-artifact / world / story / ask), each post tagged with its one funnel job (discover, deepen, or convert) and ending with either a forward promise or a bridge. Add the three email beats (announce, story, release-eve). Mark the two hard deadlines from Chapter 35's spine: distributor upload (done or dated) and editorial pitch submission (Week −4). Sanity-check the whole thing against the burnout law: if this calendar wouldn't survive a bad week at your actual job, thin it now, on purpose, and write the one-line justification.

C3. The playlist pitch. ★ (30 min) Draft your editorial pitch: genre and subgenre, mood, instrumentation, your one-liner, and two sentences of story — under 120 words total, no superlatives, nothing a curator couldn't file. Read it against the chapter's example. Then write one personal note (three sentences max) to a real independent curator whose list you genuinely listen to: name the fit, link the EPK, ask nothing else. If you can't name a real curator, that's tonight's other assignment: find three lists where your track honestly belongs, by listening, not by follower count.

C4. The EPK build. (45 min) Assemble the folder: short bio (two sentences, built around your one-liner), medium bio (one paragraph, the story week's material compressed), two or three photos you'd defend, cover art, direct links, your two strongest tracks, notable bullets, contact. File-name everything like a Chapter 19 graduate. Test it on one person who doesn't know your music: can they say back, in one sentence, what you are and who you're for? If not, the one-liner — not the photos — is what needs work.

C5. Design the superfan tier. (30 min) Answer the inner-room questions concretely: What do your most devoted listeners get that nobody else does — early listens, stems, credits, replies, input on choices? Where does that tier live (the owned channel)? How does a listener get invited — what raised-hand behaviors (repeat comments, message replies, signup) will you actually watch for and respond to? Write the welcome message a new superfan-tier member receives. Keep the whole design something one person can operate in under an hour a week, or redesign it until it is.

C6. Stand up the owned core. ★ (45 min) Create the email channel (any reputable list tool — the principle, not the brand, is the assignment) and build the lead magnet from your session: a stem pack, sample kit, project-file breakdown, or extended version. Clear the rights first — if any stem contains a collaborator's performance, get the yes in writing, Chapter 36 style, before it ships. Wire the bridge: the signup link goes wherever a rented touchpoint can carry it (profile, pinned post, video captions). Send the first email to however many subscribers exist — even one — announcing the campaign. Treat the send like a release: proofread, test the links, then ship.

C7. The release-day checklist + analytics baseline. (30 min) Write your release-day checklist: every platform link verified, artist profiles claimed, pinned posts swapped, 12:01 a.m. email queued, thank-you list drafted, Week +1 breakdown content scheduled before the day arrives. Then set the analytics ritual: choose your three signal metrics from the chapter's table, log today's honest baseline values (small numbers are the correct numbers — write them anyway), and put a recurring fifteen-minute weekly review on your actual calendar. The baseline entry is the deliverable: trends need a starting point.

Part D: Synthesis

D1. The platform-death stress test. ★ (20 min) Write the one-page scenario: tomorrow morning, the platform where you have your largest following announces it's shutting down in 30 days (it has happened; it will happen again). Inventory what you'd actually lose, what survives (be specific: list, catalog, EPK, relationships), and the 30-day migration plan. Then the real deliverable: name the one change you'd make to your current setup after writing this — and make it this week.

D2. The ethics line. (20 min) The chapter teaches hook economics; clickbait also "earns the first seconds." Write a half page locating the line between the two, using the document-don't-fabricate rule as your anchor. Test your line against three cases: (a) titling a clip "this mix mistake almost ruined my single" when it's true; (b) the same title when it's exaggerated; (c) a staged "accidental" leak of your own song. Does your line survive all three? Would your reference artists' content pass it?

D3. Define success before launch. (25 min) Before your campaign runs, write the post-mortem criteria you'll grade it against at Week +4 — three quantitative signals (from the signal column only — and expressed as direction and presence, not invented targets: "saves-per-listener exists and isn't collapsing," "the list grew at all") and two qualitative ones (a stranger's comment that proves the one-liner landed; a remix or cover existing). Seal it — no editing after release. This is the discipline that makes the Week +4 review a diagnosis instead of a mood.

D4. The two-year cadence memo. (25 min) Using career = catalog × audience × time, write yourself a one-page memo: your sustainable release rhythm (honestly — count your actual free hours), your sustainable posting cadence, the seasons you'll allow (production seasons, quiet seasons, and what the owned channel does during them), and the three signals you'll check monthly to confirm no term is sitting at zero. End the memo with the sentence you'll reread when someone else's spike makes your dashboard feel small.

Part M: Mixed Practice

Interleaving keeps the earlier chapters honest — and most of these are exactly the cross-domain decisions a release month forces.

M1. (Chapters 22 & 30) A listener comments that your single sounds "muddy on my phone." Before touching the campaign, run the diagnosis: name the frequency zone most likely implicated, the 60-second check you'd run on the master, and the decision you face if the comment is right — including what Chapter 31 said about whether mastering can fix it and what that means for a track that's already live.

M2. (Chapters 19 & 36) Your remix-bait post works: a producer you don't know wants the vocal stems. List exactly what you send (file specs, documentation — the Chapter 19 protocol) and the two rights questions that must be answered in writing before anything ships, given that the vocal is a collaborator's performance and the composition has three names on the split sheet.

M3. (Chapter 33) For the campaign's snippet, your collaborator argues for printing a special extra-loud bounce "so it hits harder in the feed." Explain what streaming normalization does and doesn't imply here: why the loudness-war logic died for the catalog release, why a feed snippet is a slightly different playback context, and the chapter-consistent way to make the snippet hit (hint: it's an arrangement decision from Part B, not a limiter decision).

M4. (Chapters 13 & 16) You're choosing the fifteen-second snippet for the drum-rebuild post. Using Chapter 16's energy-curve vocabulary and Chapter 13's groove anatomy, explain why "the two bars right before and after the beat switches from flat grid to pocketed groove" outperforms "the busiest fill in the song" — and what that implies about before/afters in general.

M5. (Chapters 4 & 21) You're A/B-ing two edits of the same promo clip and the version with louder audio "feels better." Name the bias, the Chapter 4 reason it operates, and the matched-loudness discipline you'd apply before trusting the comparison — then state the general law this is one more instance of.

M6. (Chapters 14 & 35) Your patch-origin clip is outperforming everything else, and a viewer asks for the preset. Decide: free lead magnet, paid product, or tutorial content — and justify the choice using the funnel (which transition does each option serve?) and Chapter 35's metadata lesson about why your artist name needs to be consistent everywhere the preset travels.