Jump to section
TL;DR: A modern customer success tech stack has four layers: a CS platform for internal lifecycle operations (Gainsight, Planhat, ChurnZero), a customer-facing collaboration and onboarding layer for the work you do with the customer (Valuecase), a product analytics layer for measuring activation (Mixpanel, PostHog), and a CRM as the source of truth (HubSpot, Salesforce). These solve different jobs and most teams run several together. The common confusion – treating a customer onboarding platform as a replacement for a CS platform – gets the architecture wrong: the onboarding layer sits alongside Gainsight or Planhat, not instead of it.
Ask ten customer success leaders what's in their stack and you'll get ten different lists – but underneath, the same four jobs keep showing up. The confusion isn't usually about which vendor; it's about which layer a tool belongs to, and which layers a single tool can credibly cover. This guide maps the modern CS stack by job to be done, names the tools in each layer, and shows where the customer-facing onboarding layer fits relative to the CS platforms it's so often confused with.
The four layers of a modern CS stack
Most CS stacks resolve into four layers, each answering a different question:
- CS platform – How does my team run the customer lifecycle internally? Health scores, renewal forecasting, playbooks, CS operations.
- Customer-facing collaboration and onboarding layer – Where do my team and the customer actually do the work together? The shared, branded space for onboarding plans, tasks, forms, and content.
- Product analytics – Is the product actually being adopted? Activation events, funnels, feature usage.
- CRM – What's the single source of truth for the account? The system of record everything else syncs to.
The key insight: these are complements, not substitutes. A health score (CS platform) tells you an account is slipping. A shared onboarding space (collaboration layer) is where you fix it with the customer. An activation funnel (product analytics) tells you whether it worked. They answer different questions, so mature teams run more than one.
Layer 1: CS platforms (Gainsight, Planhat, ChurnZero)
Customer success platforms are built for teams managing the entire customer lifecycle, not just the first 90 days. Their home turf is internal CS operations: health scoring, renewal forecasting, playbook automation, NPS, and journey orchestration. They are where a CS leader runs the team and watches the book of business.
The three that anchor the category sit at different weights. ChurnZero is the leaner option – strong on the internal CS workflow of health scores, automated playbooks, and renewal forecasting, built for teams managing the full lifecycle without enterprise sprawl. Planhat is more data-heavy, built around a single customer 360°-view, and fits mid-market to enterprise teams where the data layer across the lifecycle matters most. Gainsight is the enterprise heavyweight – customer 360, health scoring, journey orchestration, and a CS Ops suite at scale – best for large organisations running dozens of CSMs and thousands of accounts.
What all three share is a thinner customer-facing surface. They're designed for your team to operate the lifecycle, not to be the polished space the customer logs into during onboarding. That's not a flaw; it's the layer boundary. Which is exactly why the next layer exists.
Layer 2: the customer-facing collaboration and onboarding layer (Valuecase)
This is the layer that runs the work you do with the customer – most visibly during onboarding, but also through expansion and renewal moments. Where a CS platform is an internal cockpit, the collaboration layer is the shared room: a branded space the customer can open from a link with no login, holding the onboarding plan, tasks, forms, resources, video, and the people involved.
Valuecase is built for this layer. Each customer gets a branded Space combining the plan, tasks, auto-saving forms with conditional logic, content, and chat in one shareable link, while your team gets a dashboard across every active onboarding with Kanban, Gantt, and custom saved views. Spaces personalize per customer, including multi-language support. An embedded AI agent drafts content, updates plans, answers questions on customer data, and surfaces risk across the portfolio – and MCP support lets external agents like Claude or ChatGPT act on your Valuecase data. It integrates deeply with HubSpot (including custom objects) and Salesforce, is ISO 27001 certified with EU data hosting, and starts at €59/month with no seat minimums.
The important architectural point: this layer sits alongside your CS platform, not in place of it. Gainsight tells you an onboarding is at risk; Valuecase is where you and the customer actually move it forward. Many teams sync the two, so the collaborative work in the space updates the health picture in the CS platform. If you're still placing the categories, what is customer onboarding software and how to choose customer onboarding software draw the boundaries in detail.
Layer 3: product analytics (Mixpanel, PostHog)
Strictly, product analytics tools aren't CS tools – they're the measurement layer behind everything else. If you run any kind of data-driven success motion, this is where the question "is our onboarding actually working?" gets answered.
Mixpanel is the go-to for tracking activation events, funnels, cohort retention, and feature usage – teams use it to define what "activated" means and measure how well onboarding drives customers there. PostHog is the open-source, self-hostable alternative that bundles analytics with session replay, feature flags, and experimentation, which suits engineering-led teams that want product data under their own control. Neither is an onboarding or CS tool on its own; both are the instrumentation that tells you whether the other layers are working.
Layer 4: the CRM as source of truth (HubSpot, Salesforce)
Underneath all of it sits the CRM. HubSpot or Salesforce is usually the system of record for the account, and the depth of integration between your CRM and the other three layers determines how much manual re-entry your team lives with. A collaboration layer that syncs two-way with the CRM – custom objects, deal stages, property updates – means the handoff from sales into onboarding, and from onboarding into renewal, carries context instead of dropping it.
How the layers connect
Picture the stack as a loop rather than a tower. The CRM holds the account record. When a deal closes, it triggers a space in the collaboration layer where the customer onboards. The activity in that space – tasks completed, forms submitted, engagement – flows back to the CRM and feeds health scores in the CS platform. Product analytics measures whether the customer reached activation. The CS platform watches the whole book and fires a playbook when an account slips, which sends the CSM back into the collaboration layer to act.
No single tool owns that whole loop, and the teams that try to force one to usually end up with a cockpit that customers hate logging into, or a beautiful customer space their CS leaders can't report on. The cleaner architecture keeps each layer doing its job and wires them together. For the broader market view across categories, the 2026 platform comparison maps the named tools in each.
This loop is also where the most useful AI lives in 2026 – not as a chatbot bolted onto one layer, but as agents that move between them: scoring onboarding risk, generating weekly customer status reports, and chasing stalled accounts with context. Valuecase's library of AI agent use cases shows what that looks like in practice.
FAQ
What's in a customer success tech stack?
A modern CS stack has four layers: a CS platform for internal lifecycle operations (Gainsight, Planhat, ChurnZero), a customer-facing collaboration and onboarding layer for the work done with the customer (Valuecase), a product analytics layer for measuring activation (Mixpanel, PostHog), and a CRM as the source of truth (HubSpot, Salesforce). They solve different jobs, so most teams run several together rather than expecting one tool to cover everything.
Does Valuecase replace Gainsight?
No – they sit in different layers and work best together. Gainsight is a CS platform for internal operations: health scoring, renewal forecasting, and playbooks across the whole book of business. Valuecase is the customer-facing collaboration and onboarding layer – the branded space where your team and the customer actually do the work. A CS platform tells you an account is at risk; the onboarding layer is where you act on it. Teams commonly run both and sync them.
Where does onboarding sit in the CS stack?
Onboarding lives in the customer-facing collaboration layer, not inside the CS platform. CS platforms can track that onboarding is happening and feed it into health scores, but the actual collaborative work – the shared plan, intake forms, content, and stakeholder coordination – happens in a purpose-built onboarding space that the customer can open without a login. That space then syncs activity back to the CRM and CS platform.
Want to see where the collaboration layer fits in your stack? Book a demo of Valuecase or start a free trial.
