Agendas, minutes and recaps

What a meeting leaves behind: the agenda before it, the minutes and recap after it, and the decisions and action items a team can find a month later.

Practical guides to running meetings that end with a readable record, written for the person who hosts them.

AI note taker for Google Meet: the ways to get notes from a Meet call, and what each leaves the team with (2026)
Meetings & recaps

AI note taker for Google Meet: the ways to get notes from a Meet call, and what each leaves the team with (2026)

An AI note taker for Google Meet is one of four things: Gemini's own Take notes for me, a notetaker bot that knocks and sits in the participant list, an app that records on your device with no bot, or a meeting room with the notetaker built in. Each one leaves something different behind the call — where the notes land, who receives them, which Workspace edition it needs, in which language they read, and what the guest who knocked walks away with. The four ways by the vendors' own documentation, a verdict table, and how to choose in 30 seconds.

The Mind.com Team

AI note taker for Microsoft Teams: the ways to get notes from a Teams meeting, and what each leaves the team with (2026)
Meetings & recaps

AI note taker for Microsoft Teams: the ways to get notes from a Teams meeting, and what each leaves the team with (2026)

An AI note taker for Microsoft Teams is one of four things: Teams' own Recap with Copilot or Facilitator, a notetaker bot that waits in the lobby and sits in the participant list, an app that records on your device with no bot, or a meeting room with the notetaker built in. Each one leaves something different behind the call — where the notes land, who receives them, in which language, and what the external attendee on the link gets. The four ways by the vendors' own documentation, a verdict table, and how to choose in 30 seconds.

The Mind.com Team

AI note taker for Zoom: the ways to get notes from a Zoom meeting, and what each leaves the team with (2026)
Meetings & recaps

AI note taker for Zoom: the ways to get notes from a Zoom meeting, and what each leaves the team with (2026)

An AI note taker for Zoom is one of four things: Zoom's own Meeting summary with AI Companion, a notetaker bot that sits in the participant list, an app that records on your device with no bot, or a meeting room with the notetaker built in. Each one leaves something different behind the call — where the notes land, who receives them, in which language, and what the guest on the link gets. The four ways by the vendors' own documentation, a verdict table, and how to choose in 30 seconds.

The Mind.com Team

Asynchronous work: how a team runs on written updates, voice notes and recaps — with a weekly template (2026)
Meetings & recaps

Asynchronous work: how a team runs on written updates, voice notes and recaps — with a weekly template (2026)

Asynchronous work is work that does not wait for a reply: each person posts the update, the question or the decision in writing, by a set time, and the others read and answer it when they are at their desk, not when it arrives. What stays live and what goes written, the four building blocks — the written update, the thread, the voice note and the recap of the one live call — a weekly template you can copy, three filled-in examples, where each piece lives in Teams, Zoom, Google Workspace and Slack, and how a channel keeps the whole week readable by each member in their own language.

The Mind.com Team

How to conduct an interview: structure, questions, scoring — and the write-up for the hiring team (2026)
Meetings & recaps

How to conduct an interview: structure, questions, scoring — and the write-up for the hiring team (2026)

To conduct an interview, run the same structure for every candidate: a short opening, the candidate's story, four or five competency questions with follow-ups, ten minutes for their questions, and a close that names the next step — then score against a rubric within the hour and write it up before the debrief. The structure minute by minute, the questions and the follow-ups that get the real answer, a scorecard you can copy, and what the write-up for the hiring team must contain. Also where the interview record lives in Teams, Zoom and Google Workspace, and how it comes back to a hiring team whose members read in different languages.

The Mind.com Team

AI meeting notes: how they are made, what they miss, and where the notes live after the call (2026)
Meetings & recaps

AI meeting notes: how they are made, what they miss, and where the notes live after the call (2026)

AI meeting notes are a summary a language model writes from the transcript of a call: what was discussed, what was decided and who does what, delivered after the meeting as an email, a document or a message. How the four steps work — capture, transcription, summary, delivery — the seven things a machine-written draft misses and a five-minute check before you send it, where the notes live in Teams, Zoom, Google Meet and the bot notetakers, and what happens to them once the call ends.

