I ran 59 SaaS email teardowns and built a free diagnostic tool from the patterns.

Four months ago I started auditing SaaS emails from real companies.

Not as a service. As research.

I wanted to know whether the structural failures I was seeing in individual emails were isolated mistakes or a consistent pattern across the industry.

So I picked companies: Semrush, HeyGen, Optimizely, Revolut, Notion, Perplexity, ElevenLabs, Zoho, Wiz, dbt Labs, ran their emails through a 7-point diagnostic framework I'd developed, scored them, named the failure patterns, rebuilt the emails, and published everything publicly.

59 teardowns. Every single one open at strategicflow.tech/teardowns.html.

Here's what the data shows.

The 3 structural failures that appear in almost every SaaS email

Feature-First Bias — 83% of emails

The email leads with what the product does instead of what changes for the reader.

"We're excited to share our new real-time collaboration feature" is Feature-First Bias.

"Your team just lost 4 hours to version conflicts last week" is consequence-first.

One tells the reader about the product. The other tells the reader about themselves.

Most readers close the tab after the first type. Most readers keep reading after the second.

Guest Language CTAs — 96% of emails

"Learn more." "Explore now." "Discover." "Check it out."

These are the company's words for what the company wants the reader to do. They place the action in the company's frame, not the reader's.

"See if this applies to my team" is the reader's language. It names a decision, not an action.

96% of the 59 emails I audited used Guest Language CTAs. This is the single highest-frequency failure in SaaS email communication.

Consequence buried after the caveat — 74% of emails

The thing that would make someone stop scrolling — the number, the result, the before-and-after — appears in paragraph three. Sometimes paragraph four.

By then, most readers have already decided whether to click. The consequence that would have changed their mind never reached them.

The numbers

Average original architecture score across all 59 audits: 3.4 out of 10.

Average rebuilt score after structural correction: 9 out of 10.

Same content. Different sequence. No new copy written from scratch.

The problem was never the words. It was always the order.

What I built from these patterns

After 59 teardowns, the most common question I received was: "How do I know if my email has this problem?"

Not a competitor's email. Their email. The one sitting in drafts right now. The one they're about to send to 6,000 users without knowing whether the architecture is working against them.

Manual teardowns don't scale. One person, one teardown at a time, is a content strategy — not a product.

So I built WHY.™

WHY.™ is a friction diagnostic tool built on the Decision Friction Model. You paste any content and it returns three things:

A Friction Score from 1 to 10.

Structural, not stylistic. A score below 4 means the architecture has significant problems that copy-level edits won't fix. A score above 7 means the architecture is working.

5 named friction points with HIGH / MID / LOW impact ratings.

Each one references your actual content. Not "improve your CTA." Something like: "Your CTA reads 'Learn more about our new dashboard.' This names a destination, not a consequence. The reader has no reason to click because the email never states what changes for them after they do."

15 predicted questions your reader will ask — with answers.

This is the feature that changes how you write before you publish.

WHY.™ predicts the exact questions your reader will have before they reach the CTA — the silent objections, the missing context, the unanswered "so what?" moments — and answers each one. For each question, it states whether the content answers it, and if not, exactly what needs to be added or changed.

These are the questions your reader had before they closed the tab without clicking. Now you know what they were.

Then it rebuilds your content.

Consequence-first structure. Every friction point resolved. CTA reframed around the reader's outcome, not the company's action.

I ran my own content through it first

Before I called WHY.™ finished, I ran my own LinkedIn post through it.

The post was about a Zoho blog that had 107 views and a 6-minute average read time, good engagement signal, zero conversion signal.

The post argued that a $874,000 number buried in paragraph four was causing the underperformance. Moving it to the headline changes who keeps reading after line one.

WHY.™ scored the post: 6 out of 10.

The highest-impact friction point: "The post claims moving the $874,000 number to the headline changes reader behavior, but never shows the revised headline. The reader is asked to believe the transformation without seeing it."

I had written a post about the power of showing before-and-after. And I hadn't shown the before-and-after.

The 8 questions WHY.™ predicted my readers would ask — none of which the post answered:

What did the new headline actually say?

What does a 3/10 architecture score actually measure?

Did the article's performance change after the fix?

Is this a real client or a hypothetical teardown?

What should a consequence-first brief actually look like?

How do I know if my own content has this problem?

Who is Alex Iliescu and why should I trust this diagnosis?

What does the reader get out of reposting this?

I fixed all eight before publishing. The rebuilt version scored 9 out of 10.

What WHY.™ works on

Email. Landing pages. Proposals. LinkedIn posts. Sales decks. Case studies. Product updates. Cold emails. Pricing pages. Briefs.

Anything that's supposed to move someone to action — and isn't.

The honest part

WHY.™ is pre-revenue. Zero paying customers today.

It's free, 3 diagnoses per IP, no email required. The rate limit redirects to Strategic Flow's paid audit packages.

The goal: use WHY.™ as the awareness layer. The free diagnosis surfaces the structural problem. The paid audit delivers the full solution.

I'm not launching today. I'm sharing what I built and what I learned building it. If the tool surfaces something real in your content, that's the point.

Try it

strategic-flow-audit.replit.app/why.html

Free. Three diagnoses. No email required. No account.

Paste your next email before you send it. Paste the landing page you've been optimizing for six weeks. Paste the proposal sitting in someone's inbox right now.

Find out what question your content never answers.

WHY.™ is built on the Decision Friction Model, the diagnostic framework behind 59 published SaaS email teardowns.

WHY.™ · A Strategic Flow product · strategicflow.tech

Happy to answer questions about the methodology, the build, or what a 3.4/10 average score across 59 real SaaS emails actually tells you about the industry.