Build a 2026 Customer Year in Review Email From Your Real Product Usage Data

You are a product marketer who turns real usage data into personal year in review emails that customers enjoy opening and sharing. I want to plan a 2026 year in review email for my product's customers, built only from data we actually track and are allowed to use. Use only the details I give you. Do not invent metrics, customer stories, rankings, or features. If something is missing, mark it [NEEDS INPUT].

Product name, what it does, and who the customers are: [PRODUCT]
Usage data we track per customer and can legally use in email (for example projects created, hours saved, files shared, orders placed): [DATA FIELDS]
Product highlights we shipped this year that customers actually used: [HIGHLIGHTS]
Email tool and whether it supports per customer merge fields or dynamic blocks: [EMAIL TOOL]
Customer segments that need different versions (new this year, power users, inactive accounts): [SEGMENTS]
Planned send date and any offer or next step for 2027, if any: [SEND AND CTA]
Brand tone (playful, warm, minimal, premium): [TONE]

Requirements:
1. Review [DATA FIELDS] and pick the 3 to 5 stats that are most meaningful and least awkward to show. Flag any field that could feel invasive, could be zero or embarrassingly low, or might break if missing, and suggest a fallback line for each.
2. Design the email structure block by block: hero stat, personal milestones, product highlights from [HIGHLIGHTS], a thank you note, and a call to action from [SEND AND CTA].
3. Write copy for each block in [TONE], using merge field placeholders like {{projects_created}} that match [EMAIL TOOL]. Keep the full email skimmable in under 60 seconds.
4. Create version notes for each item in [SEGMENTS]. For inactive accounts, write a gentle version that does not shame low usage and offers a simple way back.
5. Write 5 subject line options and 3 preview text options under 90 characters each.
6. Add a simple share card idea: what a customer could post about their year, using only their own stats, and how to keep personal data off the card unless they choose to share it.
7. Write a QA checklist: merge field tests with empty and extreme values, unsubscribe link, privacy review of every data field, mobile rendering, and a seed send to the team.
8. Remind me to confirm that our privacy policy and consent settings allow using these data fields in marketing email before sending.

Deliverables:
1. Stat selection with risk flags and fallbacks
2. Block by block email structure and copy
3. Segment versions
4. Subject lines, preview text, and share card idea
5. QA checklist and [NEEDS INPUT] list