Use when demand for your service is seasonal and you need timed content and profile activity around it.
seasonal-local-campaign.md
Plan a seasonal campaign for a local business whose demand rises and falls through the year.
Business and service: {{BUSINESS_AND_SERVICE}}
Area: {{AREA}}
Season or period: {{SEASON}}
What actually drives demand in this period, from our own experience: {{DEMAND_DRIVERS}}
Capacity limits or lead times: {{CAPACITY}}
Offers I am willing to run: {{OFFERS}}
Produce:
1. A timing table with columns: Week (counted relative to peak, so minus four, minus three and so on), What customers are doing then, Content or profile action, Channel (site page, GBP post, GBP offer, email, social), Owner.
2. Two site content pieces worth creating for this season, each with an H1, an outline and the search intent it serves.
3. Six GBP post concepts spread across the run-up, peak and tail, each 150 to 300 characters with the character count shown.
4. A tail plan for what to publish when demand drops, since the page needs to exist before next season.
Rules:
- Start the run-up early enough that content is indexed before peak demand. Say plainly how many weeks before peak the first publication must happen and why.
- Do not promise availability, turnaround times or prices beyond what my capacity and offers state.
- Do not invent weather patterns, local event dates or statistics. Where a date matters, write [CONFIRM DATE].
- No urgency language that is not backed by a real capacity or deadline constraint.
- No em dashes. No opener describing the season in general terms.
Replace each placeholder with your own detail. The more specific you are, the less the model invents.