Freemium: How do you decide what's free and what's not?
I'm working on https://httptoolkit.tech, a suite of developer tools. I've just released a first free version with a very minimal feature set, and I'm starting to build out the paid feature set (and checkout infrastructure etc) at the moment.
The hardest question I'm coming up against is how to decide what features should be free, and what should be paid only. The free version is a major marketing channel, so needs to be useful enough that it's interesting, but obviously I need there to be a strong incentive to buy the paid version.
Do you have any heuristics for where the line should be? Anybody have any stories where this decisions has gone especially well or badly for them?
This is super easy to get wrong. Long story short => most SaaS that use a freemium model end up either dying or killing the free option. Usually large growth companies open freemium to fill the top of the funnel.
I’d study materials from Patrick at Price Intelligently. He will blow your mind on what you should do here.
It is a lot of trial and error. For us, it was features around branding (custom domain, no footer, etc).
Maybe you restrict the number of domains or only allow the free version on well known public domains.
Same! Custom branding seems to be a good one. At the start, people won't care about a "Powered by" message or something along those lines, but ultimately people/companies will want to be able to separate themselves a bit and use their own domain, etc.
This comment was deleted 7 years ago