stephenrogan/multi-threading-playbook

Multi-Threading Playbook

A structured approach to expanding relationships beyond your single point of contact. Single-threaded accounts are the highest-risk accounts in any portfolio -- not because the account is unhealthy, but because the entire relationship depends on one person's continued presence, engagement, and advocacy.

How to Use

Provide:

• Account name and context (ARR, tenure, segment)
• Current contacts: who you know, their roles, your relationship strength with each
• Who you think you should know but do not (from the org chart, from conversations, from intuition)
• What has prevented multi-threading so far (champion is a gatekeeper, you do not have a reason to engage others, you have not prioritised it)
• Your goal: what does the ideal stakeholder coverage look like for this account?

Why Multi-Threading Matters (The Risk Arithmetic)

Single-threaded accounts carry compound risk:

| Event | Impact on Single-Threaded Account | Impact on Multi-Threaded Account | |-------|----------------------------------|--------------------------------| | Champion leaves | Relationship drops to zero. No internal advocate. Renewal at immediate risk | Relationship weakened but surviving. Other contacts maintain continuity. Risk is elevated, not existential | | Champion goes on leave (3+ months) | Effectively the same as departure during the leave period. Decisions stall | Other contacts continue the partnership. Leave is a pause, not a crisis | | Champion gets promoted | May lose interest in your product as their scope expands. Or may gain the power to expand -- but you cannot influence which | Same upside with lower risk. Other contacts maintain day-to-day relationship | | Champion becomes a detractor | Your only advocate becomes your biggest obstacle. No counterbalance | Other contacts provide perspective. Detractor is one voice, not the only voice | | Budget review | Champion defends alone. If they are overruled, you have no backup | Multiple stakeholders defend the investment from different angles | | Competitive evaluation | Champion may or may not tell you. If they do not, you have no visibility | Multiple contacts increase the probability you hear about the evaluation early |

The rule: Any account where the loss of one person would put the relationship at risk is underinvested in multi-threading. The time to multi-thread is before the champion leaves, not after.

The Multi-Threading Framework

Step 1: Map What You Have

| Contact | Role | Relationship Strength | Last Touch | Primary Channel | Value They Get From You | |---------|------|---------------------|-----------|----------------|----------------------| | [name] | [title] | [Strong/Adequate/Weak] | [date] | [email/call/meeting] | [what they specifically gain from the relationship] |

Step 2: Identify Who You Need

For a well-threaded account, you need coverage in three dimensions:

Vertical coverage (levels):

• Executive sponsor (VP or C-level) -- provides air cover and strategic alignment
• Operational leader (Director/Manager) -- makes the day-to-day decisions about the product
• End user champions (1-2 power users) -- validate the product's value in daily workflows

Horizontal coverage (functions):

• The function that owns the product (your primary relationship)
• The function that funds the product (finance, if different from above)
• Adjacent functions that use or benefit from the product

Decision coverage:

• The person who decides to renew (may be different from your champion)
• The person who controls the budget (may be different from both)
• The person who influences the decision-maker (often the most important person you are not talking to)

Step 3: Prioritise Who to Develop

Not every gap has the same urgency. Prioritise by:

| Priority | Criteria | Why | |----------|----------|-----| | 1 | Economic buyer not engaged | The renewal decision will be made by someone you have not spoken to | | 2 | Only one active contact (single-threaded) | Any disruption to that contact puts the entire account at risk | | 3 | Executive sponsor not established | No air cover for the investment. Vulnerable to budget reallocation | | 4 | Adjacent function expressing interest | Organic expansion opportunity that deepens the account's dependency on the product | | 5 | New hire in a relevant role | Fresh relationship to build before they form opinions about existing vendors |

Step 4: Choose the Engagement Path

Each new contact requires a reason to connect and a path to get there:

