skills/competitive-threat-assessor/SKILL.md
Evaluates the severity of a competitive threat on a specific account by assessing the evaluation stage, trigger, relationship strength, and switching cost. Produces a threat classification with a response framework. Use when asked to assess a competitive signal, evaluate a competitive threat, determine how serious a competitor situation is, prepare a competitive response, or when a customer has mentioned evaluating alternatives. Also triggers for questions about competitive analysis on a specific account, handling competitor mentions, responding to customer evaluations, or assessing the risk of losing an account to a competitor.
npx skillsauth add stephenrogan/csm-skills competitive-threat-assessorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Evaluates how serious a competitive threat is on a specific account and produces a structured response framework. Turns "the customer mentioned a competitor" from a panic event into a assessed, actionable situation.
The key insight: competitive threats are symptoms, not causes. A customer evaluating alternatives has an unmet need. Your job is to find and address the need, not to fight the competitor.
Provide:
Score each dimension on a 1-5 scale:
| Dimension | 1 (Low Threat) | 3 (Moderate) | 5 (High Threat) | |-----------|----------------|--------------|-----------------| | Evaluation stage | Casual mention, no active evaluation | Active comparison, demo scheduled or completed | Decision imminent, contract presented | | Trigger severity | Proactive competitor outreach (customer was not looking) | Product gap or pricing concern (addressable) | Service failure or trust damage (relationship-based) | | Competitor fit | Competitor is weaker for this use case | Competitor is comparable | Competitor is stronger for the specific need that triggered the evaluation | | Relationship strength | Deep multi-threaded relationship with executive coverage | Adequate relationship, champion supportive | Thin or strained, single-threaded, champion departed | | Switching cost | High (deep integrations, trained team, embedded workflows) | Moderate (some integrations, moderate training) | Low (standalone tool, minimal configuration, easy to replace) | | Time pressure | Renewal 6+ months out | Renewal 60-180 days out | Renewal under 60 days |
Composite threat score = average of 6 dimensions.
| Score | Classification | Interpretation | |-------|---------------|---------------| | 1.0-2.0 | Low | Monitor. The customer is not actively pursuing alternatives. Reinforce value proactively | | 2.1-3.0 | Moderate | Act within 2 weeks. Investigate the trigger, reinforce value, address the gap | | 3.1-4.0 | High | Act this week. Dedicated save strategy required. Consider executive engagement | | 4.1-5.0 | Critical | Act today. Executive involvement, commercial flexibility, and root cause intervention required |
The response depends on why they are evaluating, not who they are evaluating:
| Root Cause | Response Focus | What to Avoid | |-----------|---------------|--------------| | Product gap | Address the gap: roadmap if planned, workaround if possible, honest acknowledgement if neither | Do not dismiss the gap. "We are working on it" without a timeline is worse than "we do not have that today" | | Pricing | Establish value first, then discuss pricing. Compete on ROI, not sticker price | Do not discount reflexively. Understand whether the issue is budget, value perception, or competitive pricing | | Service failure | Acknowledge, recover, rebuild. The competitor did not win -- you lost. Win back by being better | Do not deflect blame or minimise the failure | | Proactive competitor outreach | The customer was not looking. Reinforce the relationship and make the competitor's pitch irrelevant | Do not overreact. The customer took a meeting; they did not make a decision | | New leadership with prior preferences | Build the relationship with the new person on your product's merits. Do not fight their history | Do not badmouth their prior vendor. Respect their experience and show what your product does for this team | | Strategic priority shift | Reposition your value in the context of their new priorities. If it genuinely does not fit, be honest | Do not contort your product to fit a use case it does not serve. Honesty builds long-term credibility even in a loss |
For the specific capabilities the customer cares about (not a generic feature matrix):
| Dimension | Your Position | Competitor Position | Implication | |-----------|--------------|-------------------|------------| | [Capability 1] | [Your strength/weakness] | [Their strength/weakness] | [What this means for the customer] | | [Capability 2] | [Your strength/weakness] | [Their strength/weakness] | [What this means for the customer] |
Be honest with yourself. If the competitor is stronger in the area that triggered the evaluation, saying "we are better overall" does not address the customer's specific need. Address the specific gap, not the general landscape.
Not for sharing with the customer, but for your assessment:
| Factor | This Account | |--------|-------------| | Integrations to rebuild | [count and complexity] | | Users to retrain | [count] | | Workflows to reconstruct | [count and complexity] | | Data to migrate | [volume and complexity] | | Productivity loss during transition | [estimated weeks] | | Total estimated switching cost | [time and money] |
High switching costs favour you -- the customer's perceived pain of leaving may exceed their perceived pain of staying. But never rely on switching costs as your retention strategy. They buy time, not loyalty.
Based on the assessment:
## Competitive Response Plan: [Account Name]
**Threat Classification:** [Low/Moderate/High/Critical]
**Root Cause:** [What triggered the evaluation]
**Competitor:** [Named or unknown]
**Evaluation Stage:** [Early/Active/Decision imminent]
**Renewal Date:** [Date] ([X] days)
### Response Strategy
[2-3 sentences on the overall approach based on root cause and stage]
### Immediate Actions (This Week)
1. [Specific action with owner]
2. [Specific action with owner]
### 30-Day Plan
1. [Action to address root cause]
2. [Action to reinforce value]
3. [Action to strengthen relationship]
### Executive Engagement
- Needed: [Yes/No]
- If yes: [Who from your side, who from their side, what framing]
### Commercial Flexibility
- Available without approval: [What you can offer]
- Requires approval: [What needs escalation]
- Do not offer preemptively: [Discounting before understanding the full situation weakens your position]
### Decision Criteria
- Win signal: [What would indicate the customer is staying]
- Loss signal: [What would indicate you are losing]
- Walk-away point: [When the cost of retention exceeds the value of the account]
development
Structures the CSM's week based on their portfolio status, upcoming events, overdue items, and strategic priorities. Produces a time-blocked plan that balances reactive demands with proactive account management. Use when asked to plan a week, structure daily priorities, build a weekly schedule, allocate time across accounts, manage a busy week, or when a CSM feels overwhelmed and needs to determine where to focus. Also triggers for questions about time management, weekly planning, account prioritisation for the week, daily priority setting, or how to balance competing demands across a portfolio.
development
Constructs a compelling value narrative for a customer account by connecting product usage to business outcomes in the customer's language. Produces different versions for different audiences -- the champion, the CFO, the board. Use when asked to build a value story, articulate ROI, create a business case for the customer, prepare value evidence for a renewal or QBR, or when a CSM needs to translate usage metrics into business impact the customer will recognise. Also triggers for questions about value articulation, ROI storytelling, customer business case, value evidence, or how to prove the product is worth the investment.
data-ai
Takes raw usage data -- even a spreadsheet export or pasted metrics -- and identifies patterns, risks, and opportunities. Translates product analytics into account intelligence a CSM can act on. Use when asked to interpret usage data, analyse product metrics, make sense of a usage report, identify trends in customer behaviour, flag usage-based risks, or when a CSM has data but does not know what it means for the account. Also triggers for questions about usage analysis, product analytics interpretation, behavioural pattern detection, usage-based risk identification, or turning raw metrics into actionable insight.
development
Builds a structured 30-60-90 day plan for a CSM taking over a new book of accounts or joining a new team. Prioritises accounts by risk and value, identifies immediate relationship actions, and structures the ramp to full productivity. Use when asked to plan a book transition, create a new CSM onboarding plan, structure a territory takeover, build a 30-60-90 plan for a new role, or when a CSM is inheriting accounts and needs a systematic approach to getting up to speed. Also triggers for questions about account transitions, new book ramp-up, CSM onboarding to a portfolio, territory planning, or how to take over accounts from another CSM.