The Operator's Manual for Customer Success in HubSpot
A practitioner's guide to building your CS workspace from the ground up. No fluff, no generic best practices. Just the decisions you need to make and why they matter.
Download the Manual.jpg?width=860&t=1773508206756)
A practitioner's guide to building your CS workspace from the ground up. No fluff, no generic best practices. Just the decisions you need to make and why they matter.
Download the Manual
Service Hub gives you the tools. It doesn't tell you how to structure your customer success operation.
Their documentation shows you how features work. It doesn't show you how to build an object model, configure your workflows, or structure your reporting so your team can actually do their jobs.
You're left making critical architecture decisions without knowing which ones you'll regret six months in. This manual gives you the framework to build it right the first time.
The workspace architecture in this manual is organized around the four pillars of customer success intelligence: Realization (are customers getting value), Relationship (do we have the right engagement cadence), Renewal (where's the revenue risk), and Risk (what signals matter). Every property, workflow, and view serves one of these four outcomes. If it doesn't help you understand realization, strengthen relationships, protect renewals, or surface risk, it doesn't belong in your workspace.
The foundational architecture decisions that determine whether your workspace scales or becomes a data swamp. Where renewals live, how CSMs track activity, what properties actually matter.
Which processes to automate first and which to leave manual. How to build workflows that support your team instead of creating noise and false positives.
The metrics that matter and how to surface them. Building dashboards your CSMs will actually use instead of vanity metrics that look good in screenshots.
How to set up views, filters, and task queues so your team can work efficiently. The difference between a workspace that helps and one that gets in the way.
When to integrate and when to consolidate. How to evaluate whether you need that data sync or if you're just creating another system to maintain.
If you're coming from Gainsight, ChurnZero, Salesforce, or spreadsheets, here's what to move, what to leave behind, and how to sequence the transition.