How to kill a hydra? (without Hercules on staff)

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!

5 comments