PMF
Wrong customers, wrong value proposition, or wrong positioning. The fix is usually upstream of CS — ICP, pricing, packaging. No amount of playbook work will save an account that shouldn't have been sold.
CS Strategy
The system that makes NRR compound.
These are the frameworks I bring into every engagement. They aren't theory — they're the load-bearing mental models I've used to build CS orgs from scratch, scale teams, and get NRR moving in the right direction.
Framework 01
The CS formula.
Understand what customers value. Ensure they get it from your product. Profit. Every CS investment should ladder back to this equation. Credit: Gainsight.
Framework 02
Stage-appropriate strategy.
The CS organization you need at Series A is not the one you need at Series B+. Building ahead of your stage wastes runway; building behind it costs renewals.
| Stage | Focus | What to prove |
|---|---|---|
| Pre-seed → Series A | Product-market fit | High gross retention |
| Series A → Series B | Compelling GTM | High net retention |
| Series B+ | CS model for scale | High margins |
Framework 03 Root cause 01 Root cause 02
The net revenue diagnostic — two root causes.
When net revenue targets slip, there are only two root causes. The interventions for each are completely different, which is why starting with the diagnostic matters more than jumping to a solution.
GTM execution
Product is right, but people, processes, and tools aren't set up to deliver outcomes at scale. This is the space where CS Science operates — where the returns on a system-level fix compound for years.
Framework 04
CX maturity — seven components, three levels.
A snapshot of where your customer experience currently lives, and where a system-level investment would move the needle most.
| Component | Low | Medium | High |
|---|---|---|---|
| Journey, ICP & Segmentation | One-size-fits-all | Segment-aware playbooks | Persona × lifecycle journeys |
| Handoff, Kickoff & Goal Setting | Informal handoff | Standard kickoff deck | Documented success criteria per segment |
| Implementation & Onboarding | Ad-hoc | Defined milestones | Time-to-Value measured & optimized |
| Customer Education | Tickets & tribal knowledge | Content library | Role-based learning paths |
| Customer Support | Reactive | SLAs + CSAT | Proactive + product feedback loop |
| Customer Success | Firefighting | CSM playbooks | Outcome-based health & interventions |
| Renewal & Upsell | Event | Scheduled motion | Continuous value + PROPEL expansion |
Framework 05
The three pillars.
CS isn't one team — it's three coordinated functions. When they optimize independently, the customer feels the seam. Churn lives in the seam.
Pillar 01 · Commercial
CSMs & AMs
Own NRR and operating margin. Run the renewal and expansion motion; close with PROPEL when the usage signal is there.
Pillar 02 · Technical
Support & Services
Own customer outcomes and value delivered. The trust-building function — support has two jobs: solve, and feed back to product.
Pillar 03 · Consistent CX
Sales, Solutions & Implementation
Own journey quality. The handoff from pre-sale to post-sale is where most CS programs quietly fail. Remove the seam.
Next step
Scope an engagement → Want the full diagnostic applied to your org?
A CS Foundations engagement runs 3–4 weeks and ends with a working operating plan your team can execute.