ANNOUNCE

Make the thing understandable and relevant.

Asset: [thing]. Audience: [audience]. Action: [action]. Write a Halloween announcement that answers what it is, who it is for, why it matters now and what to do next. Use the seasonal angle only where it adds context.

Create two announcement routes for [thing]: one led by the project itself and one led by the Halloween use case. Explain which audience each route fits better.

Track: [description]. Identify the musical moment that best earns the announcement. Write a post that leads with that evidence instead of adjectives.

Event: [details]. Build an announcement that makes date, time, location, experience, audience and action scannable in under 10 seconds.

Offer: [details]. Explain what changes for Halloween and what does not. Remove fake urgency and vague “spooky savings” language.

TEASE

Create curiosity without hiding the value.

Create a teaser for [thing] that withholds one interesting detail but still makes the value obvious. State exactly what is revealed now and what is saved for later.

Design a teaser concept where one object, crop or texture signals the campaign identity without showing the full asset. Include safe text area and CTA.

Choose a 5-10 second audio moment from [track description]. Explain what it proves and build a teaser around hearing that moment.

Tease the experience of [event] using one sensory or participation detail. Do not repeat the full event announcement.

Show one use, outcome or close-up detail from [product] without listing every feature. End with the next reveal date.

DEMONSTRATE

Show evidence, experience or use.

Product/service/content: [thing]. Create a Halloween demonstration showing a real use case from setup to result. Keep copy secondary to the evidence.

Create a before-and-after demonstration for [thing]. Define what changed and make sure the Halloween element is part of the use case, not decoration.

Turn this process into a short behind-the-scenes asset: [steps]. Choose the one step that best proves human direction or quality.

For [track], propose a visualizer or performance clip that demonstrates the strongest musical feature. Explain what viewers should notice.

Show what attending [event] will actually feel like using 3 concrete details. Avoid promises you cannot verify.

COUNTDOWN

Add new reasons to care as time moves.

Build a 5-day countdown for [thing]. Each day must reveal new information: context, feature, proof, story, final action. No generic day-count posts.

For [event], create 3 countdown posts that progressively reduce attendance uncertainty: experience, practical details, final reminder.

For [song], use three different evidentiary moments: artwork/identity, audio hook, release action.

For [offer], create a countdown where each post explains a different use case or customer question rather than repeating urgency.

For [stream], use participation, topic and live-only value as the three countdown reasons.

LAUNCH

Turn preparation into one clear action.

Launch [thing] today. Lead with the strongest concrete value, show the seasonal context second, then give one action. No recap of the entire campaign.

Song: [details]. Write a release-day post that gives the track a job beyond “out now”: mood, setting, listener use or story.

Event: [details]. Write a day-of post prioritizing attendance information and one reason the experience is worth leaving home for.

Product: [details]. Lead with the buyer job it solves this Halloween. Mention contents only after the use case is clear.

Stream: [details]. Write a going-live post that makes the live-only participation mechanic obvious in the first two lines.

REMIND

Add information instead of repeating yourself.

Original announcement: [paste]. Write a reminder that adds one new proof point, use case or detail. Do not paraphrase the launch post.

Create a song reminder using a different musical moment or listener use case than the launch asset.

Write a reminder that answers the single biggest attendance question still unresolved: [question].

Write a reminder around who the offer is best for and one real outcome, not only the deadline.

Remind the audience about [video/stream/post] by surfacing one overlooked idea or reaction from the content.

FINAL CALL

Use real constraints and remove clutter.

Write a final-call post for [thing]. Use only real time, capacity or schedule constraints. State what happens if the audience does nothing without inventing loss.

Event details: [details]. Make arrival/action information obvious. Remove nonessential storytelling.

Offer: [details]. Restate fit, deadline and action in that order. No exaggerated urgency.

Create a one-hour-to-live post centered on the live-only participation benefit.

If there is no real deadline for the song, do not fake one. Convert this into a “Halloween weekend listen/use” post instead.

FOLLOW-UP

Capture proof and point somewhere useful.

Summarize what happened in this campaign using results: [data]. Separate facts from interpretation and identify one next action.

Write a thank-you post for [event/launch] that includes one meaningful result and points to the next relevant piece of work.

Use these comments/listener reactions: [paste]. Build a follow-up around a recurring response without overstating consensus.

Show how buyers/customers used [product/service] during Halloween. Turn that into proof for the evergreen version.

Turn a Halloween event result into a bridge toward the next event, mailing list or regular offer.

REPAIR

Diagnose the layer before rewriting everything.

Audit [campaign] for clichés, vague benefits, generic AI phrasing and borrowed seasonal personality. Replace each with a project-specific detail.

Results show low reach/engagement: [data]. Review hook, first frame, relevance and audience match. Pick one variable to change next.

Results show attention but weak clicks/sales/attendance: [data]. Diagnose offer clarity, proof, CTA and destination. Change one variable.

Compare these campaign assets: [paste]. Identify conflicting promises, tones, visuals or CTAs. Define one campaign rule to restore consistency.

This campaign is too large: [plan]. Reduce it to explain → prove → ask. List what to defer.

REUSE

Turn seasonal work into reusable capability.

From this Halloween campaign [paste/results], extract the reusable structure without copying Halloween imagery or wording.

Convert the strongest Halloween asset into an evergreen version. State what seasonal element is removed and what core value remains.

Adapt the campaign decision structure to [Christmas/Valentine/etc.] while changing the audience context, not merely the decorations.

From these results [data], write one reusable rule in the form: When [condition], use [decision], because [evidence].

Create a short campaign record: objective, audience, assets, result, strongest signal, failed assumption, reusable decision, next test.

Quality-control checklist

Vault completion record

← Free Halloween Promotion guide · Campaign Feedback Loop →