Just adding my support for a more flexible pricing structure. I think all you need to do is lower the entry point of the plan, as suggested previously. If a customer could start at $10/month and then scale as you have the plan currently structured, I believe that it would help adoption for Prisma Cloud. If I invest my time in building out and orchestrating the various pieces of my infrastructure, I am less likely to adopt a more expensive managed solution later. Especially when it is only managing a piece of my overall infrastructure needs.
As a bit of perspective…I built out my current Django ‘serverless’ infrastructure on AWS, using free tier services and pay-as-you-consume services. The stack includes Route 53, API Gateway, Lambda, RDS, SNS, S3, and EC2, all within a NAT gated VPC. I can run my whole stack at the same scale as the Prisma Cloud private plan for much less than $45/month. Yes it took more work on my part, but I now have most of it automated and it is easy to manage.