home / skills / microck / ordinary-claude-skills / objection-pattern-detector

objection-pattern-detector skill

safe

/skills_all/objection-pattern-detector

This skill mines lost deal notes to identify objection patterns and builds proven response playbooks from won deals.

npx playbooks add skill microck/ordinary-claude-skills --skill objection-pattern-detector

Review the files below or copy the command above to add this skill to your agents.

Files (2)

SKILL.md

1.4 KB

---
name: objection-pattern-detector
description: Mine lost deal notes to identify recurring objection patterns. Create objection response playbooks from won deals.
---

# Objection Pattern Detector
Mine lost deal notes to identify recurring objection patterns. Create objection response playbooks from won deals.

## Instructions

You are an expert at objection handling and sales enablement. Analyze lost deals, identify objection patterns, and create proven response frameworks from winning deals.

### Output Format

```markdown
# Objection Pattern Detector Output

**Generated**: {timestamp}

---

## Results

[Your formatted output here]

---

## Recommendations

[Actionable next steps]

```

### Best Practices

1. **Be Specific**: Focus on concrete, actionable outputs
2. **Use Templates**: Provide copy-paste ready formats
3. **Include Examples**: Show real-world usage
4. **Add Context**: Explain why recommendations matter
5. **Stay Current**: Use latest best practices for sales

### Common Use Cases

**Trigger Phrases**:
- "Help me with [use case]"
- "Generate [output type]"
- "Create [deliverable]"

**Example Request**:
> "[Sample user request here]"

**Response Approach**:
1. Understand user's context and goals
2. Generate comprehensive output
3. Provide actionable recommendations
4. Include examples and templates
5. Suggest next steps

Remember: Focus on delivering value quickly and clearly!

Overview

This skill mines lost-deal notes to surface recurring objection patterns and synthesizes playbooks from winning deals. It automates pattern recognition across CRM notes, call transcripts, and deal reviews to reveal root causes of loss. The output prioritizes repeatable objections and provides ready-to-use response frameworks for sales reps and managers.

How this skill works

The tool ingests unstructured deal notes, labels objection instances, clusters similar objections, and scores patterns by frequency and impact. It cross-references winning-deal language to extract successful rebuttals and templates, then assembles playbooks with scripts, key evidence, and recommended actions. Results are delivered as prioritized patterns, response templates, and tactical recommendations for coaching and collateral updates.

When to use it

After a quarter with rising loss rates to diagnose systemic objections
When onboarding new reps and you need tested objection scripts
Before sales enablement updates to align collateral with real buyer concerns
During win/loss analysis cadence to convert insights into playbooks
When A/B testing pricing or packaging triggers unknown buyer pushback

Best practices

Feed the skill consistent, labeled inputs (deal stage, outcome, transcript vs note)
Combine quantitative signals (loss reason tags, ARR impact) with qualitative notes
Prioritize high-frequency, high-impact objections for immediate action
Validate suggested rebuttals by pairing with recorded winning calls
Iterate playbooks monthly and measure lift with controlled rep cohorts

Example use cases

Detect a recurring 'budget timing' objection and create a script that converts 10–20% of those deals
Turn top three product misconceptions into one-page rebuttal cards for reps
Produce an enablement brief that maps objections to product collateral and demo snippets
Generate coaching guides showing word-for-word winning responses tied to deal outcomes
Build a prioritized roadmap of collateral updates driven by objection impact

FAQ

What input formats are supported?

Accepts CRM notes, call transcripts, meeting summaries, and structured win/loss tags; plain text or CSV uploads are typical.

How are objection patterns validated?

Patterns are scored by frequency and revenue impact, then validated against winning-deal language and sample call excerpts.

Can playbooks be exported?

Yes — playbooks and templates export to copy-paste-ready text, PDF briefs, or CSV for enablement systems.