The Mind.com Team

Retrospective template: format, example — and how action items survive until the next retro (2026)
Meetings & recaps

Retrospective template: format, example — and how action items survive until the next retro (2026)

A retrospective template is a one-page format for the meeting where a team looks at how it worked over a sprint or a month and commits to one or two changes: last retro's actions checked first, what went well, what didn't, the changes chosen, an owner and a check date for each. The format, a sprint retrospective template you can copy, a filled-in example, four prompt sets and when each fits, where the retro lives in Teams, Zoom, Google Workspace and Slack — and how its actions come back at the next retro as done or not done, in every member's own language.

The Mind.com Team

Skip-level meeting: purpose, questions, cadence, and the notes that stay with the manager (2026)
Meetings & recaps

Skip-level meeting: purpose, questions, cadence, and the notes that stay with the manager (2026)

A skip-level meeting is a conversation between a manager and an employee who reports to one of that manager's direct reports — the middle layer is told, not present. What the meeting is for and what it is not, how to prepare it from both sides, a 30-minute template, fifteen questions by purpose, how often to hold one per report, the four ways it goes wrong — and where its notes live in Teams, Google Workspace and Slack, and in a channel the senior manager hosts, with every session readable later in each member's own language.

The Mind.com Team

One-on-one meeting questions: 60 questions by situation — the first meeting, a stalled quarter, a hard week — and how to keep the answers between meetings (2026)
Meetings & recaps

One-on-one meeting questions: 60 questions by situation — the first meeting, a stalled quarter, a hard week — and how to keep the answers between meetings (2026)

Sixty one-on-one meeting questions grouped by situation: the first meeting with a new report, a week when the list is short, a stalled quarter, a hard week, growth, feedback for the manager, a remote report, a report who manages others, the weeks before a review, and the questions a report asks a manager. Three per meeting, the second question behind each, and the answer said back as a sentence with a name and a date. Then the part question lists skip: where the answers live between meetings in Teams, Slack, Google Workspace and Zoom — and in a space where both of you read the running history in your own language.

The Mind.com Team

Internal wiki: tools, structure, and the wiki that grows out of the channel history (2026)
Meetings & recaps

Internal wiki: tools, structure, and the wiki that grows out of the channel history (2026)

An internal wiki is the set of pages a team writes for itself — how we do things, where things are, what we decided — kept in one place, organized by the questions people ask, with an owner and a review date on every page. The structure that keeps a wiki from growing into four hundred pages nobody opens, a page template you can copy, a worked example, where the wiki lives in Teams, Slack, Google Workspace and WhatsApp by documented facts — and how a channel that keeps every note, file and meeting recap becomes the wiki each member reads in their own language.

The Mind.com Team

Parent-teacher communication: what to send, how often, and one channel where every parent reads it in their own language (2026)
Meetings & recaps

Parent-teacher communication: what to send, how often, and one channel where every parent reads it in their own language (2026)

Parent-teacher communication is the set of messages a school sends about a class and about one child, and what it hears back: a welcome note that says how the school talks, a weekly class note, good news and a concern per child, logistics with a deadline, and the conference twice a year. What each message carries, how often it goes, templates you can copy and a filled-in weekly note, where the messages live in Teams, Google Workspace and WhatsApp and what each keeps — and how one channel per class gives every parent the whole year in their own language, with the record staying with the school.

The Mind.com Team

Remote team management: rituals, tools and the one habit that replaces status meetings (2026)
Meetings & recaps

Remote team management: rituals, tools and the one habit that replaces status meetings (2026)

Remote team management is running a team you do not share a room with: a fixed set of weekly rituals, the status round moved into writing, one place where decisions and history live, and rules for who is in the space — the team, the contractors and the clients. This guide gives the week's cadence, a copyable template for the written weekly that replaces the status meeting, three filled-in examples, and a documented comparison of what Teams, Zoom, Google Workspace and Slack keep after a meeting and for whom. It ends with one way the whole week lives in a channel every member reads in their own language.

