Build a one-page account brief from records you already hold
Forty minutes before a call, someone asks where things stand with an account. Everything is in the CRM — spread across two owners, a newsletter log and a property panel nobody has opened since the deal closed.
What you'll make
a one-page internal brief on one account, with a date on every line and the things the records don’t know listed as questions.
What you'll need
access to the account’s CRM records and permission to use them with AI at work, either through your CRM’s own assistant (HubSpot’s Breeze Assistant here) or by pasting excerpts into ChatGPT, Claude, Copilot or Gemini. Allow about twenty minutes for the first one.
Example result.
Current position: Customer. Annual value field £31,000, last updated 18 Feb 2025; contract value not checked.
Open items: Expansion deal open, target close 30 June 2026 (passed). Two tickets open, details unread.
Last meaningful contact: 3 May 2026 note (invoice PO reference). 11 July was an automated newsletter.
Recent changes: Morgan became owner, 1 September 2026.
Questions to ask: Was the PO request resolved? Where did you get to on the second site?1. Name the conversation and set out the page
Write one line naming the account, the reader and the upcoming call, and pick a cutoff date: the day you stopped checking. Then set out the page before you generate anything:
ACCOUNT BRIEF — [account] — for [purpose] — records checked to [cutoff date]
Current position (one sentence, with the date it became true)
Open items (deals, tickets, commitments, each with a date)
Last meaningful contact (who, when, what was said)
Recent changes (anything that moved recently)
Questions to ask (what the record can't tell you)Two limits belong here. Renewal values, contract terms and discounts live in the agreement and the billing system, not a CRM field, so read any number you’ll say out loud from there. And brief the company, not a person: a profile of a named individual built from activity history and the tone of old emails is a different job with different obligations.
Why this works: the last heading is the one that earns the page. Every brief has gaps; writing them down turns a silence into questions you can ask.
What you should see: an empty page with a purpose line, a cutoff date and five headings.
2. Generate the summary and ask for a dated draft
In HubSpot, open the company record. In the upper right of the left sidebar, open Actions and select Summarize. The summary appears in the Breeze Assistant panel. HubSpot says it’s generated automatically and can’t be customised: it reflects what people logged, not what happened.
If your CRM has no assistant, paste labelled excerpts from the record into a chat instead. That route doesn’t connect the assistant to your CRM, and confidential records shouldn’t move to a different service because it’s convenient.
Then ask, in the same panel or chat:
Using only this record, prepare an internal account brief for [account] for [purpose], covering records up to [cutoff date]. Use these headings: Current position, Open items, Last meaningful contact, Recent changes, Questions to ask. Put a date and a source beside every factual line. If a fact has no date, write "date unknown". Keep contradictory entries visible.[account], [purpose] and [cutoff date] are the same as your purpose line. Name the account exactly so similarly named records don’t get mixed.
Why this works: forcing a date beside every line catches the undated figure that sounds current. “£31,000, last updated February 2025” is a different sentence from “£31,000”.
What you should see: a draft under your five headings, some lines with dates, some marked “date unknown”.
3. Ask the follow-up that finds what isn’t there
The summary tells you what’s in the record. This follow-up finds the other half:
Using only this record, answer these four questions. Where the record does not contain the answer, write exactly "not in the record". Do not infer it from similar accounts or from what is typical.
1. When was the last two-way contact with anyone at this account, and who was it with?
2. Which open items have a date that has already passed?
3. Which contacts on this record have had no activity in the last 12 months?
4. What is the most recent thing anyone wrote in their own words, as opposed to a field that was updated?- “Using only this record” stops the assistant borrowing a pattern from other accounts to fill a gap.
- A required “not in the record” gives it a legitimate way to produce nothing. When the only acceptable output is content, you get content.
- Question 4 is the one that surprises people. Workflows and imports update fields; people who were in the room write sentences.
Why this works: each question targets a different way a record looks fresher than it is.
What you should see: four short answers, some of them “not in the record”. Each of those goes under Questions to ask.
4. Write the final brief yourself
The AI draft is your input, not the brief. Open your page from step 1 and type the brief in your own sentences, in the order that matters for the call. Keep the CRM and the original notes open as you go.
Writing the sentence is what makes you notice that two of your facts contradict each other, or that the main contact hasn’t appeared since spring. A summary you only read doesn’t do that.
Keep the brief internal. It holds your commentary, your pipeline position and your view of the customer. Briefs leak by being forwarded.
Why this works: the brief shows your judgement rather than the summary’s confidence.
What you should see: a page that fits on one screen, where every important line is either dated and sourced or written as a question.
Check the result
For every line that could change what you say on the call, open its source and ask:
- Is the date when something happened, when someone entered it, or when something is expected?
- Does the source record an agreement, a suggestion or an internal assumption?
- Has a later entry changed the position?
- Is anything missing because it’s in an attachment or activity type the assistant couldn’t read?
The usual failure: the draft promotes record activity into a conversation, or an old field into a current fact. An automated email becomes “our July conversation”; a value field updated last year becomes “renews at £31,000”. Spot it by checking what each date refers to and whether a person wrote anything on that day.
Recheck this brief statement: [sentence]. Show the supporting source text and say what its date refers to. If it doesn't establish the claim, replace the sentence with the narrower supported fact or an open question. Keep the rest of the brief unchanged and do not use other accounts.[sentence] is the line you couldn’t support. Check the revision yourself; if the source stays unavailable, keep that gap on the page.
Worked example: Pennington Logistics
Fictional example. A service call on 7 October 2026, using records checked to 6 October.
Company record, Pennington Logistics:
Customer status. Owner: Morgan, assigned 1 September 2026.
Annual value field: £31,000. Last updated 18 February 2025.
Last activity field: 11 July 2026.
Account note, 3 May 2026:
Customer asked whether invoices can show a purchase-order reference.
Additional site discussed. No site decision or timetable recorded.
Activity, 11 July 2026:
Automated service newsletter sent. No reply logged.
Expansion deal: Open. Target close date 30 June 2026. Not updated since.
Support: Two open tickets. Ticket detail not supplied.The first draft’s Current position read: “Pennington is expanding and renews at £31,000 after our July conversation.”
- The failure. Three claims, none established. The expansion was discussed, not decided. The £31,000 is a field from February 2025, not a contract. “July conversation” is a newsletter.
- The repair. The follow-up’s question 4 returned the 3 May note as the most recent sentence anyone wrote. So the account has been touched in July and talked to in May. The recheck prompt on the draft sentence returned: “Customer. Annual value field £31,000, last updated 18 February 2025; current contract value not established.” The expansion became a question: “Where did you get to on the second site?”
- The internal action. The deal’s target date passed in June and nobody moved it. That’s for Morgan to fix, not something to raise with the customer.
The finished brief is the example result at the top of this page.
Task kit for this job: Download (ZIP) · Reusable instructions
Go deeper
Optional training: Know what the summary can't see
In HubSpot, a Super Admin controls what the assistant can read at Settings › Account management › AI › Access. CRM data and Customer conversation data are on by default; Files data is off. If a commitment lives in an attached PDF and files data is off, the summary can’t see it, and it won’t mention the gap. With Sensitive Data turned on, some activities, such as calls and sales emails, can’t be summarised at all.
Ask your admin for the current settings rather than changing them for this job, then add a coverage note to the brief:
Add a short coverage note listing the source types and date range you used, plus anything you could not read. Identify which brief points depend on a summary rather than an original entry. Do not claim you searched all CRM history.Optional training: When the record is thin
If four headings have a line each and Questions to ask is long, the brief hasn’t failed. It’s accurate, and it tells you the call is about finding things out. The temptation is to loosen the prompt until something fuller comes back. Everything you get that way is exactly the content you removed the constraint to avoid.
Making the next brief easier starts with how call notes are written: what was discussed, what was agreed, who agreed it and what happens next. Write a CRM call summary the next person can actually use covers that. For news about the company from outside your records, see Research an account before a call without inventing the news.