Step 1 · We map the meeting typesWhat closes which conversation?
Meeting CockpitThe meeting ended.Where did the follow-up go?
A preparation card reaches you before the call, notes are kept during it, and a summary with a task list comes out after. An item without an owner and a date does not count as closed, and the record is written into the client file.
Connected platforms
- Google Calendar
Google Meet
Zoom
HubSpot
Slack
Notion- Phone call
How it is built
From the moment the invite landsto the moment the task closes.
The first job is writing down what closes each kind of meeting: a sales call with a proposal, an internal meeting with a decision, a client call with a task. Then we connect the calendar and the client record and set up the cockpit. Last, we start tracking the open tasks.
Step 2 · The cockpit is builtPreparation and summary join one card.
Step 3 · Follow-up is measuredOpen items become a number.
What it can do
It prepares the meetingand leaves the closing to you.
Six modules take on the four moments of a conversation: preparation, notes, summary and tasks. Follow-up stops depending on personal discipline and starts depending on the system.
Before, during, after
As a meeting approaches, the client's history, open items and recent messages gather on one card. When it ends, the summary, the decisions and the tasks are written onto the same card.
The history comes from your own records
The preparation card is fed by your CRM records, earlier meeting summaries and open tasks. Every line you see on it has its source in your own system.
Tasks come out with an owner
Every item discussed becomes a task with a named owner and a date. An item without an owner does not count as closed and stays on the open list.
What was not said is not written
The summary comes only from what was actually discussed. The system does not try to complete a decision that was left open; it marks an unresolved item as unresolved.
The record lands in the CRM
The summary and the tasks are written to the client record. The preparation card for the next meeting feeds from that record, so you do not ask the same question twice.
Follow-up stays visible
The number of open tasks, the overdue items and the decisions per meeting sit on one screen. Which meeting produced a result stops being a matter of opinion.
Every platform
Wherever the meeting happens,it is written onto the same card.
Online call, phone or in person: the way the record is captured changes, the output does not. Adding a new platform does not touch the existing flow; only that platform's recording rule is written.
- A preparation card arrives beforehand
- Notes and markers are kept during
- A summary and tasks come out after
Frequently asked
Meeting CockpitFrequently asked questions
No. The system works from notes taken by hand. If you do want recordings, obtaining the attendees' consent is part of the build; without consent, recording does not start.
The system turns items into draft tasks and suggests an owner. A person makes the assignment; an unapproved task is not given to anyone.
From your own records: CRM history, earlier meeting summaries, open tasks and recent correspondence. Nothing is added from outside.
The summary comes out after the meeting and can be edited. Items that stayed unresolved are marked as unresolved; the system does not try to complete a decision that was not made.
The preparation card shows that item's history: which meeting it was first discussed in, who it was assigned to, and why it did not close. A reopened item is not treated as new; it appears as the continuation of the same item.
On your own infrastructure and in your own CRM. Meeting content is not used to train models.
Yes. If you use HubSpot we build on top of it; if you have your own panel we connect to that. The cockpit does not open a new place to store records; it feeds the record you already keep with the meeting output.
Discovery takes a week. In that week we write down the meeting types and the output expected from each. The first live workflow opens within 4-8 weeks; the range depends on the number of platforms, the CRM structure and the consent rules. Your own timeline is written into the discovery report.
Three things are measured before the cockpit is built: tasks produced per meeting, the time it takes a task to close, and the number of items reopened two weeks later. All three are measured again afterwards. The number of meetings with no summary drops to zero; every call on the calendar enters the record.
Connected platforms
Wherever the meeting comes from,the output stays the same.
Each platform is connected with its own recording rules. Whether a recording is taken, and who sees the summary, is decided during the build.
Calendar invite
A preparation card comes out of the attendees and the agenda, and is written to the client record.
CRM meeting
History and open items reach the card; the summary and tasks go back to the same record.
Team channel
A decision list comes out of the meeting notes and is written to the channel and the record together.
Internal meeting
Minutes and tasks are produced from the agenda page and land underneath that same page.
Online call
A summary and tasks come out of the audio or the notes; recording runs through a consent flow.
Phone call
A call summary is produced from the recording or the notes and written to the client record.
Related products
Next step
The process first, the proposal after
In a short discovery call we map the process together and tell you plainly whether it is worth automating. If it is not, we say that too.
30 minutes · no preparation needed
Discovery call
Process maptogether
Automation candidatesprioritised
Measurement planin writing
Next stepclear
