1.5 KiB
1.5 KiB
- VCF #call
- Confliuence https://hpe.atlassian.net/wiki/x/ygK_0Q
- AHA https://hpepm.aha.io/epics/HCPC0202-E-190
- DONE followup with DaveH on PCE need completed:: 06-11-2025
- DONE check with Jennie on verisons completed:: 06-09-2025 SCHEDULED: <2025-06-11 Wed>
- CloudOps
- DONE find out when hard attach coming completed:: 06-11-2025
- DONE confirm when PCBE will incl. morpheus/VME licenses completed:: 06-06-2025
- Thoughts on SKU vs Commited Spend
- As mentioned on the call I think it makes more sense to use some sort of committed spend model over a bundled SKU.
- The more we explore the SKU model, we more we run into edge cases that require complex workarounds to make them work (e.g. if user already has licenses for product X, then discount that item to 100% ). This only gets worse as we look at upgrade/renewals etc.
- My proposal would be to do a 'commit spend model' (e.g. spend x over y to get the bundle discount) where current spend could be taken into account.
- Scenario 1 - new customer: order 150k of licenses (in any combo) of the 3 products. This gets customer the bundle discount, as long as their spend over 12 months is say $100k at the discoutned rate.
- Scenario 2 - existing customer: Cust already has 50K of OpsRamp (pro-rated by year) and needs the rest of the bundle. The 50k counts towards their spend and they get a discount on the other 2 products.