The Mind.com Team

How to build a knowledge base in 30 days: structure, sources, ownership — and the base that grows out of what the team already says (2026)
Meetings & recaps

How to build a knowledge base in 30 days: structure, sources, ownership — and the base that grows out of what the team already says (2026)

To build a knowledge base, collect the questions the team actually asks for one week, group them into a structure of no more than seven sections, name an owner and a review date per entry, write the first twenty entries from what already exists — recaps, chat answers, the files people send each other — and publish where the team already reads. A 30-day plan week by week, an entry template you can copy, a worked example, where the base lives in Teams, Slack, Google Workspace and WhatsApp by documented facts — and how a channel that keeps every meeting, file and answer becomes the base each member reads in their own language.

The Mind.com Team

Patient intake: the form, the template, the questions — and the intake conversation the patient hears in their own language (2026)
Meetings & recaps

Patient intake: the form, the template, the questions — and the intake conversation the patient hears in their own language (2026)

Patient intake is everything a clinic collects and confirms before a new patient's first consultation: who they are and how to reach them, their history, medication and allergies, the consents the clinic needs, and the reason they came — on a form the patient fills in before the visit and in a short conversation that checks it. The sections of the form, a template to copy, the questions the intake conversation asks, a filled-in example, where the intake call happens in Teams, Google Meet and Zoom and what each keeps afterwards. And how a patient whose language is not the clinic's fills in the form and hears the intake conversation in their own language, with the notes coming back to the clinician.

The Mind.com Team

Patient communication: before, during and after the visit — the notes, the follow-up, and a visit the patient hears in their own language (2026)
Meetings & recaps

Patient communication: before, during and after the visit — the notes, the follow-up, and a visit the patient hears in their own language (2026)

Patient communication is everything a clinic says to a patient and hears back around one visit: the confirmation before, the explanation and the read-back during, the written summary and the follow-up after. How to run the three moments, the after-visit summary to copy, a filled-in example, where a video visit happens in Teams, Google Meet and Zoom and what each keeps afterwards — and how a patient whose language is not the clinic's joins from a phone and hears the whole visit in their own language, with the notes coming back to the clinician. Language barriers in healthcare and the language access plan are covered in the FAQ.

The Mind.com Team

Parent-teacher conference: how to run one, the questions, the form — and how a parent who speaks another language hears the whole conversation (2026)
Meetings & recaps

Parent-teacher conference: how to run one, the questions, the form — and how a parent who speaks another language hears the whole conversation (2026)

A parent-teacher conference is a short, scheduled meeting — usually 15 to 20 minutes — where a teacher and a parent go through one student's progress and agree what each side does before the next check-in. How to prepare and run one, the form to fill in, the questions each side asks, a filled-in example, where the conference happens in Teams, Google Meet and Zoom — and how a parent whose language is not the school's joins from a phone and hears the whole conversation in their own language.

The Mind.com Team

Knowledge sharing in the workplace: rituals, tools, and what gets lost between offices (2026)
Meetings & recaps

Knowledge sharing in the workplace: rituals, tools, and what gets lost between offices (2026)

Knowledge sharing in the workplace is the set of habits by which what one person knows — how a client is handled, why a rule exists, where the current file is — becomes something the rest of the team can find without asking. This guide covers the rituals that work (handover notes, demos, a question channel, a decision log, the post-mortem), the barriers behind each failure, a knowledge-entry template you can copy, and where shared knowledge actually lives in Teams, Slack, Google Workspace and WhatsApp. Then the part most guides skip: what is lost between two offices that read different languages, and how a channel that keeps every meeting, file and recap in each member's language closes that gap.

The Mind.com Team

Project status report template: weekly format, example — and how the report assembles itself from the recaps (2026)
Meetings & recaps

Project status report template: weekly format, example — and how the report assembles itself from the recaps (2026)

