positioning-and-story

# Positioning & story > Your story is boring without a villain. And you are not the hero of it. The developer is. You're the wise advisor who hands them a better weapon. **Use this when:** your homepage explains what your product *does* before it names the problem, your positioning is interchangeable with three competitors, or nobody feels any urgency to act now. ## The core idea Developers don't buy features; they hire a tool to defeat something that's making their life worse. Get the roles right: - **Hero** = the developer (never the vendor, never the product) - **Villain** = the undeniable *trend* making the pain worse every day - **Wise Advisor** = you, arriving with a gift (the product) - **Inciting event** = the change in the world that forces the hero to act *now* No villain → no urgency → no story → no conversion. ## Framework: the 3-part story (Frankl) 1. **Inciting event**: introduce the hero and the villain; the world changed and the hero can't stay put. 2. **Obstacles**: a series of specific challenges, each solved with your help, best told as mini before/afters: *"Before X, we had [problem]. Now [measured result]."* 3. **Resolution**: villain defeated (for now), specific results, hero shares the wisdom → that's your testimonial. **The benchmark (EngFlow):** > *"Slow builds waste your time. Standard build tools can't handle today's codebases. Speed up builds now to keep engineers in flow."* - Pain: slow builds waste your time - Villain: standard tools ca...