I’m interested in hearing from Product Owners and Agile teams who build SaaS products for membership-based organizations. We’re working on a museum membership card software platform, and one of the biggest challenges is deciding what should be prioritized in each sprint. Customer requests come from different directionsmuseum administrators, membership managers, marketing teams, and IT departments.
Some of the most requested features include:
- Digital membership cards for mobile devices
- Apple Wallet and Google Wallet support
- CRM and ticketing system integrations
- Automated membership renewals
- Guest passes and family memberships
- Member notifications and engagement features
- Reporting and analytics for renewals and visitor trends
The challenge is that every customer considers their requested feature the highest priority. While Agile planning helps, balancing customer value, technical complexity, and long-term product strategy isn’t always straightforward.
For those managing similar SaaS products:
- How do you prioritize competing feature requests?
- Do you rely mainly on customer feedback, business value, or development effort?
- Have you found any frameworks that work particularly well for roadmap planning?
I’d really like to learn how other Agile teams approach these decisions, especially when serving organizations with diverse operational needs like museums and cultural institutions.