❌ Before
Subject: Three reasons to upgrade to Perplexity Pro
Counts the contents of the email. A user who hasn't upgraded already has a reason — the subject line needed to name their specific failure, not announce that three answers are inside.
✅ After
Subject: You hit the free limit at exactly the wrong moment.
Names the failure state that caused this email to be sent. A user who has hit the free limit recognizes themselves immediately. The email earns the open before explaining what Pro does.
The 5 upgrades — and why they work
1 · Subject + hero: quantity announcement → failure state
"Three reasons to upgrade" tells the reader how many answers are inside. "You hit the free limit at exactly the wrong moment" tells them why this email exists. The reader who has been blocked by the free tier recognizes their situation before the email loads. Recognition drives opens. Content counts don't.
2 · Hero body: feature description → consequence of staying free
"Pro gives you comprehensive answers" describes the product. "The free tier was never built for real work" describes what the reader is doing wrong right now. One is a product pitch. The other is a diagnosis. Diagnosis earns attention.
3 · Comparison table moved before first CTA
The original places the Pro vs Free comparison after two "Upgrade to Pro" buttons. The reader has already decided not to click before they see the information that would help them decide. The rebuild surfaces the table before the first CTA — objection handled before the ask.
4 · Three identical CTAs replaced with one escalating sequence
Repeating "Upgrade to Pro" three times with identical framing trains the reader to scroll past it. The rebuild uses one CTA above the fold (immediate action), one comparison (decision support), and one verdict bar (consequence closure). Each has a different job and different language.
5 · Feature sections rewritten from capability to consequence
"All the top models in one place" names the feature. "GPT-5, Claude, Gemini — without four separate tabs and four separate bills" names the decision the reader is already making wrong. The consequence framing converts readers who already know what the models are — which is everyone who uses Perplexity.
This is the Strategic Flow method
Reader's failure state before the product's solution. Comparison table before the CTA, not after. CTAs that name the consequence, not the product action. Visit
strategicflow.carrd.co to get your emails rebuilt.