DAS 301 · Module 1

The Tour as One Organism

Facts verified: July 2026Last updated: July 2026Curriculum v2026.1

What you'll be able to do

  • Treat a tour as one campaign organism instead of N disconnected shows
  • Map the tour lifecycle over machinery you already own from the prerequisite tracks
  • Know why marketing data now sits at the routing table, and act like it

The short version: A tour run as twelve separate show campaigns rebuilds everything twelve times and learns nothing once. A tour run as ONE organism shares a creative backbone, feeds one set of warm pools, cascades social proof forward market by market, and breathes budget across cities weekly. This module is the frame; the rest of the track is the operating manual. Nearly every part is machinery you already own - DAS 201's event lifecycle and geo doctrine, DAS 202's network and two-party coordination - assembled at highway speed.

One campaign, many rooms

The defining mental shift: the market is the ad set; the tour is the campaign. Everything DAS 201 taught about one show's lifecycle still happens per market - announce, surge, sustain, final 72, harvest - but the tour adds a dimension those modules couldn't: the markets talk to each other. City three's sellout is city nine's social proof. The Denver recap shoots Chicago's ads. The whole run's warm pool compounds nightly.

First rodeo

If this is your first rodeo (at tour scale - you've done the prereqs): the vocabulary here is routing (the sequence of dates), the advance (per-show logistics thread), holds and offers (the booking layer). This track touches booking only where ad data earns a seat at that table - which, by Module 6, it does.

The organism's four shared systems

  • One creative backbone. The tour's announce asset, trailer, and admat system produce per-market variants from one spine - Module 7's factory. Forty date-lines, not forty design jobs.
  • One warm pool, market-tagged. Every market's engagers and buyers flow into tour-scoped audiences tagged by city (DAS 201 M10's ritual × N). The pool is the tour's compounding asset and next year's launch pad.
  • One proof stream. The roll-call doctrine (DAS 202 M8) at full scale: shared announce post IDs mean every market's "already got mine" stacks onto what the next market sees. The tour promotes itself forward.
  • One budget, breathing. Money is never allocated per-market and forgotten; it flows weekly to sellthrough gaps (Module 3's war room). A tour budget is a portfolio, rebalanced.
Go deeper: the tour lifecycle mapped over DAS 201's

The translation table: tour announce = the announce phase × every market at once (Module 4's wave mechanics) · rolling on-sales = N surge mornings on a schedule · the long middle = per-market sustain with the tour's shared creative refreshing it · each date's final 72 = DAS 201 M9 verbatim, arriving on a conveyor belt one city at a time · each night's harvest = the ritual, market-tagged, feeding the NEXT morning's ads in the next city. The conveyor-belt quality is the real difference: on tour, every phase of the lifecycle is happening somewhere simultaneously. The war room exists because no human holds that in their head without a sheet.

Why marketing data sits at the routing table now

The track's quiet thesis, stated early: routing has always run on agent instinct, hard-ticket history, and relationship gravity. The tour that runs this track's machinery adds evidence - pool depth per market, cost-per-ticket curves, alert-list density by city (Module 5) - and by the routing debrief (Module 6), the marketing operation is producing the single best dataset anyone at the table has about where demand actually lives. That's not marketing serving booking; that's marketing informing it. Careers get built in that gap.

From the field

A 14-date run, first pass: every market its own fresh campaign, built by whoever had time that week. No shared post IDs, no tagged harvest, budget set once in month one and never moved. Result: three markets oversold while two died quietly with money still scheduled against the sellouts. Second run, same act, this track's frame: one backbone, shared announce IDs, the weekly war room. Same total budget; the gap markets got found in week two instead of week nine, the sellout markets threw off proof and budget instead of absorbing both, and the tour-tagged pool that came home was the third run's opening asset. Nothing about the music changed. The organism did.

Common mistakes

  • N separate campaigns built N times (the twelve-rebuild tour)
  • Budget allocated once at announce and never rebalanced (the featured sin, tour edition)
  • Fresh announce posts per market splitting the proof stream
  • Harvest skipped mid-tour "until things calm down" (they don't; the ritual is 45 minutes and the pool is the point)
  • Treating routing as upstream of marketing forever (by the debrief, the data flows both ways)

Take-home

The Tour Organism One-Pager - the four shared systems as a setup checklist, the lifecycle translation table, and the who-owns-what worksheet for tours with mixed team/promoter/label operators.

Sources & dates

DAS 201/202 cross-references as cited · the organism 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.

  • DAS 201 Modules 1, 5, 10 + DAS 202 Module 8 - the four modules this one assembles