A Call-Prep Dossier in Five Minutes
Before an important meeting, get a dossier that's actually useful: who's in the room, where the deal stands, the likely objections, and a suggested agenda you can steer.
Walk in knowing who's in the room, what they'll push on, and where you want the call to land.
Prep isn't re-reading the whole thread. It's the four things that change how you run the meeting: who's there and what they care about, where the deal honestly stands, what they're likely to object to, and the agenda you'll steer toward. Stored deal context makes that a five-minute pull.
The unprepared version is recognizable: you ask where things stand, they remind you, and you've spent your credibility before the real conversation starts.
Good prep changes how you run the meeting. Everything else is reading you could have skipped.
The agenda is a plan to steer with, not a script to read. Knowing where you want to land lets you adapt when the room goes somewhere else.
| Complexity | Easy |
| Tools needed | Claude Pro or above, Claude Desktop → Cowork mode, on macOS or Windows, Claude Projects |
| Time to build | ~20 min first time · ~5 min per meeting after that |
| Best for | Founder or sales lead running back-to-back meetings — B2B services and agencies |
What this solves
Walking into meetings cold and opening with 'remind me where we left off' — because the deal context exists but sits scattered across email, notes, and the CRM.
The problem
You’ve got three meetings today and they’ve blurred together. You walk into the second one and can’t immediately recall whether you’d sent pricing, who the skeptical one was, or what they said they needed to see before moving forward. So you open with “remind me where we left off” — which puts the work on them and tells them you weren’t tracking the deal. The information exists, scattered across email, notes, and your CRM. It just isn’t assembled into something you can absorb in the five minutes before the call.
The fix is pulling the scattered context into one dossier, fast, 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 pulls deal context and assembles a dossier — multi-step work that runs in Cowork
- Claude Projects — Your sales process, your common objections, and how you like meetings to run stay the same. A Project stores them so every dossier follows your playbook
How it works
You prep for meetings constantly, and your process — your stages, your standard objections, how you like to run a room — is consistent. A Project stores that so every dossier is built to your playbook instead of from scratch.
- 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 Prep” or “Meeting Prep” 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:
sales-process.mdandobjections.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.
sales-process.md
Your stages and what has to be true to advance, plus how you like a meeting structured. This is what lets the dossier place the deal honestly and propose an agenda that fits where things actually stand.
Example: “Stages: discovery → demo → proposal → negotiation → close. To advance past demo, we need a confirmed problem, a budget signal, and an identified decision-maker. Meeting shape: recap, one new thing, confirm next step before we hang up.”
objections.md
The objections you hear over and over, and the response that actually works for each — so the dossier can warn you what’s coming and how you’ve handled it.
Example: “‘Too expensive’ → reframe to cost of the status quo, ask what they’re comparing to. ‘We already have a tool’ → ask what it doesn’t do that’s making them take this call. ‘Need to talk to my team’ → offer to join that conversation or arm them for it.”
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 you join the call:
- The deal status is honest, not optimistic. A dossier that says “ready to close” when you’ve never confirmed budget is setting you up to misread the room. Make sure the status reflects what’s actually been established against your process, including what’s missing.
- The objections are this deal’s, not generic. If the warned objections are the same ones for every account, they’re not prep. Push Claude to ground them in what this specific buyer has said or signaled.
- The agenda leaves room to listen. A minute-by-minute script means you’ll talk over the actual conversation. The agenda should be a few beats to steer toward, with space for where they take it.
Before you join: does the dossier match your gut on this deal? You’ve been in the room; Claude has only the records. If something feels off, the notes are probably incomplete — trust your read and prep for it.
What you actually type
Name your files explicitly the first few runs, and ask Claude to show its work on anything that matters.
“I have a meeting with [company] in an hour — here's the email thread and my notes [paste, or pull from CRM]. Using `sales-process.md` and `objections.md`, give me a dossier: who's attending and what each likely cares about, where this deal honestly stands and what's needed to advance, the two objections most likely to come up with how to handle them, and a suggested agenda I can steer.”
“What's the one question I should ask to confirm we can move past the demo stage?”
A dossier with four labeled parts: who's attending and what each likely cares about, where the deal honestly stands against your stages and what's missing to advance, the two objections most likely to come up with how to handle them, and a short agenda you can steer. Short enough to absorb in the five minutes before the call. If the status reads optimistic or the objections would fit any deal, it missed — send it back.
- It only knows the thread, notes, or CRM records you give it. A deal whose real state lives in your head produces a dossier that's wrong in exactly the way your records are.
- It doesn't predict the meeting. The agenda is a destination to steer toward — the room will still go places the dossier didn't, and that's fine.
- It doesn't capture what happens on the call. The after-call summary and CRM update are a separate recipe (see 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
sales-process.mdorobjections.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 dossier says the deal is further along than it is — Claude is measuring against criteria too soft to fail. Check that
sales-process.mdstates what has to be true to advance (“confirmed budget signal,” not “good momentum”), and that you pasted the latest thread. An optimistic status almost always means stale context or vague criteria. - The objections are your standard list, not this deal’s — nothing in the context ties them to this buyer. Paste what they’ve actually said or signaled, then ask: “Ground each objection in something from this thread — if you can’t, say so.” A warning with no grounding is just
objections.mdread back to you.
Extra credit
Small additions that pay back the next time you run it.
- CRM connector — connect your CRM so Claude pulls deal stage, history, and contacts automatically instead of you pasting. See the Connectors guide.
- Calendar connector — have Claude generate dossiers for every meeting on tomorrow’s calendar in one overnight pass.
- Close the loop — after the call, use the Call-Summary recipe to capture what happened so the next dossier is even sharper.
“The point of prep isn't to predict the meeting. It's to not be surprised by the parts you could have seen coming.”
What this teaches you about Claude Cowork
The recipe is one application. The principles apply to everything you’d hand to Claude.
Assembly is the value. The information you need to prep almost always exists already — it’s just scattered. The recipe wins by pulling email, notes, and CRM into one absorbable dossier, which is work you’d never do by hand in the five minutes you actually have.
Honest beats optimistic. A dossier that flatters the deal is worse than none, because it makes you misread the room. Storing your real advancement criteria forces the status to be measured against what’s actually been established — which is the version that helps you.
A plan you can steer, not a script you read. The agenda’s job is to give you a destination, not lines. Knowing where you want the call to land is what lets you follow the prospect when they take it somewhere unexpected and still close on a next step.
Who this is for
Founder or sales lead running back-to-back meetings in B2B services and agencies (5–100 employees).
The pain: Joining meetings unable to recall where the deal stands or who'll push back
The outcome: Every meeting opens oriented — status, objections, and agenda absorbed in five minutes
Published June 12, 2026 · 0 views