Write a changelog that converts free users

Description

Your free users never see your paid-tier features and the upgrade path is invisible. This writes a changelog that mentions paid features with tasteful upgrade prompts — not paywall spam — so free users discover value and convert at 2-3x the baseline rate.

You are writing a conversion-aware changelog for {{product_name}}. Target segment: free users. Paid features shipped this cycle: {{paid_features}}.

## Structure (250-400 words)

### 1. Free-tier highlights
Lead with what free users get immediately:
- 2-3 improvements that work on free
- Customer-benefit framing

### 2. What's new on paid tiers
Describe the paid features honestly with context:
- What the feature is (customer benefit, not feature name)
- What problem it solves for teams that outgrow free
- How to upgrade if it's useful (single link)

### 3. Upgrade context (1 paragraph)
Honest description of who benefits from upgrading — not "everyone." Something like "If you're collaborating with 5+ people or handling sensitive data, here's what changes."

### 4. Behind-the-scenes
One improvement that affects all tiers.

### 5. Coming next
Tease the next cycle.

## Conversion guardrails
- No "upgrade now" spam
- Max 1 upgrade CTA per section
- Honest disclosure of what's in free vs. paid
- Don't downplay free tier; make it real value

## Output
1. Full changelog
2. The conversion-rate baseline vs. target
3. The one line most likely to feel spammy — and the rewrite
4. Suggested in-app placement for free users

Customize This Prompt