You are not alone in struggling to decide which features to put in which packages… yet again.
Or debating with your leadership whether to add a 2nd or 3rd or 4th package.
Or questioning what should be included in a package versus sold as an add-on.
Even when you’re finally feeling good about your packaging decision, your engineering team will ship a 💣 new feature that throws everything in disarray.
To help make these everyday decisions a little easier, I’m sharing - for the first time ever - my top 10 guiding principles for designing SaaS packages. These have been divided into strategic packaging principles and then more tactical advice.
Disclaimer: These principles may not apply to all situations and some may be in conflict with others. Please use your best judgment.
Keep reading with a 7-day free trial
Subscribe to Kyle Poyar’s Growth Unhinged to keep reading this post and get 7 days of free access to the full post archives.