[HN Gopher] Ask HN: When does changing pricing models break user...
       ___________________________________________________________________
        
       Ask HN: When does changing pricing models break user trust?
        
       I'm curious how people here think about this.  Many apps start with
       a one-time purchase. Clear deal. You pay once, you own the
       features.  At some point, the business model changes: subscriptions
       are introduced, and features people already paid for disappear or
       become locked behind a new paywall.  I understand why subscriptions
       exist. Recurring revenue makes products easier to sustain.  But
       from a user perspective, this feels like changing the rules after
       the fact. Not a price increase for new users -- but a retroactive
       change for existing ones.  I recently added GPX import to a project
       I work on, specifically to avoid data lock-in. The idea was simple:
       even if someone stops using the app, their data should remain
       usable elsewhere.  This raised a broader question for me:  * Is it
       ever acceptable to change the deal for existing users? * Where is
       the line between sustainable monetization and broken trust? * How
       do you think about "ownership" in software you paid for once?
       Genuinely interested in perspectives from founders and users.
        
       Author : skicoachapp
       Score  : 5 points
       Date   : 2026-01-21 21:49 UTC (1 hours ago)
        
       | JohnFen wrote:
       | > At some point, the business model changes: subscriptions are
       | introduced, and features people already paid for disappear or
       | become locked behind a new paywall.
       | 
       | If this happens, trust is immediately broken. They have taken
       | away something I paid for. It's a kind of theft.
       | 
       | > Is it ever acceptable to change the deal for existing users?
       | 
       | Not for one-time sales. If it's an ongoing contractual
       | arrangement, like a rental or service subscription, then it's
       | acceptable to change the offer when the contract renews or on
       | terms agreed to in the contract.
       | 
       | > Where is the line between sustainable monetization and broken
       | trust?
       | 
       | There is no tension between those two things. If you make
       | promises, don't break them and there won't be trust issues.
       | 
       | > How do you think about "ownership" in software you paid for
       | once?
       | 
       | If I have paid for software without the terms being a rental from
       | the start, then my expectation is that I will be able to continue
       | to use the software forever (or as long as I have machines that
       | can run it).
       | 
       | I don't expect to get free updates. If I want an updated version,
       | I expect to pay for it. There's a gray area here about security
       | updates, though. A good company will provide security updates at
       | no charge, and feature updates separately for a charge.
        
         | skicoachapp wrote:
         | This matches my intuition almost exactly.
         | 
         | Especially the distinction between: paying once to _own_ a
         | version vs paying for an ongoing service.
         | 
         | I think a lot of conflict comes from companies blurring that
         | line after users have already built habits and trust.
         | 
         | The point about security updates vs feature updates is
         | interesting too -- that gray area is where many products
         | struggle to be explicit.
        
           | JohnFen wrote:
           | What I've described is also pretty much the way this worked
           | for all software back in the day.
        
       | bobby_lea wrote:
       | I see this happen so frequently, and my co-founder and I are
       | grappling with exactly this issue. Our model will rely on
       | subscription rev for a good portion of total rev once we are at
       | full capacity, but we won't be there at launch. The approach we
       | are taking now is deliberately holding back from V1 and V2 the
       | features that we think will be the real value-ads that will
       | entice paid memberships. That way, instead of asking people to
       | pay for a think they previously got for free, we will be adding
       | new features and asking people to pay if they want more - or stay
       | on the free membership and continue doing what they are already
       | doing.
        
         | skicoachapp wrote:
         | That approach makes a lot of sense to me.
         | 
         | Adding new value and asking people to pay for _more_ feels
         | fundamentally different from taking something away and asking
         | them to pay to get it back.
         | 
         | The moment users feel something was removed, the conversation
         | shifts from value to resentment.
        
         | JohnFen wrote:
         | This is the way, in my opinion.
        
       ___________________________________________________________________
       (page generated 2026-01-21 23:01 UTC)