Somebody has the minutes, and that somebody is a person
A client meeting runs forty minutes and leaves three things behind: a commitment with a date, an objection you will have to answer two months from now, and a fact nobody wrote down because at the time it seemed obvious.
All three live in the head of whoever was there. The minutes that circulate afterwards capture what was decided, not what was said, and the nuance that actually mattered (the tone in which the client said "price is not the problem") does not fit in a set of minutes.
An individual transcription tool fixes this halfway. Now there is a recording, a transcript, a summary and a task list. But all of it hangs off one account, and the account belongs to the person who recorded.
The day that person leaves
A salesperson moves to another company. A consultant finishes her project. A lawyer joins a different firm. With them go:
- The recordings of every visit they made.
- The real objections their clients raised, with the exact sentence and the timestamp.
- The context for why that discount was accepted back in March.
- The verbal agreements that never made it into a document.
What is left is a CRM with stages and a few emails. Rebuilding a two-year relationship falls on whoever arrives, and they end up asking colleagues about things that are already recorded somewhere they cannot reach.
This is not fixed by exporting files before someone's last day. It is fixed by making sure the material was never personal to begin with.
What team mode is
A team account has a shared library. Everything any member records lands in it, with its transcript, its analysis and its citations, and the rest of the team can search it according to their role.
It is not a shared folder somebody has to remember to upload to. It is where recordings land by default.
Whoever creates the account invites, and invitations travel by link
The person who buys the plan is the account holder. From their dashboard they generate invitations and hand them out: whoever receives the link signs in with their own email address, with no shared passwords and no borrowed accounts.
Links expire and can be revoked. An invitation sent to the wrong address is cancelled, not chased.
Roles
| Role | What they can do |
|---|---|
| Holder | Buys, adjusts seats, invites and removes, sees the billing |
| Member | Records, imports, generates analyses, searches the team library |
| Guest | Opens the specific notes shared with them, not the library |
The guest role matters more than it looks: it is what lets you show a client or an outside adviser the minutes of one meeting without giving them access to anything else.
Seats, and a quota that is pooled
The plan is bought per seat, from 2 upwards. What is not divided is the quota.
A team of six does not get a bag of minutes each: it gets the sum, and whoever needs it spends it. In any real team some people record every day and others once a month, so splitting evenly leaves dead minutes on one side while blocking somebody on the other, on exactly the day they have the meeting that counts.
The same goes for AI credits (the ones spent generating an analysis, asking a note a question, or calling in from your own assistant over MCP) and for storage. They add up per seat and come out of one shared pool.
And one invoice, in the account holder's name.
What happens when someone leaves
Their seat is withdrawn. And that is the end of the episode, because:
- Their recordings stay. They were in the team library from day one, not in a personal account somebody now has to empty.
- Their transcripts and analyses stay searchable. Whoever takes over asks the notes instead of asking colleagues.
- Their access is gone immediately. They do not keep browsing the library from home because nobody remembered to remove the user.
- The seat is reused. It goes to whoever arrives, with no second trip through checkout.
The honest comparison is this: without a team plan, someone leaving is an incident to be handled in a hurry. With a team plan, it is a permissions change.
Who it is for
Accounting and tax firms. Every client meeting carries figures that later go into a model, a payroll run or a year end. When the adviser who handled it is on holiday, whoever picks up the phone needs to know what was agreed back in October. With a shared library they look it up; without one, they ask around.
Law firms. A matter that starts with one partner ends up touching three. The recording of that first meeting, with the dates and figures the client gave, is what stops the second lawyer from asking the same questions again and billing for them. And the guest role lets you share the minutes with the client without opening up the rest.
Agencies. The real brief is not in the brief. It is in the kickoff call, in the sentence where the client said what they do not want. Making that call searchable by the whole creative team, and not only by whoever took it, is the difference between a proposal that lands and three rounds of revisions.
Consultancies. Projects run for months and people rotate between them. A library of working sessions, with chapters and citations to the minute, is what lets somebody join in week six without asking anyone to narrate the first five.
Three things a team can do that one person cannot
1. Ask the whole team at once. "What pricing objections did we get this quarter, and who resolved them?" cuts across everybody's recordings, not one person's.
2. Prepare for a meeting you did not run. Ten minutes reading the analysis of previous visits, with the citations where things were actually said, instead of a handover call nobody has time for.
3. Spot what keeps repeating. When the same misunderstanding shows up in calls from four different people, it stops being bad luck and becomes a problem with the sales material.
What does not change
It is still processed in Europe. The team plan does not move anything to another jurisdiction: transcription and analysis still run on European servers.
Citations still have a source. Every answer comes with the exact minute it came from, so a claim without a citation can be rejected. In a team this matters twice as much, because whoever reads the summary was not in the room.
Nobody gatecrashes the meeting. AudioMap does not send a bot to sit in the video call under anyone's name. You record, or you upload the file, and the people in the room know what is going on.
How to start
You buy it from the [pricing](/pricing) page by choosing the number of seats, and invitations go out from the dashboard the same day.
If you would rather see it working first, the [demo](/) has real recordings and needs no sign-up. And if your team already uses AI assistants, the [MCP and API guide](/blog/conecta-tu-ia-con-audiomap-mcp-api) explains how to connect them to that shared library.