The announcement is not the campaign. It is the harvest. Whatever a festival can sell in launch week was largely decided in the months when nothing was happening, by whether the audience from last time was kept warm or left to cool into strangers.
Key takeaways
- The announcement collects attention. It does not create it.
- Most festivals gather almost all their contacts in a few weeks of sales and a few days on site, then say nothing for ten months.
- The warmest segment you have is last year's attendees who have not bought this year.
The year everyone actually runs
Here is the shape of almost every festival calendar we have seen.
Chart data
| 1 | Announcement (Everything at once. Line-up, tickets, posts, ads) |
|---|---|
| 2 | Sale window (Six weeks of intensity, then it goes quiet) |
| 3 | The event (A few days. The best content of the year, mostly unused later) |
| 4 | After (One thank you post. Then nothing) |
| 5 | Ten silent months (The audience forgets, and next year starts cold) |
Step five is not a gap in the schedule. It is most of the schedule: three hundred days in which a list you already own, of people who already said yes and already came, hears nothing from you and slowly stops being an audience.
Why silence is expensive
An audience that hears from you once a year is not a list, it is an archive. Three things wear down in those ten months, and only the first is obvious.
Deliverability. Gmail's sender guidelines ask bulk senders to send at a steady rate and to avoid bursts, and warn that a sudden jump in volume can get you rate limited. Ten months of silence followed by a heavy launch week is that jump, and it lands on the one send that matters most.
Reachability. People change email addresses, phone numbers and cities. The longer the gap, the more of the list has quietly gone dead, and you find out on announcement day.
Permission, in practice. Legally the consent may still stand. Emotionally it has lapsed. Someone who has not heard from you since last August reads your announcement as an interruption, not as news they were waiting for.
Four sends between two editions
Not more marketing. Less, spread differently. The usual objection is that there is nothing to say, which is true of the festival and false of everything around it.
| When | What to send | Why it works | The trap |
|---|---|---|---|
| Just after | The recap, one honest thing that went wrong, and what you changed | People still care about the weekend, and honesty is rare | Turning it into a humblebrag |
| Autumn | Who you are listening to right now | It makes you a curator, which is why people follow a festival | Listing only acts you have already booked |
| Winter | How a slot actually gets booked, or what is changing on site | Behind the scenes is interesting because it is not a sale | Talking about your team rather than the craft |
| Six weeks before the announcement | The date the line-up lands | It turns the announcement into an appointment | Missing the date you gave |
None of these is a campaign. Each is one message, written in an afternoon, with no offer in it, and the absence of an offer is what makes the eventual one land.
The last row is the one people skip, and it is worth the most. An announcement people expect does better than one they stumble on, because your own audience arrives first, buys the cheapest tier and creates the social proof the rest of the market reacts to.
Put the four dates in the same calendar as the production milestones. A send that lives in someone's head does not happen in the month the site plan is due.
The two segments that only exist if you kept the record
Attended last year, has not bought this year. The warmest message a festival can send. It requires attendance to have been recorded per person rather than as a headcount.
Attended two or more editions. Your actual core. These people deserve a different message, an earlier window and a better price, and most festivals cannot produce the list because each year's data lives in a different export.
Neither segment can be rebuilt after the fact. They exist only if the source and the attendance were written onto the person at the time, which is the argument of what an event CRM should do.
The pre-announcement list
This is the mechanic that pays for the whole quiet season, and it is almost never built on purpose.
- Publish the announcement date before the line-up. Six to eight weeks ahead. Just the date the news will arrive.
- Put a single sign-up next to it. One field, one sentence: we will tell you the morning it goes live.
- Promote it twice. Once when you set the date, once the week before. More than that and you are advertising an advert.
- Send to that list first on the day, thirty to sixty minutes before anything public. A small privilege that costs nothing and is noticed.
- Note its size the day before, next to last year's figure.
It works because it turns something scarce, your audience's attention in a month when you are selling nothing, into a stock you can spend on the one day it counts.
How to measure a month where nothing happens
Not by revenue, because there is none. Three numbers, checked monthly:
Reachable share. The percentage of last edition's attendees who still have a working channel. It should fall slowly. If it drops sharply, you waited too long.
Opens on the quiet sends. If they keep falling, the content has become filler. Change it or stop sending it.
Pre-announcement list size. Everyone on it asked to be told. On the day before the announcement, it is the closest thing you have to a forecast for launch week.
Where HIIPE fits
This is the job HIIPE is built for: a fanbase that keeps each person across editions with their source and history, and campaigns by email, SMS, RCS or social DMs from the same screen, so a monthly send to one segment takes ten minutes rather than a project. How the pieces connect shows the whole of it.
The whole argument
An announcement harvests attention. It does not create it. What a festival sells in launch week was decided in the ten months when nothing was on sale, by four modest sends and one list of people who asked to be told. It is cheap, it is unglamorous, and it is rare only because nobody is judged on a month in which nothing happened.
Read next : What an event CRM should do between two events · Fill your next event from the last one
