Brief a meeting in five minutes
A five-minute pre-meeting brief: the account, the people, dated news with sources, CRM history and three questions to ask.
meeting-brief/SKILL.mdDownload- name
meeting-brief- description
- Use this skill when a sales meeting is coming up. It returns a brief you can read in five minutes: the account, the people, recent news with dates and sources, open deals and history from the CRM, and three questions to ask. Every fact carries a date and a source; gaps are marked as gaps, never filled.
- license
- CC-BY-4.0
Brief a meeting in five minutes
This skill prepares a one-page brief for a sales meeting: who the account is, who will be in the room, what changed at the company recently, what your team already knows from the CRM, and three questions worth asking. It stays under 400 words so it can be read in five minutes, and every fact shows where it came from.
Inputs
- The meeting: the calendar event (title, time, attendee emails) or the user's description. With calendar access, take the next external meeting unless the user names one.
- The purpose: first call, demo, negotiation, renewal or something else. The questions depend on it.
- CRM access (read) to the account, its deals, notes and the last activities. Without it, ask the user to paste the deal and the last few notes, or to say there is no history.
- What you sell, in one sentence.
- Web access for public news. Without it, the brief covers the CRM and what the user pastes, and says so.
Steps
- Identify the account and the people. Use the email domain of the external attendees and ignore internal ones. If an attendee uses a personal email, ask who they are.
- The account in two lines. What the company does, from its own website. Size and location only from the company's site or an official filing; for US public companies, search SEC EDGAR full-text search. No estimated headcount or revenue.
- The people. For each external attendee: title and when you confirmed it, time in the role if their profile shows it, and every past interaction in the CRM with dates. Add a recent public post or talk only if it is about their work.
- Recent news, last 90 days. Up to five items: funding, leadership changes, hiring for roles that matter to you, contracts won, new sites, events. Each with its date and link. If there is nothing, write "No news found in the last 90 days" and move on. Do not pad.
- From the CRM. Open deals with stage, amount, close date and next step; the last three touches; lost deals and their reason; anything your team promised and has not delivered.
- Three questions. Open questions aimed at what you do not know and need: who decides and how, the timing behind the signal, how they handle the problem today. Tie one to the news. The third confirms the next step.
- Goal and next step. One line on what a good outcome is, and the next step to propose before the meeting ends.
- Cut to five minutes. Under 400 words. Cut adjectives first, then the oldest news.
Output
Brief · Tue 2026-11-24 10:00 to 10:30 · Pinecrest Engineering · first call
Goal: agree whether a pilot makes sense, and book the scoping call.
ACCOUNT
Civil and survey engineering firm, Austin, Texas (company website, read 2026-11-23).
PEOPLE
Dana Ruiz, Director of Field Operations · title confirmed 2026-11-23 (company site)
CRM: replied to our email of 2026-11-12; no earlier contact.
[Name], Survey Manager · title confirmed 2026-11-23 (LinkedIn) · not in CRM
NEWS (last 90 days)
2026-11-12 · posted three Survey Crew Chief openings [link]
2026-10-02 · announced a new office in San Antonio [link]
CRM
Deal: Field data pilot · Qualified · $18,000 · close 2026-12-15 · next step: this call
Last touches: 11-12 email (signal) · 11-14 her reply · 11-17 meeting booked
Lost before: none · Open promises: send the sample report (promised 11-14, not sent)
ASK
1. How are you planning to process the field data once the three new crews start?
2. Who else would weigh in on a pilot, and how have you chosen tools like this before?
3. If this is worth exploring, who should join a scoping call next week?
GAPS: company size not published · no budget information in the CRMGuardrails
- Reads: the calendar event, the CRM record for the account and its contacts, public pages about the company and the attendees' professional profiles.
- Writes: nothing. The brief stays in the chat or goes where the user asks.
- Asks before: saving the brief to the CRM or a document, and before reading any calendar other than the user's.
- MUST date and source every fact, and mark what is unknown as a gap.
- MUST flag any promise your team has not kept, at the top of the CRM section.
- MUST keep the brief under 400 words.
- NEVER include anything about an attendee's personal life, family, health, politics or religion.
- NEVER estimate revenue, headcount or budget and present it as fact.
- NEVER contact an attendee from this skill.
Sources
- EDGAR Full Text Search, US Securities and Exchange Commission: filings for US public companies (read 2026-11-20).
- Funding and leadership changes and Hiring signals, ALTARA Insights: which news is worth a line in the brief.
Made by ALTARA, the AI sales agent your team texts. More skills: https://www.altaratech.com/toolkit
Use it with
-
Connection Run the cadenceGmail, Google Calendar and DriveALTARA sends the sequences your team approved from a separate, warmed inbox. Your own AI reads your Gmail, Calendar and Drive to prepare the calls. Sending inbox for sequencesSee how →
-
Connection Run the cadenceOutlook, Teams and SharePointYour team texts ALTARA in Microsoft Teams, and it sends approved sequences from a warmed inbox. Your own AI reads your Outlook, Teams and files. Sending inbox for sequencesSee how →
-
Connection Keep the CRM currentHubSpotALTARA reads one HubSpot pipeline, read-only, and sends each change with a link to the deal. Your own AI reads the same records through HubSpot's MCP. Reads (rolling out)See how →
-
Connection Keep the CRM currentSalesforceThe ALTARA team connects Salesforce on request, read access first. Your own AI reads the same records through Salesforce's hosted MCP servers. Connected on requestSee how →
-
Connection Keep the CRM currentPipedriveALTARA keeps your Pipedrive pipeline current from the chat, after your yes. Your own AI reads the same deals through Pipedrive's MCP server. Reads and writesSee how →