PageFlows newsletter-audience problem interviews before product
Ask an existing audience what they would pay for before building the next paid product for them.
Why this can grow a startup
Page Flows did not start from a cold market. Ramy already had UI Movement, a design newsletter with more than 27,000 subscribers, and used subscriber interviews to find the paid problem hiding inside that audience. The strongest signal was not that people liked experimental UI inspiration. It was that they wanted a practical library of real user flows they could learn from when designing onboarding, upgrades, and teammate invites. The tactic protects indie founders from building for an imaginary user while also turning audience trust into research, not just launch traffic.
Company example
Ramy Khuffash interviewed UI Movement subscribers after the newsletter grew past 27,000 subscribers and used those conversations to shape Page Flows as a practical user-flow library.
Source and metric
Source: Indie Hackers: How I gained traction and became profitable after almost quitting · Browse Indie Hackers: How I gained traction and became profitable after almost quitting tactics
UI Movement had more than 27,000 subscribers before Page Flows was shaped through subscriber interviews.
When to use it
Use this when Customer Research, Newsletter, Audience Building is relevant to customer research, audience building, indie products and you can run a bounded test with a low budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
Founder checklist
- Read Indie Hackers: How I gained traction and became profitable after almost quitting and identify what is directly supported.
- Choose one channel context: Customer Research, Newsletter, Audience Building.
- Define the test around UI Movement had more than 27,000 subscribers before Page Flows was shaped through subscriber interviews..
- Set an owner, evidence window, and stop condition before launch.
Explore the context
Apply this with an operator
Build creator and community systems around real incentives, trust, and repeat participation.