Before I start I have to be honest about this — I did a lot of research and I wasn’t able to find anything out there around how to name pricing pa

How to use discovery to define pricing packages for a SaaS product

submited by
Style Pass
2021-08-17 13:00:08

Before I start I have to be honest about this — I did a lot of research and I wasn’t able to find anything out there around how to name pricing packages in a product.

There are a lot of useful examples out there as to how to price products, from using different strategies to even how to place them on a page, but there was very little around naming.

How you place pricing packages on a pace has a psychological effect. It turns out, you can actually drive the user to select the ‘middle tier’ package by adding packages around it that almost make no sense. It’s called anchor-pricing.

I’m not going to go too deep into how to do the actual pricing itself, but if you’re curious, the crew at Sumo has a great blog on this.

The important bit here: if how you layout items on a page is important, isn’t naming of those items also important? Absolutely.

Naming a package “Premium” already gives the impression something is going to cost a lot of money. How might we help the user still purchase that package, without making them feel like they’re spending?

Leave a Comment