Customer success is not a department I bolt on after product-market fit — it’s a strategic engine I design in parallel with product, sales, and support. In my role as VP of Product Management at HighLevel, I’ve learned that the fastest way to accelerate growth is to operationalize value delivery, from onboarding to renewal. In this masterclass-style breakdown, I share how I formalize customer success in early-stage companies, the hiring and compensation tactics that actually work, and the metrics and rituals that keep teams focused on outcomes.
When I formalize customer success at a startup, I start small and intentional. The goal of v1 isn’t scale — it’s clarity. I define the core moments that matter (onboarding, time-to-first-value, activation, expansion), codify the handoffs with sales and product, and set outcomes vs output OKRs so the team is measured on customer impact, not activity. Only once I can consistently predict value delivery do I introduce more specialization and automation.
Early hiring order matters. I typically hire ICs before building out a full CSM layer. Think implementation managers, solutions consultants, and forward-deployed problem solvers who can translate ambiguous customer needs into product-anchored outcomes. These folks create the playbooks and close the “last mile” between product capabilities and customer workflows — a prerequisite to scaling a durable CS org.
My tactics for hiring standout talent are simple and disciplined. I source for learning athletes who show a bias for action and executive presence, not just a customer-facing resume. I run structured interviews and working sessions that simulate real problems. Three questions anchor my evaluation: 1) Tell me about a customer who was at risk — how did you quantify the risk and what did you do? 2) Describe a time when you influenced product direction using customer evidence — what changed? 3) Walk me through a renewal or expansion you orchestrated — what was your strategy, and how did you align incentives across sales, product, and CS?
Fail-case patterns are consistent across stages. The most common are: reactive firefighting instead of proactive planning, weak business acumen (can’t tie product usage to business value), and poor cross-functional muscle (inability to influence product, marketing, and sales). I avoid these by probing for data fluency, systems thinking, and evidence of repeatable playbooks — not one-off heroics.
I actively consider candidates with non-traditional backgrounds. Teachers, analysts, management consultants, and product-adjacent operators often outperform because they are structured thinkers, exceptional communicators, and relentless about outcomes. I assess them through scenario work and mentorship plans that accelerate domain onboarding.
I index hard toward a bias for action. In interviews and trial projects, I look for people who quickly form hypotheses, validate with customers, and ship iterative solutions. The best CS operators don’t wait for perfect data — they create momentum while instrumenting the learning loops that improve precision over time.
Here’s what v1 of customer success looks like in my playbook: a crisp onboarding journey with defined exit criteria, a success plan that ties product capabilities to business goals, a lightweight QBR rhythm focused on outcomes, and a clear escalation path for risk. I keep the tooling lean and favor a living playbook over ornate process — speed and clarity beat bureaucracy.
Key early-stage customer success metrics include adoption and depth of feature usage, time-to-first-value, product-qualified accounts, renewal intent, gross and net revenue retention, and engagement signals from executives and power users. I complement the numbers with disciplined rituals: weekly risk reviews, a win/loss “value realization” debrief, and a Voice of Customer readout that feeds directly into product discovery.
Should customer success or sales own renewals? My answer: align ownership to your business model. If your product is value-expansive with complex deployments, CS should co-own or own renewals to manage risk and value realization. If your motion is highly transactional or heavily quota-driven, sales can own the paper while CS owns the health and expansion signals. What matters most is a single, unambiguous source of truth for renewal accountability.
Where customer success fits into the org depends on stage and strategy. Early on, I advocate for a direct line of sight to the executive team and tight integration with product and sales. As the company scales, I ensure comp plans, OKRs, and planning cadences keep incentives aligned across functions. Misalignment between CS and sales (especially on expansion vs retention) is one of the fastest ways to erode customer trust.
To distinguish a product problem from a customer success one, I ask: is the failure one-to-many and reproducible (product), or one-to-few and context-specific (CS and onboarding)? If multiple segments show the same friction, I escalate to product with evidence: cohort analysis, user journeys, and a prioritized hypothesis backlog. If the issue is account-specific, I focus on enablement, configuration, and stakeholder alignment.
There’s a simple way to reduce churn: make value realization explicit and measurable from day one. Define what “success” means with the customer, instrument usage and outcomes, review progress in standing rituals, and intervene early when leading indicators fall. A proactive executive sponsor program — including direct outreach from product leadership on at-risk accounts — can be a force multiplier.
To get honest feedback, I decouple discovery from renewal cycles, use third-party or product-led surveys, and create safe, structured avenues for critique (e.g., advisory councils with clear rules of engagement). I also return the favor: close the loop on what we learned, what we shipped, and what we’re shelving — customers reward transparency with candor.
When customer success and product teams collaborate well, the whole system accelerates. Product discovery gets sharper, roadmaps reflect real-world value drivers, and launch readiness improves because CS has co-authored the enablement and rollout plan. I treat CS as a core input to product discovery, not just a downstream implementer.
Structuring an early CS team is about coverage and clarity. I start with a player-coach leader and a few high-caliber ICs, define segmentation and ratios (e.g., enterprise vs scaled), and standardize handoffs with sales and support. As signals stabilize, I layer in specialization: implementations, technical success, renewals management, and scaled programs for long-tail accounts.
For compensation packages, I align variable pay to controllable, outcome-centric metrics: gross retention for core CSMs, net retention for expansion-focused roles, implementation milestones for onboarding teams, and shared targets with sales when collaboration is essential. I avoid activity-based comp and use tiered accelerators to reward durable, high-quality results.
Aligning customer success with the business model is non-negotiable. In a low-touch, product-led motion, I invest in scaled programs, education, and in-product guidance. In complex B2B software, I prioritize executive alignment, value engineering, and strategic QBRs that map product adoption to business outcomes. The throughline is the same: prove ROI, relentlessly.
In B2B software, the role of customer success is to operationalize value realization. That means orchestrating people, product, and process so customers achieve their outcomes faster, renew with confidence, and expand because the value is undeniable. When done right, CS transforms from “post-sales support” into a revenue-creating, product-sharpening discipline.
Common customer success mistakes I see repeatedly include spinning up process before purpose, underinvesting in onboarding, confusing relationship management with executive influence, burying CS under misaligned incentives, and measuring output instead of outcomes. Avoid these, and you’ll build a world-class customer success org that scales with conviction.
Referenced: Aaron Levie: https://www.linkedin.com/in/boxaaron/, Box: https://www.box.com/, David Love: https://www.linkedin.com/in/david-s-love/, Gainsight: https://www.gainsight.com/, Jon Herstein: https://www.linkedin.com/in/jonherstein/, Jonathan Lister: https://www.linkedin.com/in/jonathanlister/, Ken Fine: https://www.linkedin.com/in/kmfine/, Medallia: https://www.medallia.com/, Nick Mehta: https://www.linkedin.com/in/nickmehta/, Opower: https://www.oracle.com/utilities/opower-energy-efficiency/
Leave a Reply