How do you increase the price of a product without scaring away customers?

In my 4 or 5 years of working at startups, I’ve noticed that people always have a problem when they are told about changes:

– free version jumped to a trial with a subscription or lifetime purchase

– subscription and lifetime purchase prices increased

People who have already experienced a certain price (or free access) are very reluctant to pay more when they know they were paying less.

New people are more likely to jump to the newer (higher) price.

But older users usually start complaining:

– on support

– in comments under posts on social networks

– in public forums where ratings are given

How do you communicate the increase in the original price?

(e.g. do you add features to justify it, or what is your crisis communication plan that limits your churn rate and negative sentiment)

162 views

Add a comment

Replies

Best

I think there's not much you can do. There are always people people that are angry in that situation.

I made a change to a month ago so some features that had been free now require a paid plan.

Revenue increased by factor 4, Google Play rating dropped by 0.6 stars.

 If the revenue goes up, probably it was worth taking the steps.

 A 4x increase in revenue is a strong result, even with the drop in rating. It also shows how sensitive users can be to changes in features they were used to getting for free. Clear communication and a transition period can probably help reduce some of that frustration.

I think the key is to handle old vs new customers fairly. If the price was 25 and is now 30, existing customers should have time to reconsider or keep their original rate. That way, loyalty is respected while the new pricing moves forward.

 That is fair. I think, that implementation on the backend should not be that difficult, or?

it should not. its all about Konfiguration

It depends on many circumstances, but here are some ideas:

- Begin with a high price you expect to maintain. It is always better to lower it than to increase it in the future.

- Keep the low price for the existing users only, if possible. This can reward those who supported you from the start.

- Add features over time. Only raise the price when you add new features. Keep a lower price for a plan with the old features. Possibly, the new features are the answer for existing users, so many will have the incentive to upgrade. 

 Very well defined. Gives a fair idea on pricing change and adjustment

 I want to go with the 3rd option for sure. But first, I want to collect free users to create som buzz for Safelimit :)

I think if you are providing more value with the increase then you shouldn't worry about it and the can market the additional features without mentioning or justifying the price increase.

If you are providing same value or taking value away (eg, product features remain the same, a feature is no longer free, etc) then you should expect people to complain.

 I will see in the future in my own product how things gonna play out :D

Do you think its better to raise prices slowly or make one big price increase?

 I would go slowly for sure. And prepare them in advance :D

 Yeah I agree going slowly gives people time to adjust and makes the change feel more natural

I always think back to early Netflix days, their prices have more than tripled, but their subscribers have increased fifteen-fold. As an early adopter, I personally cannot stand the platform now, but somehow they have over 320 million subscribers. I cannot deny that they have increased their value financially, despite price increases over the years, sometimes twice in one year. The price increases usually come right after they have a big event (NFL, WWE, etc.), which allows users to “feel” as if they are getting more value, when they really are not. Perception is everything!

 well, people will pay for that, because people love procrastination :)

We rushed features to justify price increase. Mid-task coding agent lost context and rebuilt existing helper function two files away under new name. So we shipped duplicate code just to rationalize higher tier. Lost far more trust than the price change itself)

 Was there any fix or? :D Because once you lose trust... well, that will be bad.

 We cleaned up the redundant code, publicly admitted the release was rushed, and grandfathered existing users into their original pricing.

You raise it for new customers if you can keep your margins high enough.

This turns current customers into evangelists.

 I will probably do the same :)

I think the worst part is when it feels like same product but just more expensive. I’d probably just give old users some time or keep their old price for a while, then be super clear about what changed. Because people usually get more upset when they feel trapped than when the price goes up itself

 yeah, probably they wouldn't stay if (besides price) nothin else changed :D

Most of the complaints you list come from a price that changed after somebody had already been told the old one. So the version I chose is to put the rise into the offer itself, before anyone has paid.

Our launch price is set per hundred paying customers. The pricing page says how many places are left at the current rate, and after each hundred the rate steps up, four times, and then it holds. Nobody who buys at the first rate was promised it for ever, and nobody who arrives later was shown a lower one. I should say plainly that we have not sold one of those places yet, so this is a design, not a result.

The second half is what a rise touches. Most of what we sell is packs of invoices, and the credits never expire, so what someone already paid for stays theirs at the rate they paid. The new price only applies to the next pack they choose to buy. There is nothing to grandfather, because nothing they hold gets repriced.

One trap is where the old price keeps living after it changes. A cached page, a share card, a directory listing or a comparison page can go on quoting it, and then a visitor meets a bigger number at checkout than the one they just read, which is exactly the complaint you describe, and one we would have caused ourselves. A directory once built our tagline straight out of a meta tag. So our cached pages print only the one price that never moves, and the charge is computed from the same place the page reads.

So my answer: announce the rise before the first sale, never reprice what people already hold, and find every copy of the old number before the new one goes live.

 With this strategy, it is better to start with a higher price from the beginning so I do not have to be scared from "what if" scenarios when I want to increase the price. They will pay more outright :D

 That is the cleanest version of it, and it works if the first buyers will pay it. My problem is the step before: with no paying buyers yet, a high first price is a guess I cannot test, while a price that starts low and rises in public at least tells the first people why now is the cheap moment. Ask me again after the first hundred.

12
Next