I was going through the Classroom course on Packaging and I have few questions @Ulrik Lehrskov-Schmidt 1. While taking an inventory of features, how do i clearly identify the commercial features? Are these features serving only a certain category of customers, like for example, something that only a tier1 customer might use? 2. Is it mandatory to have commercial features?

Hi guys What community activities and content would you like (or even participate in)? Stuff I can do: 1) Open Q&A with me (e.g. monthly) 2) Teardowns: send me your pricing case and I'll record as I open it up and provide live feedback. 3) Webinars on topics (like the ones scheduled) 4) ? ... let me know Stuff community members can do (but I can help arrange): 1) Cases: go on a podcast with me and show off your pricing project: objectives, process, new model, outcome, learnings etc. 2) Pools: e.g. 'How often do you change pricing?' 3) Guest speakers: we invite people to come and give an AMA session, present their work, their new book etc. (or that guest speaker is YOU!) 4) Collaborative Document Creation: someone posts a link to a google doc with a 1st draft of a document like: an email to tell customers prices go up / end of life of a product / job posting for a pricing manager / SOP for sales to give discounts / ?? - community can then edit, comment and create a 'final' version (or 7 different versions), which gets put in a common library for all. 5) Experience marketplace: e.g. "I need some coaching on how to get Sales to stop selling bespoke solutions. I can offer tested framework for how to prioritise feature development in collab between Sales and Product" -> people find each other and take it to a private conversation. 6) ??? let me know your ideas Use this thread to discuss, suggest and just to let me know what you'd actually invest time and attention in consuming, participating in etc..

Hi Ulrik - I've read your book 3 times - its become the cornerstone of a major pricing project at our 10+ year old SaaS. We've built a hydra and its complexity is driving up dev, sales, support and marketing costs - and killing sales. We need to repackage, but from a 'jobs to be done' perspective we have smaller customers who have only a handful of users doing many jobs, and larger customers who have many stakeholders who split and specialize these jobs job into many smaller jobs. What might you suggest to unwind the hydra and can we overlap jobs to address different sized customers? I think we have found fair (confirmed by a few customer interviews) metrics which can differentiate between the larger and the smaller customers, but the packaging still seems tricky. Thanks!