# Prepare for tomorrow’s sales call with Claude, and check the brief before you trust it

A labeled walkthrough from calendar invite, past emails and a pasted LinkedIn profile to one checked brief, and where a manual chat stops being monitoring.

URL: https://www.hiresteve.ai/blog/ai-deal-prep-workflow
Updated: 2026-10-12

Paste what you already hold about tomorrow’s meeting into one Claude chat: the invite, the email thread, the public LinkedIn profile text and any call notes. Ask for dated facts and inferences in separate lists, then open every source it names before you walk in. The example below is illustrative practice material, not a recording of a product.

**Key takeaways**

- Confirm who the meeting is with before researching anyone; the wrong account produces a confident brief about the wrong company.
- Claude reads your calendar and Gmail through Anthropic’s connectors. We found no documented first-party LinkedIn connector on September 16, 2026, so check the live directory or paste permission-cleared profile text.
- Ask for facts and inferences in separate lists, each fact tied to a pasted source and a date.
- This manual chat brief runs when asked; configured connectors can bring in calendar and email context.

## Confirm who the meeting is with

Before you paste anything, answer one question from the invite alone: is this a new prospect, an existing customer, a partner or a colleague? [Simular’s meeting-prep template](https://www.simular.ai/workflow-template/ai-meeting-prep-for-sales-calls) puts this premise check first. A confident brief about the wrong account is worse than no brief, so make this check before anything else.

Check the attendee email domain against the company you think you are meeting. If a name resolves to two people, or the domain belongs to a parent company, write that down as an open question rather than letting the research settle it for you.

## Gather what you already have

Use a plain chat for a single meeting. If you prepare for calls every week, run each meeting as a new chat inside a Claude Project so the instructions and any reusable account notes carry over; the [Project setup lesson](/blog/claude-project-setup) covers that once. Anthropic’s [Project guide](https://support.claude.com/en/articles/9519177-how-can-i-create-and-manage-projects), checked September 16, 2026, allows up to five Projects on the Free plan.

Three inputs cover most calls.

**The calendar event.** With the Google Calendar connector enabled, Claude can view your calendar events and check attendee availability. Anthropic’s [Google Workspace connector guide](https://support.claude.com/en/articles/10166901-use-google-workspace-connectors), checked September 16, 2026, lists it as available on every plan, with Team and Enterprise organizations needing an administrator to enable it. Without the connector, paste the invite: title, attendees, agenda, time.

**Prior contact.** The Gmail connector lets Claude search and read email by natural language. By default Claude asks before sending, replying or forwarding, while Team and Enterprise owners can set a different policy. Choose the thread date range from the relationship and meeting, then add call notes or a transcript you already have. If proposals live in Google Drive, the Drive connector extracts document text but does not process images embedded in documents.

**The LinkedIn profile.** We did not find a first-party LinkedIn connector in Anthropic’s documentation on September 16, 2026, but the live Connectors Directory changes and was not crawlable in this review. Check the directory first. If none appears, open the public profile yourself, copy permission-cleared profile text and recent posts relevant to this meeting, and note the date.

The [connectors lesson](/blog/mcp-for-marketers) goes further on permissions and what each connection can and cannot read.

## Ask for facts and inferences separately

A model given a profile and an email thread may write “they are evaluating vendors this quarter” even when nothing you pasted supports it. [Simular’s template](https://www.simular.ai/workflow-template/ai-meeting-prep-for-sales-calls) separates facts from inference and dates external facts. Here, use that split to expose unsupported claims. Asking for separate fact and inference lists puts the distinction on the page where you can see it.

```prompt
Using only the material I pasted above, write a concise call brief with:
1. Facts: each with the pasted source it comes from and its date.
2. Inferences: things you conclude from those facts, marked as guesses.
3. Relevant talking points and likely objections, each tied to a fact or
   inference by number.
4. Open questions I should confirm on the call.
Do not add anything not supported by the pasted material.
```

If the meeting is with several people, request the fact list per attendee before the shared talking points.

## What the checked brief looks like

**Illustrative example**

The rows below are invented practice material with placeholders, shown to teach the shape of a good result. They do not describe a real prospect, a real conversation or any product’s output.

| Section | Example row | What makes it usable |
| --- | --- | --- |
| Fact | Three attendees from the prospect side; the invite title names a renewal. Source: calendar event, [date]. | Sourced to something you pasted, dated. |
| Fact | Attendee’s title changed in [month]; two of their recent posts discuss consolidating tools. Source: pasted LinkedIn text, copied [date]. | Copy date recorded, because the profile can change. |
| Inference | The title change may mean a new budget owner. Marked as a guess. | Labeled, so nobody repeats it as fact. |
| Talking point | Ask how the consolidation posts relate to this renewal (ties to fact 2). | Traceable to a numbered fact. |
| Objection | “We already get this from our current vendor.” Based on the [month] email thread. | Grounded in prior contact, with a date. |
| Open question | Who signs, and is procurement involved? | Not answered from the pasted material, so it is asked, not assumed. |

A brief that reads like this is short, and every specific claim has a pointer next to it. The talking points come from the facts, and the objection comes from an email you can reopen.

## Check it before you walk in

A claim that sounds plausible and a claim that appears in what you pasted are different things, and the brief will contain both. The check separates them.

- Open each source named beside a fact and confirm the wording and date match.
- Delete any fact that has no pasted source, or move it to open questions.
- Read the inferences aloud and decide which ones you would say to the prospect’s face.
- Recheck the attendee list against the invite one more time.
- Save the checked brief with the meeting date so you can compare it to what happened.

Hand-grade a handful of briefs against the calls that followed. If a talking point keeps missing, the fix is usually in what you paste, not in the prompt.

## Where this method stops

This paste-led manual workflow runs when asked. Connectors can bring in calendar and email context when configured, but their availability, permissions and source scope vary. Keep this meeting’s factual inputs in the chat or Project as dated source material.

The LinkedIn step stays manual when no approved connector is available. For frequent calls with several attendees, repeating it can make the method hard to sustain. The brief also lands in your chat rather than the channel where your team works, so sharing it is another copy and paste. Making this repeatable for a team is a different job, covered in the [workflow handoff lesson](/blog/claude-workflow-handoff), and writing the standing brief for it is covered in [how to write a job brief for Claude](/blog/claude-job-brief).

## When this is Steve’s job instead

Steve Sales Prep sends a brief to Slack before each meeting. A rep can type `/prep` in Slack with a LinkedIn URL or an email address. Auto-prep runs on meetings from your connected calendar, 25 to 40 minutes before each one. Steve fetches the LinkedIn profile, finds it from an email address first where needed, and can add matching calls already imported from Gong, Avoma, Outreach, Grain, Fireflies or Zoom. It answers questions saved by the rep or manager, posts the brief to Slack, and keeps a shareable web version.

That is a different mechanism from the chat above, and the illustration in this article is not a demonstration of it. Manual `/prep` is an ad-hoc Slack entry, while scheduled auto-prep runs from your calendar. Past-call context appears only when matching imported calls are available; without them, Steve can still build from LinkedIn context. If the configured workflow matches your needs, [Steve Sales Prep](/products/sales-prep) is the page to read. Decide the questions and check what comes back.

## Frequently asked

### Can Claude read a LinkedIn profile for me?

We did not find a first-party LinkedIn connector in Anthropic’s documentation on September 16, 2026. Check the live Connectors Directory because availability changes; if none appears, paste permission-cleared profile text manually and record the date.

### Do I need a paid Claude plan for this?

No. Anthropic lists the Google Calendar, Gmail and Drive connectors and up to five Projects as available on the Free plan. Team and Enterprise organizations need an administrator to enable connectors first.

### Is a Claude chat the same as an automated meeting-prep tool?

This manual chat workflow runs when asked. Connectors can bring in calendar and email context when configured, but availability, permissions and source scope vary.

### What if the brief states something I never pasted?

Treat it as unverified. Ask Claude which pasted line supports it; if it cannot point to one, delete the claim or check it in the original source before the call.