---
title: "Prepare a one-page account brief before a sales meeting"
description: "AI prompt and skill that turn website text, emails and CRM notes into a one-page sales meeting brief that flags what is unknown."
url: https://atulsingh.co.in/ai-playbooks/pre-meeting-account-brief
skill: https://atulsingh.co.in/ai-playbooks/pre-meeting-account-brief/SKILL.md
function: sales
roles: ["Sales executive", "Account manager", "Business development manager", "Founder doing their own sales"]
industries: ["saas", "professional-services", "manufacturing"]
published: 2026-11-14T20:49:16.886+00:00
updated: 2026-11-15T15:16:16.108443+00:00
---

# Prepare a one-page account brief before a sales meeting

This playbook turns the material you already have on a prospect into a one-page brief before a sales meeting. You paste website text, LinkedIn about text, past emails and CRM notes. You get what the company does, likely priorities, three questions to ask, risks, what to avoid and a clear list of unknowns. A person still checks it before the call.

**Time saved:** about 30 minutes per meeting

## What to gather

- The company's website text: the About page, a services or products page and any recent news page, pasted as plain text.
- The contact's LinkedIn about text and current job title, copied from their public profile.
- Any past emails or messages with this company, with personal phone numbers and addresses removed. Keep the date on each one.
- Your CRM notes: how the lead arrived, who you have spoken to and anything agreed.
- A line on the meeting: date, length, what you sell and what you want from the call.

## Steps

1. Gather the sources above and paste each one into the matching field. If you do not have one, write 'Not available' in that field instead of leaving it empty.
2. Remove anything the brief does not need: personal phone numbers, home addresses, private messages and internal pricing.
3. Copy the prompt into your company's approved AI workspace, fill in the fields and run it.
4. Read the brief with the sources open. Check every item marked 'Stated' against the pasted text and delete anything you cannot trace.
5. Read the risks and 'what to avoid' lines. For each one, find the source line behind it. Cut any line that is a guess about the prospect's suppliers, motives or politics.
6. Read the assumptions list. Add any Inferred item that is missing, and mark which ones you will confirm on the call.
7. Look at the Unknowns section and fill what you can in five minutes: a quick look at the company's latest news, or a question to a colleague who knows the account.
8. Choose your three questions for the call. Change the wording so it sounds like you.
9. After the meeting, update the CRM with what you learned and replace the unknowns you resolved.

## The prompt

```text
I am a sales rep preparing for a meeting. Write a one-page pre-meeting brief using only the material I paste below. Do not use outside knowledge about the company and do not guess. If something is not in the material, write "Unknown" and say what I could ask or check to find out.

Company: {{company_name}}
Contact: {{contact_name_role}}
About the meeting and what we sell: {{meeting_context}}

Company website text:
{{website_text}}

Contact's LinkedIn about text:
{{linkedin_text}}

Past emails with them:
{{past_emails}}

CRM notes:
{{crm_notes}}

Write the brief with these headings:
1. What they do: two or three plain sentences.
2. About the contact: role, what they appear to care about, and how they write (formal, brief, detailed).
3. Likely priorities: up to four. Label each "Stated" if the material says it, or "Inferred" if it is your reasoning from the material, with a short reason.
4. Three questions to ask: open questions that fit the meeting goal and cannot be answered from the material. Add one line on why each is worth asking.
5. Risks: up to four, such as a supplier already in place, budget or timing signals, a stalled earlier conversation, or a different decision maker.
6. What to avoid: topics, claims or wording to steer clear of, based on the material.
7. Unknowns: what the material does not tell us that matters for this meeting.

Rules: Keep it to one page, about 350 words, in short lines I can read on a phone just before the call. If the sources disagree, show both and say which is more recent when dates are given. Do not invent names, numbers, customers or news. Leave out personal details about the contact that have nothing to do with their work. At the end, list every assumption you made.
```

### Fill in

- `{{company_name}}`: The company you are meeting (for example: Kaveri Cold Chain Pvt Ltd, Pune)
- `{{contact_name_role}}`: The contact's name and job title (for example: Rohan Deshmukh, Head of Operations)
- `{{meeting_context}}`: Date, length, what you sell and what you want from the meeting (for example: First 30-minute video call on Tuesday 18 November. We sell TrackLine, software that sends automatic delivery status updates to customers by WhatsApp and email. Goal: understand how they handle delivery status queries and decide whether a pilot is worth proposing.)
- `{{website_text}}`: Text copied from the company's website (About, services, news) (for example: Kaveri Cold Chain is a Pune-based temperature-controlled transport company. We move dairy, frozen food and pharma products across Maharashtra, Gujarat and Karnataka with a fleet of reefer trucks. New: real-time temperature monitoring on all routes. Careers: hiring dispatch coordinators in Pune and Bengaluru.)
- `{{linkedin_text}}`: The contact's public LinkedIn about text (for example: Rohan Deshmukh. Head of Operations at Kaveri Cold Chain. I run dispatch, fleet and customer delivery commitments. Over a decade in logistics. Interested in reducing delays and keeping customers informed.)
- `{{past_emails}}`: Past emails or messages with the contact, personal details removed (for example: 9 Nov, Rohan to us: Saw your note. Our dairy customers keep calling to ask where their truck is. Happy to talk next week, but please keep it short. We already use a GPS vendor for the trucks.)
- `{{crm_notes}}`: Your CRM notes on this lead (for example: Lead came from our webinar on 28 Oct. Spoke briefly to dispatch coordinator Meena, who said two people answer status calls and WhatsApp messages by hand. No budget discussed. Do not know which GPS vendor they use.)

