A 7-point behavioral diagnostic framework that scores SaaS emails 1-10 and names the exact structural failure stopping readers from clicking. Not copy. Not deliverability. Architecture.
The Decision Friction Model is a 7-point behavioral diagnostic framework for identifying the structural failures that stop B2B SaaS emails from converting. It scores every email from 1 to 10 across seven checkpoints, each mapping to a specific reader behavior. It names the exact failure pattern present. It outputs a rebuilt email with the architecture corrected.
Decision friction is any element in an email that interrupts, delays, or eliminates the reader's decision to act. Friction is structural — it lives in the order of information, the visual hierarchy, and the CTA language. It does not live in the tone, the brand voice, or the word count. Most SaaS email teams optimize the wrong layer. They rewrite copy. They test subject lines. They change the template. The architecture stays broken and the click rate stays low.
The Decision Friction Model was developed by Strategic Flow across 59 published teardowns of B2B SaaS emails from companies including Notion, Figma, Revolut, Wiz, Ahrefs, HeyGen, ElevenLabs, Optimizely, and 51 others. The same six structural failure patterns appeared in every vertical, at every company size, with near-identical frequency. The model names them. The rebuild fixes them.
Each checkpoint maps to a specific reader behavior — what makes them open, what makes them read past the first line, what makes them trust the claim, what makes them click. A score below 5 on any single checkpoint is a structural failure that prevents conversion regardless of the offer.
Does the subject line name a consequence or curiosity gap — or does it announce a topic like a folder tab? A Filing Label Subject gets opened out of obligation. A consequence-first subject gets opened out of self-interest.
Filing Label Subject →Does line 1 name the reader's problem — or does it open with a product announcement, a caveat, or "We're excited to announce"? Feature-First Bias and Consequence-After-Caveat both fail here. Most readers decide in the first sentence.
Feature-First Bias →Does the email translate product capabilities into reader consequences, or does it describe what was built and leave the reader to infer the benefit? "Advanced Reporting" is a feature. "Your reports build 40% faster" is an outcome.
Does the layout direct the reader's attention to the most important claim — or does every section receive equal visual weight? Missing Visual Hierarchy means the reader scans everything, decides nothing matters, and leaves without acting.
Missing Visual Hierarchy →Does the email show the reader's current state versus their future state after acting? Without before/after contrast, the reader has no felt reason to change their behavior today rather than tomorrow.
Is there a named customer result, a specific metric, or a third-party voice above the fold — or is proof absent or buried? Proof that arrives after the CTA arrives too late. The reader has already decided whether to trust the claim.
Zero/Buried Social Proof →Does the CTA verb describe what the reader is doing — or what the brand is offering? "Learn more" is guest language. "Fix my reporting" is ownership language. Guest Language CTA is the most common failure in the dataset: 96% of audited emails.
Guest Language CTA →Across 59 teardowns, six structural failure patterns appear with near-identical frequency regardless of company size, budget, or vertical. A nine-figure company scored 2/10 on the same diagnostic a seed-stage startup fails.
Data from 59 Strategic Flow teardowns, 2025-2026.
The Decision Friction Model does not evaluate whether the product is good. It evaluates whether the email architecture allows the reader to reach a decision. Below is the same product update email — original and rebuilt — with only the architecture changed.
Paste one email. Get a score across all 7 checkpoints, the named failure pattern, and rebuilt HTML. 90 seconds. No signup.