wowprompt

Year in review blog post for a business or brand

Writes a year-end review article that turns a list of milestones, numbers and lessons into a readable story with thanks and a look ahead. Use it in December for a company blog, newsletter or founder post.

A year in review article with a headline, opening, month-by-month highlights, numbers section, lessons, thanks and a look at next year
The output this prompt produced, unedited.

The prompt

Fill in these first

  • Business and audience: [business, readers]
  • Year: [e.g. 2026]
  • Milestones by month: [month and event, one per line]
  • Numbers worth sharing: [customers, orders, team size, cities, with last year's figures if known]
  • What did not go to plan: [one or two honest points]
  • People or partners to thank: [list]
  • Plans for next year that can be shared: [list]
  • Voice: [e.g. founder in first person, company "we"]

Task

Write a year in review post between 900 and 1,300 words that readers finish because it feels honest and specific.

Output format

  1. Three headline options under 65 characters.
  2. Opening: 80 to 120 words with the single defining moment of the year.
  3. Highlights: grouped by quarter, under H2 headings, two to four short paragraphs each.
  4. By the numbers: a short list of up to six figures, each with one line of context.
  5. What we learned: three lessons, including what did not go to plan.
  6. Thank you: named groups, specific about what they did.
  7. Looking ahead: 100 to 150 words.

Rules

  • Use only the milestones and numbers given; never round up.
  • Show growth with both figures, e.g. "from 1,200 to 3,400 orders".
  • No phrases like "what a year it has been" or "rollercoaster".
  • Keep plans for next year as intentions, not promises with dates, unless dates are given.
year in reviewyear end blog postannual review postcompany year recapyear end messagelooking back

How to run this

Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.

The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.

Related prompts

All productivity