| Path | How It Works | Best For | Risk | |------|-------------|---------|------| | Champion introduction | Your champion introduces you to the target contact | Lateral moves (same level, different function) | Low -- warm introduction. Dependent on champion's willingness and relationship with the target | | Value delivery | You deliver something useful to the target directly (a benchmark, a report, training) | Technical leads, end users, operations managers | Low-Medium -- you earn the relationship through value | | Executive-to-executive | Your leadership reaches out to their leadership | C-suite, VP level | Medium -- requires your exec's time and buy-in | | Event or meeting | You meet them at a QBR, on-site visit, user group, or conference | Anyone in the account who attends the event | Low -- natural context for meeting | | Content sharing | You share a relevant article, benchmark, or insight that is specific to their role | Anyone -- good door-opener | Low -- but may not generate a response. Better as a touchpoint than a relationship builder | | Support interaction | They contact support or you are involved in resolving their issue | Technical leads, end users who had a problem | Medium -- the interaction is reactive. You turn it into a proactive relationship |

Step 5: Build the Multi-Threading Plan

| Target Contact | Path | Reason to Connect | Proposed Approach | Timeline | Success Indicator | |---------------|------|-------------------|------------------|----------|------------------| | [name/role] | [path] | [why this person, why now] | [specific first action] | [this week / this month / this quarter] | [how you know the relationship is established] |

Step 6: Maintain the Threads

Multi-threading is not a one-time effort. New relationships need sustenance:

| Thread Maturity | Cadence | Purpose | |----------------|---------|---------| | New (first 3 touchpoints) | Monthly minimum | Establish the relationship. Provide value. Demonstrate reliability | | Established (3+ touchpoints, some rapport) | Quarterly minimum | Maintain the relationship. Share relevant updates. Ask how they are doing | | Strong (mutual trust, open communication) | As needed | The relationship is self-sustaining. Touch base when there is a reason |

Output Format

## Multi-Threading Strategy: [Account Name]

### Current Coverage
[Completed contact map]

### Coverage Gaps
- [Gap 1]: No economic buyer engaged. [Name/Role] controls the budget
- [Gap 2]: Single-threaded to [champion name]. No backup relationship
- [Gap 3]: No executive sponsor

### Multi-Threading Plan
| Target | Path | Approach | Timeline | Success Indicator |
|--------|------|---------|----------|------------------|
| [name] | Champion intro | Ask [champion] for introduction at next QBR | This month | First 1:1 conversation completed |
| [name] | Value delivery | Send peer benchmark report relevant to their role | This week | Response or follow-up call |
| [name] | Exec-to-exec | Request VP-to-VP outreach via CSM manager | This quarter | Meeting scheduled |

### Maintenance Cadence
[Per-contact cadence plan]

Quality Gates

• Is the plan specific to this account? "Engage more stakeholders" is not a plan. "Get [champion] to introduce me to [CFO name] at the QBR on April 15" is
• Does every target have a reason to connect? "I want to know them" is not a reason. "They control the budget and I have ROI data that would be useful for their planning" is
• Is the champion involved in the multi-threading? Trying to go around your champion instead of through them is the fastest way to damage the primary relationship. Multi-threading expands from the champion, not despite them
• Is the plan achievable within the CSM's capacity? A 5-contact multi-threading plan on every account in a 40-account portfolio is not realistic. Focus multi-threading effort on the highest-value and highest-risk accounts

Principles

• Multi-threading is a proactive investment, not a reactive response. The time to build relationships is before you need them. After the champion leaves, every new relationship is tainted by urgency
• Your champion is your ally in multi-threading, not an obstacle. Frame it as "I want to make sure I am supporting your team broadly, not just relying on you for everything." Most champions are relieved, not threatened, when you engage others
• Quality over quantity. Three genuine relationships (champion, executive sponsor, economic buyer) is better coverage than seven superficial contacts who would not take your call in a crisis
• The economic buyer is the highest-priority multi-threading target on any account. If you do not know the person who controls the budget, you are not managing the account -- you are managing a relationship. Those are different things