Expo Followup Pipeline — Data skill for Claude Code

expo-followup-pipeline

**[English](#english) | [中文](#中文)**

Turn a conference, trade show, or business trip into a **tracked follow-up pipeline** — instead of a pile of conversations that quietly evaporate.

Works with **WorkBuddy, Claude Code, Codex CLI, Gemini CLI, Cursor, and GitHub Copilot**.

---

English

The problem

You get back from a trip and your leads are scattered across five places: the event app's chat history, voice memos on your phone, your inbox, your calendar, and your CRM. Consolidating it by hand takes half a day, and you still miss things.

This skill hardcodes the **collect → reconcile → structure → deliver** chain so it runs the same way every time, and lands the result somewhere that will actually remind you.

Six steps

1. Collect — pull from five sources in priority order (trip calendar > voice transcripts > event app > email > CRM)
2. Structure — one card per contact, with an explicit status per contact
3. Emit — a Markdown follow-up table sorted by due date, not by company name
4. Land tasks — create real tasks with real due dates
5. Land reminders — calendar reminders (never meetings, never with attendees)
6. Write back — fill the on-site notes and action-points fields in your CRM, then log the run

Step 1 deliberately starts with the **trip calendar**, not the pre-trip plan. Meetings that actually happened — including the short events you typed into your phone on site — beat any schedule made in advance.

The part that earns its keep

The status field. `Not met · need to reach out` (expired invites, unanswered last-minute requests) goes in **its own section**, so you don't quietly count missed contacts as active pipeline.

Triggers

• "Just got back from the trip, help me organize the follow-ups"
• "Turn what I discussed at the conference into todos"
• "Expo debrief" / "conference recap" / "follow-up table"
• "Turn these meeting notes into tasks"
• "Who should I chase this week?"

I