vSAN is inside VCF. The question is on what terms.

vSAN is bundled inside VCF, but the way it is bundled is not the same as it was twelve months ago. Allocation rules, capacity bands, and the treatment of stretched clusters have each moved at least once since the acquisition closed. Quotes still arrive priced as if none of that changed. The desk's first job on a vSAN review is to read the current paper, not the paper the buyer signed last cycle.

The economics turn on three questions. How many cores actually need vSAN at the tier the bundle assumes. Whether the buyer is being charged for capacity bands they do not use. And whether the mid term protection clause lets the buyer adjust if capacity drops, or only if it rises. The answer to the third question is currently asymmetric in the seller's favour on most renewals we see.

The work is a mix of deployment reconciliation, contract reading, and structure rewriting. Reconciliation usually pulls between eight and twenty two percent out of the opening quote. The contract reading finds the asymmetric clauses that protect the seller against consumption changes that go in only one direction. The rewrite makes the protection symmetric, or compensates with a price band that does the same job.

The case below shows what this looks like on a mid market renewal. The field notes describe the inclusion trap most VCF buyers do not see until the second year of the contract.