?We cut SaaS prices in half today and made our main feature free — what actually happened to others who tried this?

On Indie Hackers, the solo founder of Snyho (Content Command Center for digital agencies + creators) hit $68 MRR in 3 days at $34/mo, then slashed Pro to $19/mo. Their framing: The $34 price point was a no-brainer for established digital agencies, but it created too much friction for the solo creators, indie hackers, and freelance writers who desperately needed the tool. We slashed the Pro plan down to $19/month because we wanted Snyho to be an indispensable utility, not a luxury expense. Pattern: a price cut works when it unlocks a specific ICP that was bouncing — not as a generic try cheaper. Worth checking: for Causo, who specifically was emailing the is this a bug? question vs who specifically is now converting at $15/$59? If the new conversions are the same persona as the old $25/$150 paying customers, the cut just shrunk revenue; if they’re a different persona that wasn’t converting before, the cut found a new market segment.

On HN, commenter neom pushed back on the iterate on pricing from early feedback framing: Early feedback loops from Joe & friends can be misleading without also stepping back to ask strategic questions like: How big is this pain? Is this pain widespread? Their full point: Real zero to 1 requires that you’ve also done a broader market analysis to understand where you’re headed in a strategic sense, your “vision”. That is not just about refining an artifact based on Joe and a few friends, it’s about deeply understanding the context your artifact fits into, including the broader market dynamics, existing customer pain points, competitive landscape, and whether this thing has legs to actually scale beyond those first friendly testers. In business the answer is the answer, not what you want the answer to be: 5 customers, 500 customers, 5 million customers, there is an answer. Pattern: the pricing experiment will give you a clean conversion delta in 2 weeks — but that delta tells you nothing about whether you’re capturing a 500-customer market or a 5-million-customer one. The price cut might work and still trap you below your real ceiling.

Across Indie Hackers’ SaaS pricing discussion threads, the most consistent advice is: when existing customers ask is this a new price a bug?, that’s the highest-information data point you have. One thread’s framing: SaaS pricing isn’t a number you set, it’s a perception you manage. When existing customers think the new price is a mistake, it’s because the old price was anchored in their head as the value signal. Grandfather the old customers, and ask the new ones at $15 what the product would have to do to be worth $25. Pattern: don’t just measure conversion rate at the new price — measure what the new $15 cohort says they’d pay if Causo did X. The price cut isn’t permanent; it’s a question you’re asking the market. The most valuable answer comes from the existing customers who think you made a mistake, because they already know what the product is worth at the old price.