Ic Cross Func Prep

Cross-Functional Prep

Prepares materials for internal meetings by compiling relevant account data tailored to the meeting type and audience. Part of the Internal Coordination pillar.

This is a data compilation and formatting skill. It assembles the right data for the right audience in the right format. The CSM or manager adds narrative, priorities, political awareness, and strategic framing.

When to Run

• Triggered: By calendar integration when a recurring internal meeting is approaching (24 hours before)
• On-demand: When a CSM or manager requests materials for a specific meeting
• Scheduled: Weekly for recurring meetings (manager 1:1s, pipeline reviews)

Core Execution Logic

Step 1: Identify Meeting Type and Audience

Determine from the calendar event or request:

Step 2: Pull Data by Meeting Type

Manager 1:1 / Account Review:

Pipeline / Renewal Review:

CS-Product Sync:

Escalation Committee:

Step 3: Format for Audience

Formatting principles by audience:

Step 4: Deliver 24 Hours Before

• Generate the materials package
• Deliver to the meeting organiser (or all attendees if configured)
• Include a one-line summary of what is new or changed since the last meeting of this type
• Flag any items that require a decision in the meeting (not just awareness)

Step 5: Post-Meeting Action Capture

After the meeting (if CSM provides notes):

• Extract action items from meeting notes
• Route to lo-sla-monitor for commitment tracking
• Update CRM records as needed
• Set reminders for follow-up items

Output Format

{
  "meeting_id": "mtg-2026-weekly-pipeline-w10",
  "meeting_type": "pipeline_review",
  "date": "2026-03-11T10:00:00Z",
  "prepared_for": "CS Leadership + CRO",
  "generated": "2026-03-10T10:00:00Z",
  "materials": {
    "renewal_forecast": {
      "source": "cm-renewal-forecaster",
      "headline": "NRR forecast 95.6% for next 90 days. Down 0.3% from last week",
      "detail_included": true
    },
    "at_risk_accounts": {
      "source": "bi-risk-detector + lo-renewal-manager",
      "count": 4,
      "total_arr_at_risk": 340000,
      "accounts": [
        {
          "name": "Acme Corp",
          "arr": 85000,
          "renewal_days": 66,
          "classification": "at_risk",
          "top_risk": "Champion departed, usage declining",
          "intervention": "New stakeholder identified, outreach scheduled this week"
        }
      ]
    },
    "expansion_pipeline": {
      "source": "bi-expansion-detector + CRM",
      "count": 6,
      "total_pipeline_value": 180000,
      "new_this_week": 1
    },
    "churn_this_period": {
      "count": 0,
      "arr_lost": 0
    }
  },
  "decisions_needed": [
    "Acme Corp: approve executive engagement for at-risk renewal (CSM requesting VP-to-VP call)"
  ],
  "changed_since_last_meeting": [
    "Acme Corp moved from Watch to At Risk (champion departed)",
    "Delta Corp expansion signal surfaced ($45k opportunity)"
  ]
}

Handoff to Human

Confidence and Limitations

• High confidence for data compilation -- pulling from defined sources with structured output is deterministic
• High confidence for meeting-type matching -- the rules for which data goes to which meeting are defined
• Medium confidence for "changed since last meeting" detection -- requires access to prior meeting's data state, which depends on data retention
• Low confidence for determining what matters most in each specific meeting. The data shows what has changed, but the meeting organiser knows what the audience cares about this week. A data change that is statistically significant may be operationally irrelevant, and vice versa
• Cannot prioritise which accounts to discuss -- that is the meeting organiser's judgment
• Cannot navigate internal dynamics -- knowing which topics to raise in a group setting vs. offline is pure human judgment
• Materials are prepared 24 hours before. Last-minute changes (account churning the day before a pipeline review) may not be captured. The CSM should add real-time context

Dependencies

Required:

• Calendar integration (meeting detection and timing)
• CRM API (account data, ownership)
• bi-account-brief (account context for any account discussed in detail)

Meeting-type specific:

• Pipeline review: cm-renewal-forecaster, bi-risk-detector, bi-expansion-detector
• CS-product sync: pa-feedback-aggregator, pa-adoption-tracker, ic-feature-request-tracker
• Escalation committee: ic-escalation-router
• Manager 1:1: lo-check-in-scheduler, lo-sla-monitor, lo-milestone-tracker, bi-health-score

Downstream consumers:

• lo-sla-monitor (post-meeting action items)
• CRM (meeting record and outcomes)

References

• references/meeting-prep-templates.md -- Detailed templates for each meeting type with formatting guidelines