A Customer Value Platform is the integrated substrate where the customer relationship and the commerce that flows from it live whole — not split across a marketing tool, a CRM, a service desk, a billing system, and a customer success platform that none of them share.
A traditional CRM was built to record what salespeople do to leads. It optimized one function — sales activity tracking — and let the rest of the customer relationship live somewhere else.
Marketing automation handles outbound. Help desk handles tickets. Billing handles invoices. Customer success handles retention. Each function gets its own dashboard. The customer experiences five teams, five tools, five contexts.
A CVP is the substrate where the entire customer relationship lives — discovery, education, decision, commitment, delivery, value, advocacy, renewal. All on one record graph.
One Contact. One Company. One Order history. One Service relationship. One context every team sees. The customer experiences one team, one tool, one continuous relationship.
Any platform implementation can be measured against these five. Tools that violate them are not Customer Value Platforms — they are categories pretending to be one.
A CVP is organized around the customer relationship — not around marketing, sales, and service as separate organisms. One record per company, one history per contact, one source of truth per relationship. The Three-Org Model is the org-chart version of the same principle.
Native objects, native properties, native automations — exhausted first. Custom objects only when no native object can carry the entity. This is what makes a CVP operable by the team that runs it, not by the specialist that built it.
Orders are the revenue source of truth — not Deals. Invoices, Payments, Subscriptions are native, not bolt-ons. The financial truth and the relationship truth live in the same substrate. Pax reads from Orders. Sage reads from Contacts. Same record, different vantage.
A CVP exposes its data graph to AI agents without per-integration plumbing. Agents read from the canonical record, write through governed gateways, and the team supervises the work. The platform is the substrate every named agent operates on.
No two parallel systems claiming to be the customer record. No "marketing CRM" + "sales CRM" + "service CRM." No "ERP for finance, HubSpot for relationships, Notion for context, Slack for memory." One platform, four unified views (UCV, URV, UBC, UTE), one team that operates them.
The team uses HubSpot as its CVP. Not because HubSpot is the only platform in the category — but because, configured the way the canon prescribes, it carries the whole relationship without the team needing to operate ERP interfaces, integration consoles, or specialist tools that fragment what the customer experiences.
Across every Value-First Team client portal — and our own VF Team portal — there are only three custom objects: Deliverable, Interest, and Investment. Everything else is native HubSpot.
This isn't austerity. It's the configuration-over-customization principle at work: every custom object is a future migration tax, a future training tax, and a future "the consultant has to do it" tax. Native objects belong to the platform. Custom objects belong to whoever invented them.
| Object | ID | Role in the CVP |
|---|---|---|
| Contact | 0-1 | Every person in your ecosystem |
| Company | 0-2 | Every organization you serve |
| Deal | 0-3 | Sales process (NOT revenue truth) |
| Quote | 0-14 | Formal proposals with terms |
| Order | 0-123 | Revenue source of truth |
| Invoice | 0-53 | Billing — value delivered, payment requested |
| Payment | 0-101 | Cash flow — transaction completed |
| Subscription | 0-69 | Recurring revenue relationships |
| Service | 0-162 | Active value delivery |
| Project | 0-970 | Transformation work with phases and tasks |
| Ticket | 0-5 | Reactive support and service requests |
| Appointment | 0-421 | Scheduled time together |
| Course | 0-410 | Structured learning content |
| Listing | 0-420 | Universal content container |
Deals track the sales process — they end at commitment. Orders track revenue reality — they begin at commitment. Pax reads from Orders. Tally reconciles against Orders. The Finance Org never asks "is this Deal real?" — it asks "did this Order activate?"
Active value delivery lives in Service records. Transformation work with phases and tasks lives in Project records. Tickets stay scoped to what they are: reactive support. The portal each client sees is built on this graph.
How the team implements a CVP for a client — tiers, timelines, scope.
The org chart a CVP enables — Customer, Operations, Finance on one record.
UCV, URV, UBC, UTE — what each org actually sees on the CVP.
We run the framework. The framework belongs to anyone who wants to learn it.
Visit the protocol homeCourses, playbooks, interactive tools, and data model examples. Everything you need to transform your CRM.
Your donation helps us provide free resources and office hours to the community