A project status report template is a fixed one-page format a lead fills once a week: overall status in one line, what moved since the last report, what is at risk, what needs a decision, and the open actions with an owner and a date. The weekly format, a template you can copy, a filled-in example, a shorter weekly report template for a team lead, and when a status meeting is still needed once the report exists. Then the mechanics: where the report is written in Teams, Zoom, Google Workspace and Slack — and how its facts come out of the meeting recaps instead of being retyped, in every member's own language.

The Mind.com Team

Process documentation template: how to document a process so it gets followed (2026)
Meetings & recaps

Process documentation template: how to document a process so it gets followed (2026)

A process documentation template is the fixed skeleton a process description goes into: a header with the ID, version, owner and review date, then the purpose and outcome, the trigger and the end state, scope, roles, the stages in order with who hands what to whom and what each stage leaves behind, exceptions, measures, related SOPs and a revision history. The format, a template you can copy, a worked example, the three reasons a documented process is not followed and what fixes each, where the process document and its walkthrough live in Teams, Zoom, Google Workspace and Slack — and how the process and every walkthrough of it stay readable for each member in their own language.

The Mind.com Team

How to write an SOP: steps, template, example, review cycle — and where the SOP lives after it is written (2026)
Meetings & recaps

How to write an SOP: steps, template, example, review cycle — and where the SOP lives after it is written (2026)

To write an SOP, pick one recurring job, watch the person who does it, draft the numbered steps first — each starting with a role and a verb and ending in a result someone else can check — add the exceptions and the records, give it an ID, an owner and a review date, test it on someone new to the job, then publish it where the team already reads. The seven steps in order, a one-page template you can copy, a worked example, the review cycle that keeps the procedure true, where the SOP lives in Teams, Zoom, Google Workspace and Slack after it is written — and how the procedure and every review of it stay readable for each member in their own language.

The Mind.com Team

How to delegate tasks: the handover that sticks — brief, owner, deadline, and a record both sides can read (2026)
Meetings & recaps

How to delegate tasks: the handover that sticks — brief, owner, deadline, and a record both sides can read (2026)

To delegate a task, hand over an outcome rather than a list of steps: a one-paragraph brief with the result, the deadline and the limits, one owner who says yes out loud, a check-in agreed before the work starts, and a handover kept where both sides can read it later. The method step by step, a brief template you can copy, a RACI chart for work that several people touch, what to delegate and what to keep, where the handover lives in Teams, Zoom, Google Workspace and Slack — and how the task comes back in the next recap as done or not done, in every member's own language.

The Mind.com Team

Remote work policy: template, sections, example — and the one channel the policy lives in (2026)
Meetings & recaps

Remote work policy: template, sections, example — and the one channel the policy lives in (2026)

A remote work policy is the written set of rules for working away from the office: who may, from where, when they must be reachable, how the team communicates, who pays for equipment and connectivity, how company data is kept safe, and how the policy itself is reviewed. The ten sections a usable policy carries, a template you can copy, a filled-in example for a company of forty across three countries, where the policy and its review live in Teams, Zoom, Google Workspace and Slack — and how one channel keeps the policy, every question about it and every change readable by each member in their own language.

The Mind.com Team

How to improve team productivity: fewer meetings, written status, and a history every office can read (2026)
Meetings & recaps

How to improve team productivity: fewer meetings, written status, and a history every office can read (2026)

To improve team productivity, keep only the meetings that decide something, move status into a written update posted by a set time, and keep one history of decisions and tasks that every member can read later. The three levers with the arithmetic behind each, a weekly status template you can copy, a 30-day plan, where the written status and the meeting record live in Teams, Zoom, Google Workspace and Slack — and how a channel keeps status, tasks and every recap readable by each member in their own language.

The Mind.com Team

SOP template: format, example, review cycle — and the SOP every member reads in their own language (2026)
Meetings & recaps

SOP template: format, example, review cycle — and the SOP every member reads in their own language (2026)

An SOP template is the fixed skeleton of a standard operating procedure: a header with the ID, version, owner and review date, then purpose, scope, roles, the numbered steps with who does what and what the result looks like, exceptions, records, references and a revision history. The format, a template you can copy, two filled-in examples, the review cycle that keeps a procedure true, where the SOP and its review live in Teams, Zoom, Google Workspace and Slack — and how the procedure and every review of it are read by each member in their own language.

