Opportunity area · theme founders discuss · intermediate

Community opportunity: spent years writing sales emails

Discussion · Spent years writing sales emails. Community signal ≠ product. Extract the recurring job, ignore the loudest anecdote, then narrow. First metric beats first feature. Original insight: community volume predicts attention, not willingness to pay—price a tiny pilot early.

Problem

indie hackers describe the same loop: notice the mess late, patch it manually, promise a system later, repeat next month. Unexpected challenge: the economic buyer and the daily user disagree on what “done” means for “spent years writing sales emails.” Hidden cost: founder-only sales that never become a repeatable motion.

Target user

Operators accountable for outcomes when “spent years writing sales emails” breaks

Proposed solution

Productize the answer you find yourself typing repeatedly in communities—then attach a paid upgrade path. Discussion rule: quote buyers in their words on the landing page; delete founder poetry. Counter-intuitive advice: fewer “would you use this?” chats; more reconstructions of last week’s failed attempt at “spent years writing sales emails.” Distribution bottleneck: marketplaces and app directories tax you twice—once in fees, once in attention. One caution: marketplace dynamics are a trap for solo founders—liquidity is not a weekend project. One recommendation: open the [Idea database](/ideas) siblings for this theme (discussion / validation / distribution) and keep only the angle you can execute. Practical next step: sketch trigger → mess → your path → proof. If proof is vague, you still have a vibe. Real-world pattern: early unscalable work (white-glove onboarding, manual QA) taught companies what to productize later. Straight take: this is a boring-money theme if executed tightly—that is a compliment.