## Check the result

- Every item marked 'Stated' can be found in the pasted material. Pick two and find the sentence that supports each.
- Each 'Inferred' priority gives a short reason and connects to the goal of the meeting.
- Every risk and every 'what to avoid' line points back to something in the sources, such as a named supplier or a request to keep the call short. Guesses about competitors or office politics are removed.
- The note on how the contact writes is based on their own emails or messages, not on their LinkedIn text.
- The lead source and any earlier contacts from the CRM notes appear in the brief.
- The Unknowns section is not empty and includes at least one thing you would want to know before proposing anything.
- The three questions cannot be answered from the pasted material, do not assume the answer, and each connects to the goal of the meeting.
- No names, figures, customers or news items appear that are missing from your sources.
- The assumptions list names each inference the brief relies on, and each one is something you can confirm or correct on the call.
- The brief fits on one page and can be read on a phone in about two minutes.

## Watch out for

- Guessing presented as fact. The model may fill gaps with plausible statements, especially in the risks and 'what to avoid' sections, which the prompt does not ask it to label. Check each of these lines against your sources before relying on it.
- Thin assumptions lists. In testing, the models listed only some of their inferences. Treat the list as a starting point and add any Inferred item it leaves out.
- Old material. A website page or LinkedIn profile can be out of date. Note the date of each source in your paste where you know it, and treat older emails with care.
- Personal and customer data. Past emails and CRM notes often contain personal details. Use your company's approved AI workspace, paste only what the brief needs, and follow your own data rules under India's DPDP Act or GDPR. This is not legal advice.
- Over-reading a LinkedIn profile. A short about section says little about what a person wants. Treat the contact summary as a starting point and listen on the call.
- Confidential information. Leave internal pricing, discount limits and other companies' details out of the paste unless your policy allows it.

## Industry notes

- **saas:** Reps often run several short discovery calls a week, so the brief helps most with the unknowns: current tools, who signs off and what a trial would need to prove. Paste any product usage or trial notes into the CRM field.
- **professional-services:** Buyers are often partners or owners who judge you on how well you understood their practice. Use the brief to prepare questions about their clients and capacity, and avoid sounding as if you have read only the website.
- **manufacturing:** Company websites can be thin and out of date, so expect more unknowns. Use the brief to plan questions about plant, order flow and who decides purchases, and check them against your own site visit notes.

## Before and after

**Before:** The rep skims the company website, scrolls the LinkedIn profile and searches the inbox for old emails minutes before the call. Notes sit in different places, and the questions come out generic. Gaps in knowledge only show up during the meeting.

**After:** The rep pastes the same sources into one prompt and gets a one-page brief with priorities, three questions, risks and a list of unknowns. They check it against the sources and walk in knowing what they do not yet know.

## FAQ

**What if I only have the company website text?**

Paste it and write 'Not available' in the other fields. The brief will have more unknowns and fewer priorities, which tells you where to spend your discovery time. A short, honest brief is more useful than a confident one built on guesses.

**Can the AI look up the company by itself?**

Chat tools with web search can, but this prompt tells the model to use only what you paste, so every line can be traced. If you want wider research, do it yourself, paste the useful parts and run the prompt again.

**Is it safe to paste CRM notes and emails into an AI tool?**

That depends on your company's rules and the tool's settings. Use an approved workspace, remove personal details the brief does not need, and check your obligations under India's DPDP Act or GDPR. If you are unsure, ask whoever owns data policy before you start.

**Should I share the brief with the prospect or my team?**

Treat it as an internal preparation note. It can go into the CRM so a colleague can pick up the account. Do not send it to the prospect, because it contains inferences about them.

## Atul's note

The briefs that help are the ones that admit gaps. A rep who walks in knowing what is unknown asks better questions than one holding a confident guess. I suggest reading the brief once, crossing out anything you cannot trace to your own notes, and adding one thing you know that the AI could not.

## Tested on

- Claude Sonnet 5.5, 2026-11-14: pass
- GPT-6, 2026-11-14: pass
- Gemini 4, 2026-11-14: fail

[This page](https://atulsingh.co.in/ai-playbooks/pre-meeting-account-brief) · [Markdown copy](https://atulsingh.co.in/ai-playbooks/pre-meeting-account-brief.md) · [SKILL.md](https://atulsingh.co.in/ai-playbooks/pre-meeting-account-brief/SKILL.md)