The Mind.com Team

AI secretary for a team: what Mia does today in meetings, in the channel and with the calendar — and where today's tools stop (2026)
Meetings & recaps

AI secretary for a team: what Mia does today in meetings, in the channel and with the calendar — and where today's tools stop (2026)

An AI secretary is an assistant that carries the clerical work around a team's meetings: it prepares the brief, keeps the minutes, lists who promised what, puts the follow-up in the calendar and answers what was decided weeks later. What that job is, a brief you can copy to hand it over, what Microsoft Teams, Zoom and Google Workspace document under this heading today, and what InterMIND's Mia does on a paid plan — in the meeting, in the channel and from the assistant you already use.

The Mind.com Team

Recurring meeting: how to set it up in Google Calendar and Outlook, and how to keep its history in one place (2026)
Meetings & recaps

Recurring meeting: how to set it up in Google Calendar and Outlook, and how to keep its history in one place (2026)

A recurring meeting is one calendar event that repeats on a fixed pattern — weekly, every two weeks, monthly — so the whole series is created, invited and changed once instead of occurrence by occurrence. What a recurring meeting is and what a series is, the five settings every one needs, how recurrence is set in Google Calendar and Outlook and how one occurrence is changed without the rest, a series card you can copy, where each occurrence's notes and recap end up in Teams, Zoom, Google Workspace and Slack — and how a series keeps every session in one channel, readable by each member in their own language.

The Mind.com Team

Decision log template: how to record decisions so nobody re-litigates them — and where the log lives (2026)
Meetings & recaps

Decision log template: how to record decisions so nobody re-litigates them — and where the log lives (2026)

A decision log is the running record of what a team decided, one entry per decision: the decision in one sentence, who made it, the options rejected and why, what it rules out, the condition that reopens it, and a link to the moment it was made. The format, a template and a register you can copy, three filled-in entries, where the log lives in Teams, Zoom, Google Workspace and Slack — and how a decision taken in a meeting comes back as a line in the recap, marked agreed, open or disputed, in every member's own language.

The Mind.com Team

Meeting cadence: how often each meeting should happen, with a template for a team of 5 to 50 — and where each recurring meeting keeps its history (2026)
Meetings & recaps

Meeting cadence: how often each meeting should happen, with a template for a team of 5 to 50 — and where each recurring meeting keeps its history (2026)

Meeting cadence is the fixed rhythm of a recurring meeting — how often it happens, on which day and hour, and for how long — set once per meeting series, not per team: daily for blockers, weekly for decisions, every two weeks for review, monthly or quarterly for direction. The four rules for choosing a cadence, the cadence of each meeting most teams run, a template sized for 5, 15 and 50 people with the hours it costs, the signals that a cadence should change — and where each recurring meeting keeps its history in Teams, Zoom, Google Workspace and Slack, and in a channel that keeps every session in each member's language.

The Mind.com Team

How to run an effective meeting: before, during, after — and the channel that keeps what was decided (2026)
Meetings & recaps

How to run an effective meeting: before, during, after — and the channel that keeps what was decided (2026)

To run an effective meeting, decide its purpose in one sentence, send the list the day before, run the list inside time boxes with an owner per item, read every decision and action back in the last five minutes, and publish the recap the same day. The craft for each of the three stages, a running sheet you can copy, where the record of the meeting lives in Teams, Zoom, Google Workspace and Slack — and how a meeting run in a channel keeps its agenda, chat and recap readable by every member in their own language.

The Mind.com Team

Kick off meeting: agenda, checklist, example — for a project and for a new client, and how the kickoff becomes the channel (2026)
Meetings & recaps

Kick off meeting: agenda, checklist, example — for a project and for a new client, and how the kickoff becomes the channel (2026)

A kick off meeting is the first meeting of a project, where the people who will do the work agree what it is for, what done means, who owns which part, how they will communicate and what could go wrong — before any of the work starts. What the kickoff must leave behind, a checklist for before, during and after, a 60-minute agenda you can copy, a filled-in example for an internal project and one for a new client, where the record lives in Teams, Zoom, Google Workspace and Slack — and how the kickoff becomes the channel every later meeting of the project lives in, readable by each member in their own language.

