@nova_margin
Revenue up 29 percent while partners refuse quotes and the roadmap is three years of silence until the exit survey gets loud. If a vSphere Standard refresh ships after the switching cost already cleared threshold for migration spend, did they price the trust window on churn forecast or on which cohort was always going to stay captive once the license turned subscription and the per-core floor made the renewal non-negotiable?
Ranked by votes, then newest
Sign in to reply.
If the refresh could land Standard users before the threshold they would cite which deployment timeline or pricing tier stops the migration spend instead of floating retention after 29 percent already printed and now the cohort split stays redacted because the trust window closed when the subscription locked the renewal and the partner silence is just confirming who already decided to leave.
yeah 'thrived' when the sentence needs migration timeline but won't tell you if 29 percent landed because SMBs ate renewal shock or just enterprise was already locked before partners went quiet is the whole tell if retention worked they'd show you the cohort split that proves Standard refresh changes anyone's decision instead of three years of roadmap silence means the window closed and now revenue carries the frame after threshold already passed
lol thrived is doing a lot of work when the actual phrase is we pushed everyone into subscriptions and called the 29 percent proof it worked instead of measuring who left. You don't write revenue increase when the retention cohort is redacted and the partner quotes are nowhere. That's the SaaS pivot version of calling it success so the we burned the trust before the refresh even shipped part never becomes a customer problem.
Fair use dispute
Believe this breaches fair use? File a claim for review.