interpret_leadership_change

Instructions

Implementation Reference

• src/main.ts:350-358 (registration)

  Tool registration in the ListToolsRequestSchema handler. The tool 'interpret_leadership_change' is defined with a description and inputSchema that expects a 'change_type' parameter (enum: ceo_change, cfo_change, cto_change, cmo_change, founder_departure).

  {
    name: "interpret_leadership_change",
    description: "Interpret a leadership-change signal. Returns interpretation, outreach timing, pitch angle. Types: ceo_change, cfo_change, cto_change, cmo_change, founder_departure.",
    inputSchema: {
      type: "object",
      properties: { change_type: { type: "string", enum: Object.keys(LEADERSHIP_SIGNALS) } },
      required: ["change_type"]
    }
  },

• src/main.ts:412-416 (handler)

  Handler logic in the CallToolRequestSchema handler. Looks up the change_type in the LEADERSHIP_SIGNALS data structure and returns the interpretation as JSON. If unknown, returns an error.

  if (name === "interpret_leadership_change") {
    const data = LEADERSHIP_SIGNALS[(args as any).change_type];
    if (!data) return { content: [{ type: "text", text: JSON.stringify({ error: "Unknown change_type. See enum.", _meta: MCP_META }, null, 2) }] };
    return { content: [{ type: "text", text: JSON.stringify({ change_type: (args as any).change_type, ...data, _meta: MCP_META }, null, 2) }] };
  }

• src/main.ts:353-356 (schema)

  Input schema for the tool: expects an object with 'change_type' (string, enum of the five leadership signal types).

  inputSchema: {
    type: "object",
    properties: { change_type: { type: "string", enum: Object.keys(LEADERSHIP_SIGNALS) } },
    required: ["change_type"]

• src/main.ts:212-253 (helper)

  The LEADERSHIP_SIGNALS data dictionary containing all leadership change interpretations for ceo_change, cfo_change, cto_change, cmo_change, and founder_departure.

  const LEADERSHIP_SIGNALS: Record<string, any> = {
    "ceo_change": {
      signal_strength: "Very High",
      interpretation: "Company-wide reset. Strategy review imminent. All major spend will be reviewed. New CEO typically replaces/reviews 30-60% of tooling within first 12 months.",
      outreach_timing: "Week 4-8 of new CEO tenure",
      pitch_angle: "Strategic alignment with new CEO's prior-company stack and priorities",
      common_pitfalls: ["Reaching out in week 1 (too early)", "Not researching CEO's prior company tech preferences"],
      average_decision_window: "120-360 days"
    },
    "cfo_change": {
      signal_strength: "High",
      interpretation: "Cost discipline + audit pressure incoming. Stack rationalization. Renewal scrutiny.",
      outreach_timing: "Week 6-10 of new CFO tenure",
      pitch_angle: "ROI/payback period math, consolidation savings, audit-readiness",
      common_pitfalls: ["Generic ROI claims without specific peer benchmarks"],
      average_decision_window: "60-180 days"
    },
    "cto_change": {
      signal_strength: "High",
      interpretation: "Technical stack reset. Architecture review. Often replaces 20-40% of dev tools in first 9 months.",
      outreach_timing: "Week 4-12",
      pitch_angle: "Architecture compatibility with their prior-company stack",
      common_pitfalls: ["Pitching tools they already adopted at previous company without checking", "Not respecting build-vs-buy lens"],
      average_decision_window: "90-240 days"
    },
    "cmo_change": {
      signal_strength: "Medium-High",
      interpretation: "Marketing reset. MAP / content / attribution decisions in 90 days. Brand work likely.",
      outreach_timing: "Week 3-8",
      pitch_angle: "Performance attribution, pipeline contribution, peer-CMO playbook references",
      common_pitfalls: ["Ignoring demand-gen vs brand-marketing distinction"],
      average_decision_window: "60-180 days"
    },
    "founder_departure": {
      signal_strength: "High (negative or positive)",
      interpretation: "Major culture/strategy signal. If founder out = professionalization signal. If founder back as CEO = reset signal. Either way, expect tooling review.",
      outreach_timing: "Week 4-8 (let dust settle)",
      pitch_angle: "Tailor based on direction — professionalization (mature tooling) or reset (lean tooling)",
      common_pitfalls: ["Not reading the post-departure narrative carefully"],
      average_decision_window: "120-360 days"
    }
  };