This suggests the price may be set too high relative to perceived value; this lesson specifically notes that “frequent, strong pushback may suggest the price is set too high relative to perceived value,” and an 80% pushback rate (a notable increase from before) represents exactly this kind of frequent, strong signal this lesson identifies as worth taking seriously, rather than the kind of occasional, normal pushback that doesn’t necessarily require any change.

No, likely not; this lesson specifically distinguishes churn correlating with stated price concerns (which would suggest a pricing issue) from churn driven by other issues like “missing features or poor support”; since this pattern shows customers citing a missing feature (not price) as their reason for leaving, this suggests the more appropriate response would address the product’s feature gaps rather than adjusting price, since price doesn’t appear to be the actual underlying issue driving these specific cancellations.

Grandfathering; this lesson specifically recommends “allowing them [existing customers] to continue at their original, lower price rather than being forced into the new, higher price immediately,” since existing customers made their purchasing decision based on the original price and suddenly changing this “can feel like a broken promise,” risking unnecessary churn among already-satisfied customers.

Existing customers made their original decision to sign up and continue paying based on the price that was in effect at that time – they had no reason to expect this price would suddenly change after their commitment was already made; even if the founder has entirely legitimate reasons for raising prices for new customers going forward (perhaps reflecting increased value delivered, or correcting an initially too-low price), retroactively changing the terms for people who already committed under the original terms can reasonably feel like an unexpected, unilateral change to an agreement the customer thought was already settled, which is what creates this “broken promise” feeling this lesson describes.

This practice helps avoid “unnecessary churn among already-satisfied, currently-paying customers specifically because of a pricing change they didn’t sign up for”; by preserving existing customers’ original pricing, the founder avoids potentially losing these already-satisfied, already-retained customers over a price change that only affects new customers going forward, rather than existing customers who had no expectation of this change.

This approach doesn’t align well with this lesson’s recommendation; this lesson specifically states that “price adjustments… should generally be evidence-based rather than arbitrary or based purely on founder intuition,” and personal belief about deserved value, without supporting evidence like pushback patterns or churn analysis, represents exactly the kind of intuition-based (rather than evidence-based) reasoning this lesson advises against for pricing decisions.

This connection highlights that the underlying discipline this course has emphasized throughout – making significant decisions based on gathered evidence rather than assumption or intuition alone – applies consistently across different specific decisions a founder faces at different stages, not just during the initial idea-validation stage; just as customer interviews and demand tests provided evidence for the initial build/narrow/walk-away decision, and the necessity test provided evidence-based discipline for MVP feature scoping, this same evidence-based mindset (using pushback rates and churn reasons as evidence) should similarly inform ongoing pricing decisions after launch, rather than pricing being treated as a fundamentally different kind of decision exempt from this same evidentiary discipline.

Not necessarily; this lesson specifically distinguishes “occasional pushback” (which “is normal and doesn’t necessarily require a change”) from “frequent, strong pushback” (which suggests an actual pricing problem); occasional, infrequent pushback from a small minority, with most prospects proceeding without concern, matches the normal, expected pattern this lesson identifies as not necessarily requiring any adjustment.

Not necessarily complete on its own; this lesson identifies both signals (pushback during sales conversations, and cancellation reasons) as useful, suggesting a more complete evidence-based evaluation would ideally consider both together rather than relying on just one; a founder might reasonably want to check whether the cancellation pattern also supports the same conclusion suggested by pushback signals alone, before concluding a price change is definitely warranted based on incomplete evidence from only one of these two potential signal sources.

This situation might suggest it’s worth investigating whether the original price, set over a year ago with less product value than currently exists, might now be leaving value on the table relative to what the product currently delivers; while this lesson’s specific signals focus on pushback and churn as indicators a price may be too high, the underlying principle that pricing should be an ongoing, evidence-based process (not a one-time, permanent decision) suggests a founder should periodically revisit pricing in light of significant product changes, rather than assuming the original price remains appropriate indefinitely regardless of how much the underlying product has evolved.

Based on this lesson’s reasoning, the founder who grandfathers existing customers would likely retain more of their existing, already-satisfied customer base following the price increase (since these customers aren’t experiencing the specific “broken promise” feeling this lesson describes), while the competitor who doesn’t grandfather existing customers might experience more unnecessary churn among their existing base specifically due to this pricing change, even among customers who were otherwise satisfied with the product itself before this unexpected price change affected them.

Because an initial price is set with necessarily limited pre-launch information (value-based estimates and competitor anchoring, as covered in an earlier lesson, both involve some degree of informed estimation rather than certainty), real-world evidence gathered after launch – specifically, how often and how strongly prospects push back on price, and whether cancellations specifically correlate with stated price concerns – provides genuinely new, more concrete information that wasn’t available when the original price was set; treating this post-launch evidence as relevant, ongoing input for potential price adjustment (rather than treating the original price as fixed and unchangeable regardless of what this new evidence reveals) allows a founder to continuously refine their pricing decision using real, replayable market feedback, consistent with the evidence-based decision-making discipline this course has emphasized throughout.