SkillBrief every meeting
Turn meeting notes into a follow-up and CRM updates
From a transcript or notes: the follow-up email in your voice, the CRM note, next steps with owners and dates, and every promise flagged.
meeting-follow-up/SKILL.mdDownload- name
meeting-follow-up- description
- Use this skill when a sales meeting has just ended. From the transcript or your notes it produces the follow-up email in your voice, the CRM note, next steps with owners and dates, and flags for everything either side promised. You review it all; nothing is sent or saved without your yes.
- license
- CC-BY-4.0
Turn meeting notes into a follow-up and CRM updates
This skill turns a meeting transcript or rough notes into four things: the follow-up email, the CRM note, the next steps with owners and dates, and a list of every promise made in the room. Use it the same day as the meeting, while the details are fresh and the buyer still remembers the conversation. The checks at the end make sure nothing promised gets lost and nothing unsaid gets written.
Inputs
- The transcript or the notes. A transcript from the notetaker the team uses, or the seller's own notes. With a meeting tool connected, take the latest external meeting unless the user names one. Without one, ask the user to paste.
- Meeting date and attendees, with roles. The date anchors every "next week" in the conversation.
- The CRM record (read), or the deal pasted by the user: stage, amount, close date, next step, contacts.
- Voice guide and the language of the email (see the write-in-my-voice skill).
- What must stay out of writing: internal pricing, a discount not yet approved, anything said off the record.
Steps
- Read the whole transcript first. Identify the speakers and the meeting date. With notes only, mark every extracted item as "from notes" so the user knows it was not checked against a recording.
- Extract, with timestamps. Needs in the buyer's own words; decisions; numbers (volumes, budget, dates); objections; how they will decide and who else is involved; next steps.
- List every promise. Ours ("I'll send the case study"), theirs ("we'll check with finance") and vague ones ("we'll look into it"). Each gets an owner and a date: the one said in the meeting, or a proposed date marked as proposed.
- Draft the follow-up email. Under 150 words. A specific subject. Two or three lines on what they need, in their words; what was agreed; next steps with owners and dates; what is attached, with a reminder to attach it. Nothing that was not said in the meeting, and nothing from the "keep out" list.
- Draft the CRM note. Dated, five to eight lines: needs, decision process and people, timing, budget if discussed, risks, next step.
- Propose CRM changes. Stage (only if the meeting met the stage's rule), next step and date, close date if the buyer gave one, new contacts for attendees not in the CRM, and one task per promise we made.
- Run the checks. Every promise in the transcript appears in the email or in a task. Every number in the email matches the transcript. No claim, price or date appears that nobody said. Show the result.
- Apply after approval. With approval, save the email as a draft in the user's mailbox (never send it), add the note and create the tasks. Read the record back to confirm.
Output
Meeting: Summit Ag Supply · Thu 2026-11-19 · 45 min · transcript
Attendees: [Name] (VP Operations), [Name] (Director of Logistics), you
EMAIL (128 words)
Subject: receiving at the Fresno site, next steps
[draft in the seller's voice]
Attach before sending: sample receiving report (promised at 18:40)
CRM NOTE (2026-11-19)
Needs: receiving at the new Fresno site must handle about 60 inbound trucks a week
from March (VP Ops, 12:10). Decision: VP Ops and the CFO; the CFO signs above
$25,000 (22:05). Timing: decision before the January budget review. Risk: they
trialed a similar tool in 2025 and dropped it (31:30). Next: scoping call 2026-12-02.
NEXT STEPS
| Owner | Action | Due | Source |
| You | Send sample receiving report | 2026-11-20 | 18:40 |
| You | Send scoping call invite | 2026-11-20 | 41:15 |
| Dir. Logistics | Share current receiving volumes | 2026-11-27 | 38:02 |
| VP Ops | Confirm whether the CFO joins | proposed 2026-11-30 | 42:00 |
PROMISES
Ours: 2 (both in the email and as tasks)
Theirs: 2 (named in the email's next steps)
Vague: "we'll think about the rollout order" (27:12), confirm in the scoping call
CRM CHANGES (nothing applied)
1. Stage: Qualified to Scoping
2. Next step: Scoping call · you · 2026-12-02
3. New contact: [Name], Director of Logistics
4. Tasks: the two "You" rows above
CHECKS: promises covered 4 of 4 · numbers match · no unsaid claims
Approve: "draft email, 1 to 4" or name the lines.Guardrails
- Reads: the transcript or notes, the attendee list, the CRM record, the voice guide.
- Writes: with approval only: an email draft in the user's mailbox, the CRM note, field changes and tasks.
- Asks before: creating the draft, every CRM change, adding contacts.
- MUST capture every promise, ours and theirs, with an owner and a date.
- MUST tie each fact in the note to a timestamp, or mark it "from notes".
- MUST respect the keep-out list and anything said off the record.
- NEVER send the email. It is saved as a draft for the seller to send.
- NEVER quote the buyer's words back in a way that exposes internal remarks they made to colleagues in the meeting.
- NEVER add a price, discount, date or commitment that was not said in the meeting.
Sources
- How can a founder sell without a sales team?, ALTARA Insights: why every outcome goes into the CRM.
- How do I run outbound without hiring an SDR?, ALTARA Insights: the founder's job is judging fit and taking the calls.
Made by ALTARA, the AI sales agent your team texts. More skills: https://www.altaratech.com/store
Use it with
-
Runs in ALTARAPlaybook Keep the CRM currentKeep the CRM current from your chats with ALTARAALTARA reads client chats and your call notes, prepares stage, note and next task, and saves only after your yes. Free, with undo. 5 minutes at the end of each dayRun it →
-
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 →
-
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 →