community-automations/follow-up-writer

Sales & CRM

PublicClaude subagentDemo

Follow-Up Writer

The follow-up after a good call is where deals stall. The rep means to send it, gets pulled into the next meeting, and writes a generic note two days later that ignores half of what was discussed.

sonnet3 daysGongHubSpotGmailOpenAI
ClaudeClaude
ROI for
README.md

Why this subagent

The follow-up after a good call is where deals stall. The rep means to send it, gets pulled into the next meeting, and writes a generic note two days later that ignores half of what was discussed.

This agent reads the transcript the moment the call ends and drafts a follow-up that quotes the real conversation, matched to the contact's role and the deal stage. It lands in Gmail ready to review and send. The rep keeps control of the send button while the blank-page problem disappears.

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)

From a call transcript and deal context, draft a follow-up email that names two specifics from the call and one clear next step.

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.