Turn Call Notes Into Follow-Ups and CRM Updates
After every call, turn rough notes into three things in one pass: a follow-up email in your voice, a clean internal summary, and the CRM update you'd otherwise skip.
The deal is won or lost in the hour after the call, not during it.
Everyone takes notes. Almost no one turns them into a same-day follow-up, a clean summary, and a CRM update before the next meeting pushes them aside. Store your voice and your process and that whole after-call ritual becomes one paste and one review.
Notes that never become a follow-up are just a record of a conversation you're about to forget. The deal cools while the to-do sits in your notebook.
Capturing the call is worthless. Acting on it before the day ends is the whole game.
The follow-up is yours to send — review it. But starting from a drafted version in your voice means it actually goes out today instead of next week.
| Complexity | Easy |
| Tools needed | Claude Pro or above, Claude Desktop → Cowork mode, on macOS or Windows, Claude Projects |
| Time to build | ~15 min first time · ~3 min per call after that |
| Best for | Founder or salesperson running their own pipeline — B2B services and agencies |
What this solves
Calls that go well and then stall — because the follow-up email, the internal summary, and the CRM update never happen before the next meeting buries them.
The problem
The call went well. You scribbled notes, said you’d follow up, and moved straight into the next meeting. Three days later the notes are cold, you half-remember what you promised to send, the follow-up email still isn’t written, and the CRM says “had a call” with no detail. The momentum you built in the conversation has leaked away — not because the call was bad, but because the unglamorous after-work never happened. That after-work is where deals actually advance, and it’s the first thing that gets dropped when you’re busy.
The fix is making the after-call ritual fast enough that it always happens, the same day, every time.
Ingredients
- Claude Subscriptions — Cowork and Projects aren't available on the free plan
- Platforms & Modes — Cowork runs in the desktop app only — not on web or mobile. This recipe processes notes into several outputs at once — multi-step work that runs in Cowork
- Claude Projects — Your writing voice, your process stages, and what your CRM needs don't change call to call. A Project stores them so every follow-up sounds like you and every update is complete
How it works
You do this after every call, and the pieces — your voice, your stages, your CRM fields — are constant. A Project stores them so the follow-up sounds like you wrote it and the summary lands where it belongs.
- Open Claude Desktop and click Cowork in the mode selector across the top (Chat · Cowork · Code).
- In the left panel, find Projects and click the + button.
- Choose Start from scratch. Name the project “Call Follow-Ups” and let Claude set up its folder.
- You’ll know it worked when the project appears in the left panel with its own folder and an instructions field.
Your project has a folder on your computer — that’s where the two working files live.
- Ask Claude, right in the project: “Create two files in this project’s folder:
voice.mdandprocess.md. Leave them empty — I’ll fill them in.” (Or create them yourself in any text editor and save them into the project folder.) - Fill in both files using the descriptions below.
- Confirm Claude can see them: ask “List the files you can see in this project.” Both filenames should come back. If they don’t, see If It Doesn’t Work.
voice.md
How you write to prospects — your tone, your length, the way you open and close. This is what keeps the follow-up from sounding like a template. If you have a few emails you’re happy with, point Claude at them.
Example: “Short. Warm but not chummy. No ‘I hope this email finds you well.’ Open by referencing something specific they said. One clear next step, not three. Sign off plainly.”
process.md
Your pipeline stages and what your CRM update needs to capture — so the internal summary is structured the way your team and your records expect.
Example: “CRM needs: next step + date, deal stage, any new stakeholder, stated objection, budget signal. Stage advances only when next step is confirmed by the prospect, not proposed by me.”
Open your Project in Claude Cowork. Give Claude the specifics for this run, ask for the main output, then follow up for any additional pieces you want. The exact wording for each prompt — with what it’s asking for and why — is in What you actually type below.
Check three things before anything sends or saves:
- The email references something real. A follow-up that could go to any prospect is forgettable. It should name something specific from the call — their deadline, their concern, the thing they got excited about. If it’s generic, the notes had specifics Claude didn’t use; point them out.
- The next step is concrete and owned. “Let’s stay in touch” is not a next step. “I’ll send the security doc Thursday; you’ll loop in your CTO for a call next week” is. Make sure the email and the CRM update both carry a real, dated next action.
- The summary separates fact from your read. Action items should be what was agreed; your interpretation (“I think they’re price-shopping”) should be marked as yours. Confirm Claude didn’t record a hunch as something the prospect said.
Before you send: read the email as the prospect will. It’s going out under your name — the draft gets you 90% there, and your last read is where you confirm it sounds like you and lands the next step.
What you actually type
Name your files explicitly the first few runs, and ask Claude to show its work on anything that matters.
“Here are my notes from the [company] call [paste]. Using `voice.md` and `process.md`, give me three things: a follow-up email in my voice referencing what they actually said and confirming the next step; an internal summary with action items and owners; and a CRM update with stage, next step, and any new stakeholder or objection.”
“Tighten the email — it's a sentence too long. Keep the reference to their Q3 deadline.”
Three labeled outputs from one paste: a follow-up email in your voice that references something the prospect actually said and confirms a dated next step, an internal summary with action items and owners, and a CRM-ready update with stage, next step, and any new stakeholder or objection. The email should read send-ready after one pass of your edits, not template-ready. If the follow-up could go to any prospect, or the next step has no date and no owner, it missed.
- It can't summarize a call it doesn't have. Thin notes produce a thin follow-up — a transcript always beats scribbles.
- It drafts; you send. The email goes out under your name, and the last read is yours — the recipe gets it to 90%, not to sent.
- Out of the box it doesn't write to your CRM. The update arrives formatted to paste; writing it directly takes the connector in Extra Credit.
If it doesn’t work
- No Cowork tab in Claude Desktop — update the app to the latest version and confirm you’re on a paid plan; Cowork isn’t on the free tier. On Windows, Cowork also needs the Virtual Machine Platform feature enabled — if the tab still won’t appear, that’s the fix.
- Claude can’t see
voice.mdorprocess.md— the files aren’t in the project’s folder, or they’re in a different folder than the one the project owns. Open the project, check which folder it points to, and move the files there. Then re-run “list the files you can see.” - The follow-up could have gone to any prospect — the specifics were in the call but not in what you pasted, or they were there and Claude skipped them. Point at the moment that matters (“reference their Q3 deadline and the security concern”) and re-run. If your notes genuinely hold no specifics, that’s the real fix: capture one or two verbatim lines per call, or feed a transcript.
- The summary records your hunch as something the prospect said — the fact-versus-read split didn’t happen. Ask: “Separate what was agreed on the call from my interpretation, and label my interpretation as mine.” If it keeps blending the two, add that rule to
process.mdso every summary enforces it.
Extra credit
Small additions that pay back the next time you run it.
- CRM connector — connect your CRM so Claude writes the update directly instead of you copying fields over. See the Connectors guide.
- Transcript in — if you record calls, feed the transcript instead of notes for a fuller, more accurate summary.
- Same-day discipline — set a scheduled task that prompts you at end of day to run any calls you haven’t processed yet, so nothing carries to tomorrow.
“Most deals don't die in the meeting. They die in the silence after it.”
What this teaches you about Claude Cowork
The recipe is one application. The principles apply to everything you’d hand to Claude.
The bottleneck is action, not capture. You already take notes; the deal stalls because they never become a follow-up. The recipe attacks the actual failure point — the after-call work — by making it fast enough to always finish the same day.
Voice is stored context, not a per-email instruction. Keeping voice.md in the Project means every follow-up starts in your tone, so you’re editing instead of writing. That’s the difference between a draft that goes out today and one you mean to write later.
Separate what happened from what you think. A summary that blends agreed facts with your interpretation pollutes the record the whole team relies on. Forcing the split keeps your CRM trustworthy — and your forecast honest.
Who this is for
Founder or salesperson running their own pipeline in B2B services and agencies (5–100 employees).
The pain: Follow-ups written days late and a CRM that says 'had a call' with no detail
The outcome: Every call processed the same day — follow-up sent, summary filed, CRM current
Published June 11, 2026 · 0 views