Meeting Prep Workflow: A Research Brief Before Every Sales Call
Reps walk into calls under-prepared because research takes twenty minutes and the calendar is full. The workflow watches the calendar, and for every external meeting assembles a one-page brief from the CRM, the company's site and news, LinkedIn-level role data, past interactions and product usage — then has the AI agent write the three angles worth raising. It lands in Slack an hour before the call.
Written by Max Zeshut
Founder at Agentmelt · Last updated Sep 11, 2026
The problem
Research is skipped or shallow. Reps miss that the prospect just raised a round, that a colleague spoke to them last quarter, or that the account is at 90% of its plan limit. Calls open with questions the CRM already answered.
What changes when it runs
Every external call has a brief: who is attending and what they do, what the company does and what changed recently, the relationship history, live account signals, and three suggested talking points. Reps spend the twenty minutes on the call, not before it.
Trigger, then 7 steps
Trigger
Calendar scan (hourly) + meeting webhooks
Google or Microsoft calendar scanned for meetings with external attendees in the next 24 hours; new bookings via webhook.
Find upcoming external meetings
HTTP RequestMeetings in the next 24 hours with attendees outside the company domain; internal-only meetings are ignored.
Identify attendees and account
HubSpotContacts and company matched in the CRM; deal stage, owner, open tickets and last interactions pulled.
Research the company
HTTP RequestCompany site (about, product, pricing pages), recent news, funding and hiring signals from enrichment and news APIs; product usage or billing signals for existing customers.
Research the people
HTTP RequestRole, tenure and public professional profile per attendee from enrichment providers; recent public posts where available.
Write the brief
AI AgentOne page: company in two lines, what changed recently, attendees and roles, relationship history and open items, live account signals, and three suggested angles tied to the evidence. Nothing without a source.
Deliver
SlackPosted as a DM to the rep an hour before, and attached to the calendar event and the CRM deal.
Capture the outcome
WaitAfter the meeting a one-question prompt ('how did it go, next step?'); the answer is logged to the CRM so the next brief includes it.
Data it touches
- Calendar (Google Workspace, Microsoft 365)
- CRM (HubSpot, Salesforce, Pipedrive)
- Enrichment and news (Clay, Apollo, Clearbit, news APIs)
- Product usage / billing for existing accounts
Guardrails
- Only public and first-party data; no scraping behind logins, no personal data beyond professional role.
- Every statement in the brief carries a source; the agent is instructed to omit rather than guess.
- Briefs go only to the rep and the CRM; they are not forwarded externally.
- Enrichment credits are spent only for meetings that survive the external-attendee filter.
What a good brief contains
Not a dossier — one page a rep reads in three minutes. Company: what they do, size, what changed in the last quarter. People: role, tenure, anything public and relevant. History: every touch your company has had, open tickets, open deals. Signals: usage, plan limits, renewal date for customers; intent signals for prospects. Angles: three specific things worth raising, each tied to one of the above. The agent's discipline is to write only what has a source.
The outcome loop
The post-meeting prompt is the part reps like least and the part that makes the next brief better. One question, one line, logged to the CRM — and the next person to meet that account starts with it. Teams that keep this loop running end up with a CRM that reflects reality, which no amount of nagging achieves.
Tools in the stack
| Tool | Role in this workflow |
|---|---|
| n8n | Calendar scan, data assembly, delivery, outcome capture |
| Claude | Brief writing with sourced angles |
| HubSpot / Salesforce | Relationship history |
| Clay / Apollo | Company and people data |
Want this running without building it?
Automation workflow
$197/month
We set up, host and maintain this workflow on n8n and connect it to your tools. Setup included, cancel monthly, you keep the JSON.
Custom build
$2,500–4,000 one-time
Your systems, your rules, your edge cases. A one-off build on Claude and n8n, delivered with documentation and a walkthrough.
Per team of up to ten reps and 400 external meetings a month; enrichment credits billed by the provider. Custom research sources or CRM objects are a custom build.
Frequently asked questions
Does it work for customer success and executives too?
Yes — the same brief with account-health and usage signals for CSMs, and a lighter version for executives' external meetings.
Which calendars and CRMs?
Google Workspace and Microsoft 365 calendars; HubSpot, Salesforce, Pipedrive and Attio CRMs.
Is it compliant with privacy rules?
The brief uses public professional information and your own first-party data. No personal data beyond role is collected or stored, and enrichment providers are used within their terms.
Case study
AI Executive Assistant Agent for a PE Firm: 12 Hours/Week Reclaimed Per Partner
How a mid-market private equity firm deployed AI executive assistants to automate scheduling, deal flow coordination, and portfolio reporting for its 6 partners.
The pillar
AI Sales Agent
Research leads, personalize outreach, and book meetings—deploy in minutes, no code required.