One letter apart. Two different layers.

The boundary

CVP is what you operate on. VCP is what you operate by.

A team using HubSpot — a CVP — without VCP has the platform but no operating discipline. They will configure the platform around industrial-age defaults because that is what the foundation models in their AI tooling are trained to produce, and that is what the historical training data of the platform itself suggests.

A team committed to VCP without a CVP has the operating discipline but no machine-executable substrate. They can teach the method to humans, but the AI systems they deploy will default to the vocabulary VCP rejects, and the gap between the team's language and the system's language will widen with every release.

VCP plus a configured CVP is the operating arrangement. The CVP is the substrate where VCP runs. Other substrates are possible — the protocol is platform-agnostic by design — but HubSpot is the canonical implementing CVP for the Value-First method because it has the native objects, the configuration depth, and the public accessibility to make the configuration-over-customization principle operable.

Why the naming hurts

The acronyms differ by a single letter and live in adjacent conceptual space. This is unfortunate and intentional: both names come from the same lineage. CVP names the platform category that VCP runs on top of. They were never meant to be heard in isolation, and they are not competing for the same slot.

When you need to be exact, say it long: Customer Value Platform for the substrate, Value Creation Protocol for the methodology. When you are working inside the team, context disambiguates — but when you are introducing either concept to someone for the first time, name the layer first and the acronym second.

Related canon

• HubSpot as CVP — the canonical implementing substrate
• VCP positioning paper — where VCP sits in the protocol stack
• Encoding stack — what makes VCP machine-parseable
• Glossary — full term index