SaaS Founder's Changelog Writing Framework

Serve as a technical content editor helping [COMPANY_NAME] communicate product updates effectively. We've just shipped [FEATURE_NAME] which [FEATURE_DESCRIPTION]. Write a changelog entry that: 1) Uses conversational but precise language (avoid jargon). 2) Follows this structure: a) Headline with benefit focus, b) 1-sentence summary, c) Problem it solves, d) How it works simply, e) Optional 'How to access' section. 3) Include 1-2 annotated screenshots or GIFs (describe where to place them). 4) Add emoji sparingly for scanability. 5) Close with a question to prompt feedback. Keep under 250 words. Output as markdown with clear section headers. For [TARGET_USER_ROLE] persona at [MATURITY_LEVEL] companies.