12 Months of Reasons to Call

You are a customer-retention strategist working with a residential solar
installer who wants a year of contact with past customers that does not ask them
for anything.

### MY SITUATION
Company: [name]
Region and climate: [e.g. Phoenix AZ, hot and dusty / coastal NC, salt and storms]
Customer base: [rough size, install year range]
What I can produce cheaply: [production data? photos? monitoring access?]

### BUILD ME A 12-MONTH CALENDAR

One touch per month. Each must be genuinely useful on its own — if the only
value is that it reminds them I exist, it does not belong on the calendar.

Weight it to my actual climate. Storm prep matters where there are storms; dust
season matters in the desert; snow and ice matter where they fall.

Include, timed sensibly:
  - an annual production report (their system's output, plainly explained)
  - a seasonal check they can do themselves in five minutes
  - tax-season documentation they may need
  - at least one piece of local rate or policy news that affects them
  - at least one that is purely goodwill with no commercial angle at all

### FOR EACH MONTH GIVE ME

theme | why it matters this month | what I send | what it costs me to produce |
what it sets up later

### RULES

- No filler. If a month has nothing worth saying, tell me to skip it. Eleven
  good touches beat twelve where one is padding.
- Nothing may contain an offer. Not a soft one either.
- Do not reference the federal 25D residential credit as available; it expired
  for expenditures after 2025-12-31. Tax-season content should be about
  documentation, not incentives.

### OUTPUT

CSV: month | theme | rationale | asset | production_cost | sets_up

Write the template for an annual solar production report I send to every past
customer.

This is the most valuable thing I send all year. It must be readable in ninety
seconds by someone who does not think about kilowatt-hours.

### INCLUDE
  - what their system produced, in plain language and in money
  - how that compares to what was projected at sale
  - how it compares to last year, with degradation explained honestly as normal
  - what, if anything, they should do
  - what I am NOT charging them for

### RULES
- Every number is a merge field I populate from monitoring data. Invent nothing.
- If production is DOWN, the template must handle that honestly and without
  alarm — with a clear path to a service check. Do not write a template that
  only works when the news is good.
- No offer anywhere in the document. The report earns the next conversation by
  being useful, not by selling.
- Plain language. A kilowatt-hour means nothing to them; dollars do.

### OUTPUT
The template with merge fields marked, plus a variant for the down-production
case and a short note on which monitoring platforms can export these fields.