Prepare a one-page account brief before a sales meeting
What this does
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.
On this page
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.
Saves about 30 minutes per meeting

From my practice
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.
What to have ready
- 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 removedKeep 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.
Build your prompt
- 1. Gather your inputsHave the items above to hand.
- 2. Fill in the formYour prompt updates as you type.
- 3. Copy or open in your AIClaude, ChatGPT or Gemini.
- 4. Review before you sendCheck it against your notes.
Your prompt · 0 of 7 filled
Gemini cannot be filled from a link, so the prompt is copied first. Paste it with Ctrl+V or Cmd+V.
Use it as a skill
Add this playbook to your assistant once, then ask for it by name.
How to install
- Claude: download the zip and upload it as is under Settings, Capabilities, Skills.
- Other assistants: open SKILL.md, copy it, and paste it into the assistant's custom instructions or project.
- Ask for the playbook by its task, and give it your details when it asks.
The skill is plain text with no scripts, links or commands. Read SKILL.md before you install it, and use a company-approved AI workspace. Need help setting it up? Book a call.
See a real result
Sample input: Kaveri Cold Chain Pvt Ltd, Pune · Rohan Deshmukh, Head of Operations · First 30-minute video call on Tuesday 18 November. We sell…
Tue 18 Nov, 30 min video call. Contact: Rohan Deshmukh
1. What they do
- Pune-based temperature-controlled transport.
- Moves dairy, frozen food and pharma in Maharashtra, Gujarat and Karnataka using reefer trucks.
- Website says real-time temperature monitoring is now on all routes.
2. About the contact
- Head of Operations: runs dispatch, fleet and customer delivery commitments.
- Cares about reducing delays and keeping customers informed.
- Writes briefly and directly. Asked us to "keep it short."
3. Likely priorities
- Fewer "where is my truck" calls from dairy customers: Stated (his 9 Nov email).
- Fewer delays, customers kept informed: Stated (LinkedIn).
- Less manual status handling: Inferred. Meena said two people answer calls and WhatsApp by hand.
- Dispatch capacity: Inferred. They are hiring dispatch coordinators, which may mean workload pressure.
4. Three questions
- "What happens today when a customer asks where their truck is?" It shows the process, volume and pain, and none of that is in the material.
- "What does your GPS vendor provide, and can customers see any of it?" It shows whether we overlap with or complement the vendor.
- "What would need to be true for you to try something new, and who else would be involved?" It surfaces success criteria and the decision maker.
5. Risks
- Existing GPS vendor may offer, or add, customer updates.
- Limited time and patience: he asked for brevity.
- No budget discussed.
- Decision maker unconfirmed.
- Thin history: a webinar lead and one short chat with Meena.
6. What to avoid
- Pitching TrackLine as a GPS replacement.
- Guessing at their systems, volumes or customers beyond dairy.
- Long demos or overrunning 30 minutes.
- Quoting savings or numbers we can't source.
- Assuming Rohan knows what Meena told us.
7. Unknowns
- GPS vendor: ask Rohan, or check with Meena.
- Call volume and which customers call: ask.
- Budget and timing: ask.
- Decision maker: ask.
- What "your note" referred to: check our sent email.
- Whether customers prefer WhatsApp or email: ask.
Assumptions
- "Saw your note" refers to our outreach after the webinar.
- Meena's comment is current (it is undated).
- Rohan's style is judged from one email and a short bio.
- Customers' calls go to Kaveri's own staff.
- The sources do not conflict.
1. What they do
Kaveri Cold Chain is a Pune-based temperature-controlled transporter of dairy, frozen food and pharma products across Maharashtra, Gujarat and Karnataka. Its website describes a reefer fleet and real-time temperature monitoring on all routes.
2. About the contact
Rohan Deshmukh, Head of Operations, runs dispatch, fleet and customer delivery commitments. He explicitly values reducing delays and keeping customers informed. His email is brief and direct; he asks to keep the call short.
3. Likely priorities
- Stated: Reduce delays — named in his LinkedIn text.
- Stated: Keep customers informed — named in LinkedIn; his email reports dairy customers calling for truck locations.
- Inferred: Reduce manual status handling — Meena says two people answer calls and WhatsApp messages manually.
- Inferred: Understand fit alongside existing GPS — Rohan specifically flags their current vendor.
4. Three questions to ask
-
Walk me through a dairy customer’s status query, from arrival to resolution. Where does it get difficult?
Why: Reveals workflow and friction beyond the known manual handling. -
How do you use your GPS system to answer queries, and what customer updates does it already provide?
Why: Establishes overlap and possible gaps before positioning TrackLine. -
What would you need to see from a pilot to consider it worthwhile, and who would help evaluate it?
Why: Identifies success criteria and participants without assuming buying authority.
5. Risks
- Existing GPS supplier: capabilities and overlap are Unknown.
- Budget: Unknown; none discussed.
- Buying authority: Unknown; Rohan’s operational role does not establish approval power.
- Limited attention: first call is 30 minutes, and Rohan explicitly requests brevity.
6. What to avoid
Avoid a long demo or generic pitch. Do not imply GPS replacement, confirmed integration, temperature-monitoring functionality or guaranteed savings. Do not treat hiring as proof of growth or operational strain.
7. Unknowns
- Unknown: Query volume, time spent and business impact. Ask Rohan for a typical day.
- Unknown: GPS vendor, data access and customer-update capabilities. Ask Rohan; check vendor documentation.
- Unknown: Budget, approver and pilot timing. Ask about evaluation and approval steps.
- Unknown: Customers’ preferred update channels. Ask whether WhatsApp and email would fit.
Assumptions made: Only the two labelled inferences above: reducing manual handling and assessing GPS fit may be priorities. No other assumptions made.
Was this playbook helpful?
Want this set up for your team?
I can fit this playbook into your CRM, helpdesk or inbox and train your team to use it.
Book a 30-minute reviewReview before you send
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.
Tips for your industry
This playbook works for any business. These notes help you adapt it.
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.
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.
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.
Questions people ask
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.
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.
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.
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.
Last checked · Updated