Sales
Event-driven
Meeting Prep & Follow-up Agent
Arrive ready. Leave aligned.
Prepare for a sales meeting, then turn the notes into a follow-up email and suggested CRM updates.
Prepare for Northstar's meeting, then draft a follow-up from the notes.
- Assemble calendar and CRM preparation
What it does
Keep the conversation moving after the meeting.
Prepare for a sales meeting, then turn the notes into a follow-up email and suggested CRM updates. Built for account executives and sales teams.
Bring the context
Choose the meeting, account details and any previous conversation notes. Earlier conversations and company updates can sharpen the meeting brief.
Capture what was agreed
Summarise what matters before the call, then extract agreed actions from the meeting notes.
Review the follow-up
Get a meeting brief, follow-up email draft and proposed updates for your sales records.
How it works
Prepare for a sales meeting, then turn the notes into a follow-up email and suggested CRM updates. Built for account executives and sales teams.
- Approved documents and context
- Approved offering and delivery limitations Commitment extraction schema: owner, action, due date, evidence CRM stage criteria and allowed field mappings Optional: attributed excerpts from previous calls and open commitments, to avoid repeating questions and surface unfinished actions. Optional: recent official company announcements and the account's current product usage, where access is permitted, to identify relevant discussion points.
- Keep the conversation moving
- Start with a concise account brief and review a recap email drafted from the meeting notes after the call.
- Keep next steps out of scattered notes
- Review exact CRM updates supported by the conversation, ready for the account owner to approve.
- Google Calendar · Read meeting and attendee identity (read)
- Anchor preparation and deduplication to the meeting event.
- Google Drive · Read approved notes revision (read)
- Extract attributed commitments and exact date evidence.
- HubSpot · Read account and prepare field patch (draft)
- Compare current CRM fields with supported changes.
- Gmail · Prepare follow-up email (draft)
- Create a reviewable message without sending it.
- Human review and permissions
- Account owner approves email recipients and body. CRM field changes require a separate approval against the displayed record revision.
01Gather the context
Bring together the relevant information from Google Calendar, Google Drive, HubSpot, Gmail.
02Check what matters
Summarise what matters before the call, then extract agreed actions from the meeting notes.
03Prepare the result
A short account brief before the call and an email recap drafted from the meeting notes. Complete email with supported owners and dates.
04Review proposed changes
Account owner approves email recipients and body. CRM field changes require a separate approval against the displayed record revision.
Integrations
Calendar & meetings
Google Calendar
Microsoft Outlook
Documents
Google Drive
Microsoft OneDrive
CRM
HubSpot
Salesforce
Gmail
Microsoft Outlook
Choose the platforms your team already uses—you don’t need every example shown. Confirm the required features and configure access during implementation.
What you get
Spend less time preparing for sales calls and turning the conversation into follow-up work.
- Keep the conversation moving
- Start with a concise account brief and review a recap email drafted from the meeting notes after the call.
- Keep next steps out of scattered notes
- Review exact CRM updates supported by the conversation, ready for the account owner to approve.
More for sales teams
Account Research
Turn company information and sales notes into a short brief before contacting an account.
Inbound Lead Qualification
Review new enquiries against your ideal customer criteria and suggest the next step.
Proposal Draft Builder
Turn agreed customer needs into a proposal draft with scope, price, timing and exclusions.
Start with a blueprint. Build it around your business.
We’ll adapt it to your workflows, connect your systems and build an agent your team can put to work.
30 minutes. One bottleneck. Leave with a clear system concept.