SUBJECT LINE OPTIONS: A) "The mistake that cost me $40k" (47 chars) B) "Why your funnel is leaking money" (33 chars) PREVIEW TEXT: Most founders fix the wrong thing first. Here's what I'd do differently. OPENING HOOK: In 2022, I spent six months building a feature nobody wanted. Not because I didn't do research — because I asked the wrong questions. The brutal truth? Most early-stage startups die from good execution of a bad idea. Here's the framework I now use before writing a single line of code. SECTION 1 — THE PROBLEM: THE VALIDATION TRAP Most founders validate by asking "Would you use this?" That question is useless. People lie to be polite. What you need is behavior data: are they currently paying for a workaround? How much time do they lose each week? Real validation isn't a survey — it's a credit card or a calendar invite. SECTION 2 — THE INSIGHT: DEMAND VS. DESIRE There's a difference between what people want and what they'll pay for. Desire is "I'd love a personal chef." Demand is "I already spend $800/month on meal delivery." Your job is to find demand — an existing budget you can redirect — not create desire from scratch. SECTION 3 — THE PRACTICAL TAKEAWAY: THE 48H TEST Before your next build sprint, run this: find 10 potential customers this week. Don't pitch. Ask: "What's the most painful part of [problem]? What do you currently do about it?" If 7 of 10 describe the same pain without prompting, you have signal. If not, pivot the question — not the product. CLOSING & CTA: Building in the dark is exhausting. This framework won't guarantee success — but it'll stop you from wasting six months like I did. If you found this useful, forward it to one founder who needs to hear it. → Reply "VALIDATE" and I'll send you my full 10-question customer discovery script. ENGAGEMENT HOOK: What's the biggest assumption you're currently building on? Hit reply — I read every response.