# PageFlows newsletter-audience problem interviews before product > Ask an existing audience what they would pay for before building the next paid product for them. - Canonical HTML: https://growth.iangoh.com/growth-ideas/pageflows-newsletter-audience-problem-interviews-before-product/ - Source: [indiehackers.com](https://www.indiehackers.com/interview/how-i-gained-traction-and-became-profitable-after-almost-quitting-18dc0bc62d) - GrowthDex source hub: [Indie Hackers: How I gained traction and became profitable after almost quitting](/sources/indie-hackers-how-i-gained-traction-and-became-profitable-after-almost-q/) - Last checked: 2026-06-07T02:26:25.106Z - Rarity: rare - Budget: low - Channels: Customer Research, Newsletter, Audience Building - Stages: customer research, audience building, indie products, product discovery - Key metric: UI Movement had more than 27,000 subscribers before Page Flows was shaped through subscriber interviews. ## Why this can grow 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. ## Ian's take From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it. ## Action plan 1. Define one narrow startup segment where pageflows newsletter-audience problem interviews before product can create a measurable lift. 2. Turn the tactic into one offer, page, campaign, or workflow for the Customer Research and Newsletter channel. 3. Use the evidence from indiehackers.com to set the first version of the message, format, and audience. 4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal. 5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook. ## Source-backed 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. ## Adjacent tactics in the same lane - [PageFlows fake payment form before building paywall](/growth-ideas/pageflows-fake-payment-form-before-building-paywall/) - same source, 1 shared stage - [PageFlows sporadic-use quarterly pricing](/growth-ideas/pageflows-sporadic-use-quarterly-pricing/) - same source, 1 shared stage - [PageFlows long-tail flow pages from every recording](/growth-ideas/pageflows-long-tail-flow-pages-from-every-recording/) - same source, 1 shared stage - [PageFlows low-overhead library margin watch](/growth-ideas/pageflows-low-overhead-library-margin-watch/) - same source, 1 shared stage ## Read GrowthDex essays Browse the plain-English essay index at [GrowthDex Blog](/blog/). ## Related GrowthDex essays - [The library should survive the first wrong price](/blog/the-library-should-survive-the-first-wrong-price/) - indie products, pricing, programmatic SEO ## Advisory If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.