The festival ends Sunday night. By Tuesday morning you’re back home, exhausted, with a head full of people you talked to and almost no memory of who they actually were. By the following weekend, the festival feels like something that happened a long time ago. By the time you remember to follow up with someone, the moment has passed and you’re not sure they’d remember you anyway.
This is the festival aftermath problem, and almost every working DJ I know has experienced some version of it. You meet thirty people in a weekend. You get six numbers, eleven Instagram follows, four “let’s link up” exchanges, and a stack of mental notes you intended to convert into real follow-ups. Three months later, you’ve done none of it, and the relationships that could have come out of that festival have all gone cold.
This is what I learned about how to actually stay in touch — not in theory, but in practice, with a system that survives a tour schedule.
What goes wrong
The default fail mode after a festival is straightforward: you intend to follow up, you don’t, life moves on, and the contacts decay.
The reasons are predictable.
You’re tired. Festivals are physically and socially exhausting. The first 48 hours after returning home, you’re recovering, not networking.
The contacts blur. By Tuesday you’ve genuinely forgotten which conversation went with which face. You remember “the German promoter” but not their name or what they actually said.
The medium varies. Some you DM’d on Instagram. Some you exchanged numbers with. Some you only know by first name and a description of where they were from. Without a single capture system, the contacts scatter.
The timing window closes. The right moment to follow up is roughly within a week of the festival. After that, the original conversation feels distant, the energy fades, and the message gets harder to write.
The pile of intentions becomes overwhelming. Thirty contacts to follow up with feels like a project. Projects don’t get done in the post-festival haze. They get postponed. Postponed projects in this domain die.
The combined result is that festivals — which are objectively the highest-leverage networking moments in DJ careers — produce far less follow-through than they should.
The 48-hour rule
After a few cycles of losing festival contacts to inertia, I imposed a personal rule: every meaningful contact gets logged within 48 hours of the festival ending. Not followed up with. Logged.
The distinction matters. Logging means I capture the contact in a single place — name, where I met them, what we talked about, what (if anything) was promised by either side, and how to find them again. The follow-up message itself can come later. But if the contact isn’t logged within 48 hours, it’s effectively dead, because by Day 4 I won’t remember enough to write a real message.
The 48-hour rule survives jet lag, sleep debt, and re-entry chaos because it’s small. Logging takes 30 seconds per contact. Even after a four-day festival, an hour on the train home gets it done.
The actual capture is whatever fits. I use Notion, but a phone note works, a spreadsheet works, a voice memo works — as long as it’s one place. Multiple places is the same as no place.
The triage system
Once you’ve logged 30 contacts, you have to triage. Not all 30 are equally worth following up with.
I sort into three tiers:
Tier A — the ones with concrete openings. Anyone who said something specific. “Send me your latest mix.” “We’re booking for spring, message me.” “I’d love to put your track on the next compilation.” These are not casual remarks; they’re invitations. Tier A gets followed up first, usually within five to seven days.
Tier B — the ones with warm interest. People you had a real conversation with where the chemistry was good but no specific opening was named. Fellow DJs you’d want to do shows with. Promoters who said “let’s stay in touch” without specifying anything. Tier B gets a softer follow-up: an Instagram follow with a comment, a quick DM that doesn’t ask for anything specific.
Tier C — the ones where the conversation was pleasant but thin. Brief introductions, a few minutes at the bar, no real exchange of substance. These don’t need a follow-up. The Instagram follow itself is the closure of the interaction.
For thirty contacts after a festival, the typical breakdown is something like 8 in Tier A, 12 in Tier B, 10 in Tier C. The Tier A messages are the ones that pay off; the Tier B touches keep the door open for future opportunities; Tier C is left to grow naturally if the connection ever has reason to reactivate.
The follow-up message that works
The festival-aftermath follow-up has a different texture than a cold pitch. The relationship exists. The shared context exists. You’re not selling — you’re picking up a thread.
A working structure for Tier A:
Hey [name] — really enjoyed our chat at [festival] about [specific topic]. As promised, here’s [the thing they asked for]. Take your time with it. Hope the rest of your weekend was good.
Four sentences. References the festival. Delivers on whatever was implicitly promised. Releases pressure on response timing.
For Tier B, even lighter:
Hey [name] — good to meet you at [festival]. Just wanted to say the [specific thing they did or said] stuck with me. Following on Instagram so I can keep an eye on what you’re up to.
Three sentences. Acknowledges the real interaction. Compliments authentically. Sets the relationship to “warm acquaintance” without pretending to be more.
The mistake to avoid in both cases is generic warmth. “Great meeting you, hope to stay in touch” is the universal signal of low-effort post-festival messaging. Specific references to what you actually talked about — even brief, even small — separate your message from the dozen others they’re getting.
The CRM input
After the 48-hour log and the follow-up wave, the contacts go into my main CRM with appropriate status fields. Tier A contacts go in as “warm — recent festival conversation” with a next-action date in 14 days. Tier B contacts go in as “warm — light touch” with a 90-day check-in reminder. Tier C contacts get logged as cold contacts in case they ever reactivate.
This is the step most artists skip. Without it, the festival is a one-time event whose contacts you’ll either follow up with immediately or lose forever. With it, the festival becomes ongoing pipeline — Tier B contacts that produce something six months later, Tier C contacts that get reactivated when context shifts.
The effort is, again, small. Twenty minutes of CRM data entry produces years of latent leverage. The tools that make this lighter — like Backline for the Instagram-DM portion of the contact graph — are useful, but the real discipline is capturing the contacts at all. The format is secondary.
What this looks like over time
I now treat festivals less as performance moments and more as networking sprints with a performance attached. The set itself matters, obviously. But what matters at least as much is the operational discipline of the 48 hours afterward — capturing, triaging, and re-engaging the contacts before they fade.
Over the last two years of doing this consistently, I’d estimate something like 30% of my bookings now have origins in festivals where I performed and met someone backstage, in the artist hospitality area, or after the closing party. That number was much lower before I built the system, mostly because the contacts I was meeting were never converting into real relationships.
The festival isn’t where the network gets built. The 48 hours after is where it gets built. Or lost.
The bottom line
Thirty contacts from a festival is a real opportunity. The default fail mode loses almost all of them to inertia. The fix is two routines: capture within 48 hours, follow up within seven days, in tiers that match the strength of each interaction.
It’s an hour of work, total, for a weekend that probably cost a few thousand euros to attend. The return on that hour is one of the best you can find in independent music.
The festival is the input. The follow-through is the work.
Backline handles the Instagram-DM half of festival follow-up: it surfaces every new conversation from the last weekend so you can act on them while the context is fresh. Privacy-first parsing, built specifically for this kind of contact-capture loop.