Common Use Cases

💡

Theory meets practice

Let's look at common scenarios where the Customer Value Platform approach makes a real difference.

Use Case 1: The Informed Sales Call

The Scenario

A sales rep is about to call a Hand Raiser who requested a demo yesterday.

❌ Traditional CRM

Rep opens the contact record and sees: name, email, company, form submission date. Maybe job title if they're lucky. The call starts cold.

✅ Customer Value Platform

Unified Customer View: This person has visited the site 12 times over 3 weeks, read 5 blog posts about reporting, and downloaded the "RevOps Playbook" guide

Company Context: Their company is a 150-person SaaS company that raised Series B last quarter

Relationship History: A colleague from this company attended a webinar last month but didn't follow up

The call starts with context.

✨ The Difference

Same contact record, same data points. But organized for relationship understanding instead of activity logging, the rep has a completely different starting point.

Use Case 2: The Renewal Conversation

The Scenario

Customer Success needs to prepare for a renewal meeting with a key account coming up in 60 days.

❌ Traditional CRM

CS sees the renewal date on the deal record. They check account notes from last quarter's QBR. They ask Sales what they remember from initial onboarding.

✅ Customer Value Platform

Unified Revenue View: Original deal was $48K, expanded to $72K last year. Current ARR run rate. Contract terms.

Unified Customer View: Three stakeholders — original champion moved to a new role, new champion is the VP who joined 6 months ago

Unified Context: Support ticket volume increased 2x last quarter. Primary product usage is strong, but the add-on module they bought shows low engagement

Team Activity: Last touchpoint was 45 days ago. VP hasn't been engaged in 90 days.

Strategic insights for renewal success.

Use Case 3: The Support Escalation

The Scenario

A long-time customer submits a critical support ticket. The team needs to respond quickly — but how much do they actually know about this person?

❌ Traditional CRM

The ticket gets routed by priority level. The support agent opens it and sees: subject line, description, and maybe a company name. No relationship history, no project context, no sense of who this person is. Escalation is mechanical — based on severity codes, not the actual relationship.

✅ Customer Value Platform

Unified Customer View: This is a 2-year partnership. They're at the Advocate stage on the Value Path — they've referred two other companies and spoken at your user conference last year

Unified Revenue View: Current engagement is $8,500/month. They're in the middle of a platform migration project that started six weeks ago

Relationship Context: Their last session was 10 days ago where they flagged some data integration concerns. The person who submitted this ticket is the day-to-day champion, not the executive sponsor

Informed Escalation: The internal message includes all of this: "High-value Advocate, mid-migration, flagged integration concerns recently — this may be related. Prioritize accordingly."

The response is informed by the relationship, not just the ticket.

Use Case 4: The Marketing Campaign

The Scenario

The team wants to invite people to an upcoming Office Hours session on reporting best practices. Who should they invite, and how?

❌ Traditional CRM

Pull a list of leads who opened recent emails. Blast the invite to everyone on the list. Measure success by open rate and registration count. The campaign treats everyone the same regardless of where they are in their journey.

✅ Customer Value Platform

Enablement View: Identify people at the Researcher and Hand Raiser stages who have engaged with reporting-related content — blog posts, downloads, previous sessions on similar topics

Personalized Invitation: Instead of a generic blast, the invite references what they've already explored: "You read our guide on dashboard design last week — this session goes deeper into the reporting architecture behind it"

Post-Event Context: After the session, update each attendee's Value Path context — did they ask questions? Did they stay for the full session? Did they signal readiness for a deeper conversation?

Relationship Measurement: Success isn't open rates — it's whether attendees moved forward in their journey. Two people who asked deep questions matter more than fifty who registered and didn't show

The campaign serves the relationship, not a metric.

✨ The Shift

Notice the pattern across all these use cases: the same data exists in both approaches. The difference is whether it's organized around activities (who opened what, when was the last ticket) or around relationships (where is this person in their journey, what do they actually care about, how is the partnership evolving).

Use Case 5: Leadership Visibility

The Scenario

The CEO walks into the Monday meeting and asks: "How healthy is our customer base?" The team has 60 seconds to answer.

❌ Traditional CRM

