customer-relationship-ladderlisted
Install: claude install-skill deciqAI/knowledge-skills
# Customer Relationship Ladder
## Overview
Most B2B teams treat relationship deepening as an attitude problem — be friendlier, schedule more QBRs. The Ladder reframes it as structural: each rung requires a fundamentally different operating model, and you cannot skip rungs.
| Rung | Name | Signal |
|------|------|--------|
| 1 | Partial Fulfillment | Vendor meets stated need only; customer keeps alternatives warm |
| 2 | Basic Fulfillment | Vendor reliably delivers; customer stops shopping around |
| 3 | Deep Understanding | Vendor understands unstated needs; proactive insight delivery |
| 4 | Trusted Strategic Partner | Customer shares roadmap; joint planning occurs |
| 5 | Driver / Pioneer | Vendor shapes customer's strategy; co-creation; high switching cost |
**Cross-skill composition:** After `jobs-to-be-done` (surfaces jobs per rung). Before `demand-leadership` (Ladder = supply-side account; Demand Leadership = demand-side category). Alongside `principal-agent` to audit incentive alignment before Rung 4–5 joint planning.
## When to Use
**Trigger:** Key account renewal at risk; team claims "strategic partner" but can't name one unstated need addressed this quarter; new CSM needs rapid diagnostic; deal lost on relationship despite best product; board asks "how do we become indispensable to top accounts?"
**When NOT to use:** Transactional/high-volume (<$500 ACV); customer prefers arms-length; fewer than 10 customers (use `lean-startup` first).
---
## Coaching Novic