── ── Startups
Customer Relationship Ladder
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.
How it works
3D-T Framework: Diagnose → Design → Deploy, anchored by Trust
Step 1 — Diagnose: Collect across 4 dimensions: information flow, vendor substitutability, problem source, meeting cadence. Stop-rule: Can't answer "what specific unstated need did we address this quarter?" → capped at Rung 2.
Step 2 — Design: 1→2: Reliability (operational). 2→3: Embedded knowledge — assign someone to learn their business from inside. 3→4: Shared stakes — joint initiative, both parties commit resources. 4→5: Co-creation via proprietary data, methodology, or talent.
When to use it
- a key account renewal is at risk and the team can't explain why the customer values them
- someone asks 'how do we become a strategic partner?'
- a CSM needs to know where a relationship actually stands
- the team claims to be strategic but has no proactive insight delivery this quarter
- a deal was lost on relationship despite having the best product
When not to use it
the customer base is transactional high-volume with ACV under $500 (Rung 3–5 is structurally impossible); the customer explicitly prefers arms-length vendor relationships.
Worked example
IBM's Transformation from Hardware Vendor to Strategic Partner (1993–2001)
Source: Lou Gerstner, Who Says Elephants Can't Dance? (2002, HarperBusiness); IBM Annual Reports 1992–2001, available at https://www.ibm.com/annualreport/
Install this skill (free, MIT)
npx skills add deciqAI/knowledge-skills