The Mind.com Team

Stand-up meeting: format, daily agenda, async variant — and what the channel does between stand-ups (2026)
Meetings & recaps

Stand-up meeting: format, daily agenda, async variant — and what the channel does between stand-ups (2026)

A stand-up meeting is a short daily meeting of one team — fifteen minutes at most, same time every working day — where each person says what they finished since yesterday, what they will do until tomorrow and what is blocking them, so blockers surface while they are still cheap. The format and its six rules, the three questions and the version that works better, a daily agenda you can copy, the asynchronous variant for a team across time zones — and what the tools you already use do with the blockers between one stand-up and the next.

The Mind.com Team

All-hands meeting: agenda, format, examples — and how every office hears it in its own language (2026)
Meetings & recaps

All-hands meeting: agenda, format, examples — and how every office hears it in its own language (2026)

An all-hands meeting is the one meeting the whole company attends — leadership shares the numbers, the decisions and the stories, and everyone gets to ask about them. The format that works, a cadence by company size, an agenda template you can copy, three filled-in examples, where the all-hands lives in Teams, Zoom, Google Workspace and Slack — and how the questions, the answers and the decisions come back afterwards to the office that joined at 7 a.m. and the one that joined at 9 p.m.

The Mind.com Team

Action items: how to write, assign and track them — and how the recap keeps the list (2026)
Meetings & recaps

Action items: how to write, assign and track them — and how the recap keeps the list (2026)

An action item is one task that came out of a meeting, written as a verb with one owner and one date, so that someone who wasn't there can tell what will happen and who will make it happen. The format, how to write items during the call and at its close, how to assign them so they get done, a template and a tracker you can copy, where action items live in Teams, Zoom, Google Workspace and Slack — and how the recap of a recurring meeting writes the list, reads it back at the next session and marks each item done or not done.

The Mind.com Team

Meeting notes template: what to capture, who writes them now, and where they live after the call (2026)
Meetings & recaps

Meeting notes template: what to capture, who writes them now, and where they live after the call (2026)

A meeting notes template is a one-page layout you fill in during the call: the purpose and who was there, one block per item with what was said, what was decided and who does what by when, and a parking lot for anything raised but not resolved. The format, a template you can copy, two filled-in examples, how notes differ from minutes and from the recap — and where the notes live in Teams, Zoom, Google Workspace and Slack, with what happens to them once the call ends.

The Mind.com Team

Meeting agenda examples for 12 kinds of meetings — and what each one leaves behind (2026)
Meetings & recaps

Meeting agenda examples for 12 kinds of meetings — and what each one leaves behind (2026)

Twelve meeting agenda examples you can copy — weekly team meeting, daily stand-up, one-on-one, project kickoff, sprint review, retrospective, all-hands, leadership meeting, board meeting with a consent agenda, client call, customer QBR and hiring debrief — each with purpose, items, owners and minutes, and the one thing most examples skip: what the meeting leaves behind, and in whose language.

The Mind.com Team

Meeting agenda template: format, examples, and how the agenda comes back as the recap (2026)
Meetings & recaps

Meeting agenda template: format, examples, and how the agenda comes back as the recap (2026)

A meeting agenda is the list of what a meeting is for: the items, in order, each with an owner, a time box and the outcome it needs. The format, a template you can copy, five filled-in examples for the meetings most teams actually run, where the agenda lives in Teams, Zoom, Google Workspace and Slack — and how each item comes back after the call as decided, open or deferred, in every participant's own language.

The Mind.com Team

One-on-one meeting template: structure, cadence, and a running history both of you can read (2026)
Meetings & recaps

One-on-one meeting template: structure, cadence, and a running history both of you can read (2026)

A one-on-one is the report's meeting, not the manager's status update. The 30-minute template, the 45-minute monthly variant, how to prepare and run it, how often to hold it, the first one-on-one with a new report, fifteen questions by situation — and where the running history of your one-on-ones lives in Teams, Slack and a space built so both of you read it in your own language.

