octavehq/insights

/octave:insights - Field Intelligence

Surface insights from your sales conversations—objections, pain points, questions, and what's resonating. Learn from the field to improve your library and messaging.

Usage

/octave:insights [--type <finding-type>] [--period <time-range>]

Options

• --type <type> - Focus on specific finding type (objections, pain-points, questions, competitors, value-props)
• --period <range> - Time range (today, week, month, quarter, custom)
• --segment <name> - Filter by segment
• --persona <name> - Filter by persona
• --company <domain> - Filter by company

Examples

/octave:insights                                    # Overview of recent insights
/octave:insights --type objections                  # Top objections
/octave:insights --type pain-points --period month  # Pain points this month
/octave:insights --persona "CTO"                    # Insights from CTO conversations
/octave:insights --company acme.com                 # Insights from Acme conversations

Instructions

When the user runs /octave:insights:

Step 1: Determine Focus

If no options provided, show an overview:

What insights would you like to explore?

1. Overview - Summary across all finding types
2. Objections - What objections are prospects raising?
3. Pain Points - What problems are prospects mentioning?
4. Questions - What are prospects asking about?
5. Competitors - Which competitors are coming up?
6. Value Props - Which value props are resonating?
7. Custom - Specific filters

Your choice (or just ask a question):

Step 2: Query Events and Findings

Use the MCP tools to gather data. list_events takes event types inside filters; list_findings requires a natural-language query describing the kind of findings you want, with entity and outcome filters inside eventFilters.

For Overview:

# Get recent events
list_events({
  startDate: "<30 days ago>",
  endDate: "<today>",
  limit: 50,
  filters: { eventTypes: ["CALL_TRANSCRIPT", "EMAIL_SENT", "EMAIL_REPLY_RECEIVED"] }
})

# Get findings across the main types
list_findings({
  query: "objections, pain points, questions about the offering, competitor mentions, value props presented",
  startDate: "<30 days ago>",
  endDate: "<today>",
  limit: 100
})

Group the returned findings by type yourself (objections, pain points, questions, competitors, value props) before presenting the overview.

For Specific Type (e.g., Objections):

list_findings({
  query: "objections and pushback raised by prospects in calls and emails",
  startDate: "<period start>",
  endDate: "<period end>",
  limit: 50
})

With Persona/Segment Filter:

list_findings({
  query: "<finding type description>",
  eventFilters: {
    personas: ["<persona_oId>"]
  },
  limit: 50
})

Step 3: Present Insights

---

Overview Output

See overview-output.md for the overview output template.

---

Type-Specific Output (Objections)

See objections-output.md for the objection-type output template.

Step 4: Drill Down Options

When user wants to see specific events:

get_event_detail({
  eventOId: "<event_oId>"
})

Present the full context:

EVENT DETAILS: Call with John Smith (Acme Corp)
===============================================
Date: January 15, 2026
Duration: 32 minutes
Participants:
  - Internal: Sarah (AE), Mike (SE)
  - External: John Smith (VP Ops), Lisa Chen (Director)

Matched Persona: VP Operations
Matched Playbook: Enterprise Efficiency

---

KEY FINDINGS

Objections Raised:
• [12:34] John: "Your pricing is 2x what we're paying now for our current solution"
  → Response: Sarah mentioned ROI payback period

Pain Points Acknowledged:
• [08:15] John: "We're spending 20 hours a week on manual data entry"
  → Matches persona pain point ✓

• [15:42] Lisa: "The biggest issue is data not syncing between systems"
  → Consider adding to persona

Questions Asked:
• [18:20] John: "How long does implementation typically take?"
• [22:05] Lisa: "Do you integrate with Salesforce?"

Competitor Mentioned:
• [25:30] John: "We looked at [Competitor] last year but didn't move forward"

Value Props Delivered:
• [10:15] Sarah: "Customers typically see 80% reduction in manual work"
  → Positive response from John

---

[View full transcript] (uses get_event_detail with includeTranscript: true)

Step 5: Apply Updates to Library

If user wants to update library based on insights:

Based on this insight, I recommend:

Update Persona: VP Operations
Add pain point: "Data silos causing manual reconciliation work"
Add objection: "Pricing compared to current solution"

Update Playbook: Enterprise Efficiency
Add objection handling: "Pricing 2x current solution"
Response: "Let's look at total cost of ownership including the 20 hours/week
your team spends on manual work. At $X/hour, that's $Y annually..."

Apply these updates?
1. Yes, update both
2. Update persona only
3. Update Motion ICP narrative only
4. Let me customize first
5. Skip

If yes, use update_entity to apply.

Finding Types Reference

Express the finding type in the list_findings query text:

| Type | Description | Example query | |------|-------------|---------------| | objections | Pushback and concerns raised | "objections and pushback raised by prospects" | | pain-points | Problems prospects mention | "business problems and pain points prospects described" | | questions | Questions asked about offering | "questions or confusion about our offering" | | competitors | Competitor mentions | "competitors mentioned or compared against our offering" | | value-props | Value props that resonated | "value props presented and how prospects responded" | | use-cases | Use cases discussed | "use cases brought up in conversations" | | proof-points | Proof points referenced | "proof points and customer stories cited" |

MCP Tools Used

Event & Finding Access

• list_events - Search events with filters
• list_findings - Aggregate findings across events
• get_event_detail - Get detailed event info with transcript/content

Library Context

• get_entity - Get persona / segment / competitor / objection details
• list_motions / list_motion_icps / find_motion_icp - Pull the Motion ICP narrative (Target ICP overview, Operating landscape, Strategic narrative, Pains and consequences, Benefits and impacts, Methodology, References) for persona × segment context
• search_knowledge_base - Find related library content

Library Updates

• update_entity - Apply suggested updates to library entities (personas, segments, objections, etc.)
• update_motion_playbook - Edit Motion ICP narrative sections (Strategic narrative, Benefits and impacts, Pains and consequences) with field-informed refinements

Error Handling

No Events Found:

No events found for the specified period.

This could mean:

1. No calls/emails have been synced yet
2. The date range is too narrow
3. Filters are too restrictive

Try:

• Expanding the date range
• Removing filters
• Check that your CRM/email integration is connected in Octave

No Findings Extracted:

Events found but no findings extracted yet.

Findings are extracted automatically when events are processed. Recent events may still be processing.

Check back in a few minutes, or view raw events instead.

Related Skills

• /octave:analyzer - Analyze specific conversations in depth
• /octave:wins-losses - Focus on deal outcomes
• /octave:audit - Ensure library captures field learnings
• /octave:library - Update library with insights
• /octave:battlecard - Competitive intelligence from conversation data
• /octave:icp-refine - Use conversation patterns to refine ICP
• /octave:enablement - Turn field insights into team enablement materials