Positioning

Positioning can start from an emotional consumer desire, an outcome that creates a new buying opportunity or a job already repeated among the best paying customers. The last route uses observed spend, close ease and use case to revise the original ICP after launch. Whichever promise is chosen, feature requests still need filtering so the workflow or tier boundary does not blur. Positioning remains a hypothesis until activation, retention and customer outcomes support it.

Start here

1. Discovering an ICP from Paying Customers — Use when post-launch calls reveal a repeated high-value job.
2. Positioning SaaS Around an Outcome-Created Opportunity — Decide whether outcome education can reach buyers outside the existing category.
3. Positioning a Mobile App Around a Core Desire — Anchor a consumer app in a durable desire and visible gap.
4. Filtering Feature Requests Without Diluting Positioning — Protect the chosen difference as requests arrive.

Pages

• Discovering an ICP from Paying Customers — Nicholas Dulait using ChatSEO; retarget around the repeated job of the easiest, highest-spending customers
• Positioning a Mobile App Around a Core Desire — Frederick James; a consumer app anchored in a recurring desire and one missing incumbent feature
• Positioning SaaS Around an Outcome-Created Opportunity — Nevo David; teach a customer outcome to create demand beyond feature-comparison shoppers
• Filtering Feature Requests Without Diluting Positioning — Tibo using Revid.ai; reject requests that blur the core workflow or tier boundary

Gaps

• Minimum paying-customer sample and comparison fields before narrowing an ICP
• Customer-interview methods for separating the underlying job from a requested implementation
• Activation, retention and lost-deal evidence before and after a positioning change
• Controlled comparisons of feature-led and outcome-led positioning for B2B workflow products