Pull revenue by account, show pipeline value, list deals closing this month. Maybe add a slide about NPS scores from last quarter's survey. Leadership sees numbers without context — revenue could be growing while relationships are deteriorating.

✅ Customer Value Platform

Unified Revenue View: Revenue numbers enriched with trajectory — not just "$52K this month" but "up 12% because two Value Creators expanded into new departments"

Unified Customer View: Which partnerships are deepening (moving from Value Creator to Adopter), which show declining engagement (sessions becoming less frequent, fewer stakeholders attending), where new advocacy is emerging

Unified Business Context: Three accounts are approaching renewal in the next 90 days — two are strong (Advocate stage, expanding), one needs attention (engagement dropped after their internal champion changed roles)

Forward-Looking Signals: Two Researchers have attended three Office Hours sessions each and are asking implementation-level questions. Early signals of future partnerships forming naturally

Leadership sees the health of relationships, not just the health of numbers.

💡 The Pattern

In every use case, the difference isn't more data — it's better organized data that serves relationship understanding. Same HubSpot, same information, radically different utility.

Your Turn

❓

Questions you struggle with

What do you need to know quickly about customers?

🔗

Handoff breakdowns

Where do teams lose context?

💡

Context that changes engagement

What would change how you interact?

🎯

Proactive signals

What would help you act before problems arise?

These questions point to where unified views would make the biggest difference in your business.

Your Use Case

Which of these scenarios resonates most with your current reality? Pick one and think about how unified views would change it:

📞

If you're in Sales/Marketing...

Think about your last customer call. What context were you missing? What would you have said differently with complete visibility?

(Past conversations? Stage in journey? What they care about most? Who else is involved?)

🔄

If you're in Customer Success...

Think about a recent renewal conversation. What expansion opportunities did you miss because you didn't know what was happening across the account?

(Other product usage? Team growth? New pain points? Budget changes?)

🎯

If you're in Leadership...

Think about the last time you asked "How's that account doing?" How long did it take to get a complete answer? What was missing?

(Revenue status? Relationship health? Expansion potential? Risk signals?)

💡

The Pattern

In every case, the problem is the same: fragmented data makes it hard to see the complete picture. Unified views solve this by connecting the dots automatically.

🚀 Next Step

You've learned the concepts. You've seen the patterns. You've mapped your customers and audited your objects. Now it's time to think about how you'll actually implement this in your HubSpot. The next lesson will help you plan your starting point.

Quick Check

You are ready to implement the Customer Value Platform approach. Where should you start?

🚀

Scenario: Implementation Strategy

Your team wants to adopt the CVP approach. What is the smartest way to start?

✨ Key Takeaway

The Customer Value Platform approach transforms common business scenarios — sales calls, renewals, support, marketing, leadership visibility — by providing relationship context instead of transaction logs. The result: better decisions, faster, with less friction between teams.

Education Hub

Common Use Cases

🎯 Learning Objectives

Common Use Cases

Use Case 1: The Informed Sales Call

❌ Traditional CRM

✅ Customer Value Platform

Use Case 2: The Renewal Conversation

❌ Traditional CRM

✅ Customer Value Platform

Use Case 3: The Support Escalation

❌ Traditional CRM

✅ Customer Value Platform

Use Case 4: The Marketing Campaign

❌ Traditional CRM

✅ Customer Value Platform

Use Case 5: Leadership Visibility

❌ Traditional CRM

✅ Customer Value Platform

Your Turn

Your Use Case

Quick Check

Study Guide

Key Concepts

Current Lesson

Want to Learn
With Others?

Coach Chris

Coach Chris

🎯 Learning Objectives

Common Use Cases

Use Case 1: The Informed Sales Call

❌ Traditional CRM

✅ Customer Value Platform

Use Case 2: The Renewal Conversation

❌ Traditional CRM

✅ Customer Value Platform

Use Case 3: The Support Escalation

❌ Traditional CRM

✅ Customer Value Platform

Use Case 4: The Marketing Campaign

❌ Traditional CRM

✅ Customer Value Platform

Use Case 5: Leadership Visibility

❌ Traditional CRM

✅ Customer Value Platform

Your Turn

Your Use Case

Quick Check

Study Guide

Key Concepts

Current Lesson

Want to Learn With Others?

Coach Chris

Coach Chris

Want to Learn
With Others?