agentleFS
stephenroganstephenrogan/csm-skills/skills/multi-threading-playbook/SKILL.md

multi-threading-playbook

Skill0 starsChanged 8 months agoMITView on GitHub

Provides a structured approach to expanding relationships beyond a single contact at a customer account. Identifies target contacts, recommends engagement approaches, and builds a multi-threading strategy to reduce single-thread risk. Use when asked to multi-thread an account, expand relationships at a customer, reduce single-thread risk, build broader stakeholder coverage, develop new contacts, or when a CSM realises they are dependent on one person at a key account. Also triggers for questions about relationship breadth, single-thread risk, stakeholder expansion, going wide at an account, or how to build relationships with people beyond the primary contact.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Not every gap has the same urgency.

    line 68

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

EventImpact on Single-Threaded AccountImpact on Multi-Threaded Account
Champion leavesRelationship drops to zero. No internal advocate. Renewal at immediate riskRelationship 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 stallOther contacts continue the partnership. Leave is a pause, not a crisis
Champion gets promotedMay lose interest in your product as their scope expands. Or may gain the power to expand -- but you cannot influence whichSame upside with lower risk. Other contacts maintain day-to-day relationship
Champion becomes a detractorYour only advocate becomes your biggest obstacle. No counterbalanceOther contacts provide perspective. Detractor is one voice, not the only voice
Budget reviewChampion defends alone. If they are overruled, you have no backupMultiple stakeholders defend the investment from different angles
Competitive evaluationChampion may or may not tell you. If they do not, you have no visibilityMultiple 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

ContactRoleRelationship StrengthLast TouchPrimary ChannelValue 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:

PriorityCriteriaWhy
1Economic buyer not engagedThe renewal decision will be made by someone you have not spoken to
2Only one active contact (single-threaded)Any disruption to that contact puts the entire account at risk
3Executive sponsor not establishedNo air cover for the investment. Vulnerable to budget reallocation
4Adjacent function expressing interestOrganic expansion opportunity that deepens the account's dependency on the product
5New hire in a relevant roleFresh 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:

PathHow It WorksBest ForRisk
Champion introductionYour champion introduces you to the target contactLateral moves (same level, different function)Low -- warm introduction. Dependent on champion's willingness and relationship with the target
Value deliveryYou deliver something useful to the target directly (a benchmark, a report, training)Technical leads, end users, operations managersLow-Medium -- you earn the relationship through value
Executive-to-executiveYour leadership reaches out to their leadershipC-suite, VP levelMedium -- requires your exec's time and buy-in
Event or meetingYou meet them at a QBR, on-site visit, user group, or conferenceAnyone in the account who attends the eventLow -- natural context for meeting
Content sharingYou share a relevant article, benchmark, or insight that is specific to their roleAnyone -- good door-openerLow -- but may not generate a response. Better as a touchpoint than a relationship builder
Support interactionThey contact support or you are involved in resolving their issueTechnical leads, end users who had a problemMedium -- the interaction is reactive. You turn it into a proactive relationship

Step 5: Build the Multi-Threading Plan

Target ContactPathReason to ConnectProposed ApproachTimelineSuccess 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 MaturityCadencePurpose
New (first 3 touchpoints)Monthly minimumEstablish the relationship. Provide value. Demonstrate reliability
Established (3+ touchpoints, some rapport)Quarterly minimumMaintain the relationship. Share relevant updates. Ask how they are doing
Strong (mutual trust, open communication)As neededThe 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.