community-automations/meeting-prep

Sales & CRM

PublicClaude subagent

Meeting Pre-Brief

Reps walk into calls cold because prepping means opening the CRM, scrolling call notes, and rereading the last email thread. With back-to-back meetings, that prep just does not happen, and it shows.

sonnet4 daysGoogle CalendarHubSpotGongSlack
ClaudeClaude
ROI for
README.md

Why this subagent

Reps walk into calls cold because prepping means opening the CRM, scrolling call notes, and rereading the last email thread. With back-to-back meetings, that prep just does not happen, and it shows.

Thirty minutes before each external meeting, this agent reads the deal, the recent calls, and the email history, then sends a tight brief to Slack. You get the current stage, what is blocking the deal, and three things worth raising. The rep shows up sounding like they remember every detail, because now they do.

How it runs

    • Read

      Used at step 01 to kick off the pipeline.

    • Write

      Used at step 01 to kick off the pipeline.

    • WebFetch

      Used at step 01 to kick off the pipeline.

    • WebSearch

      Used at step 01 to kick off the pipeline.

Sample output

json
// Sample output
// (generated when the pipeline finishes)

For an upcoming meeting, return a brief with deal_stage, two to three blockers, and exactly three talking points tied to recent activity.

Unlock the rest

The full agent definition, install snippet, and starter task are gated for community members.

Members get the full `.md` agent file, the npm / pnpm install one-liners, a starter prompt that we've tuned against real runs, and the open-source repo when this automation ships there. One email, magic link, done.