The Mind.com Team

Where Microsoft Teams and Google Meet store your transcript, recording and summary — and how to keep them after the call
Meetings & recaps

Where Microsoft Teams and Google Meet store your transcript, recording and summary — and how to keep them after the call

Looking for where Teams saved your transcript? Not with the recording. On Microsoft Teams and Google Meet the recording, the transcript and the AI summary are three separate objects in three places with three permission lists, and moving one does not move the others — Microsoft's own documentation says captions aren't fully supported once a Teams recording is moved. A documented map of where each artifact lands, who can still open it afterwards, and what it looks like when the meeting is a place instead of a folder of files.

The Mind.com Team

Book a demo: how to set up a demo flow with a calendar and one meeting link (2026)
Meetings & recaps

Book a demo: how to set up a demo flow with a calendar and one meeting link (2026)

What "book a demo" means, how it differs from a free trial and a discovery call, how to ask a vendor for one — and how a small team runs a demo flow without an SDR stack: a booking page in the calendar it already uses, one reusable meeting link in the description, each side in its own language, and a write-up that files itself in the CRM. Our own Book a call page is the worked example.

The Mind.com Team

Discovery call: what it is, how to run one, and how to hold it in the lead's own language (2026)
Meetings & recaps

Discovery call: what it is, how to run one, and how to hold it in the lead's own language (2026)

A discovery call is the first real conversation with a lead: you find out whether their problem is one you solve, and they find out whether you are worth a second meeting. A 30-minute agenda, 15 questions, a short script, what happens after — and a three-step setup for leads who would rather answer in the language they think in: a booking page in your calendar, one reusable meeting link, and a write-up that files itself in your CRM.

The Mind.com Team

How to write meeting minutes: format, template, example — and who writes them now (2026)
Meetings & recaps

How to write meeting minutes: format, template, example — and who writes them now (2026)

Meeting minutes are the official written record of a meeting: what was decided, who voted, who does what by when. The format, a template you can copy, a filled-in example, the board-meeting additions — and the question the format never asks: in whose language does the record arrive?

The Mind.com Team

Sales follow-up email: templates for after the call, and how to make the write-up send itself (2026)
Meetings & recaps

Sales follow-up email: templates for after the call, and how to make the write-up send itself (2026)

A sales follow-up email restates what was said on the call, what was decided, and the next step with a date — and it goes out the same day. Five templates for the situations that actually come up, the timing rules, how the email reaches the CRM by BCC in HubSpot, Pipedrive and Zoho (with their documented conditions), and a setup where the call write-up is generated for you and filed on the prospect's record without anyone copying it there.

The Mind.com Team

Meeting recap: how to write one, and what Zoom, Teams and Google Meet actually keep after the call (2026)
Meetings & recaps

Meeting recap: how to write one, and what Zoom, Teams and Google Meet actually keep after the call (2026)

A meeting recap is the part of the meeting that gets used — cited in the next call, searched a month later, read by whoever wasn't there. A short template, then the documented answer for each platform: where the recap lives, who receives it, who can edit it, how long it stays, and in whose language. Zoom AI Companion, Teams Recap, Google Meet's Take notes for me, and InterMIND, with sources.

The Mind.com Team

How much of your meeting still exists in your language a week later?
Meetings & recaps

How much of your meeting still exists in your language a week later?

Live translation gets measured in seconds and language counts. But meetings do their real work afterwards — in decisions cited, history searched, newcomers catching up. A documented audit of what survives the call on Zoom, Teams, Google Meet and the AI notetakers — and in whose language.

The Mind.com Team

Your SOPs Are Translated. Your Meetings About Them Aren't.
Meetings & recaps

Your SOPs Are Translated. Your Meetings About Them Aren't.

Regulated teams localize controlled documents but conduct cross-site audits, CAPA reviews, and inspections in broken English. The DMS solves the document layer. InterMIND solves the conversation layer.

The Mind.com Team