Tokenizing
Human Interaction
Capture all the company knowledge in online and offline meetings, calls, rooms, screens and ambient office conversation — with quality and consent.
- Transcript
- Who said each line
- Language of each line
- Timestamps
- Participants and the meeting or call
- Screen context
- Consent record
Agents don’t see most company knowledge
- Gmail, Outlook
- Notion, Drive
- Slack
- Jira, Linear
- HubSpot, Salesforce
- Client calls
- Stand-ups and 1:1s
- Meeting rooms
- Screens
- The hallway
We’re a source for brains and agents
Who builds on _æfer: company brains and agent builders.
MeetingsCallsRoomsScreens
- Glean
- Dust
- Mem
- Notion AI
- ChatGPT Enterprise
- Sentra
Unlock company superintelligence
Capture everything the company says. Every team can build on it.
Decision log. Why X was decided, who decided it, and the meeting where it happened.
Sales
- Sales coachingCompares every demo with the ones that closed and tells each rep what to change.
- Deal riskFlags the deals where the buyer went quiet on budget or named a competitor.
- Client follow-upsEvery promise made to a client goes out as a follow-up, with who made it.
Product
- Decision logWhy X was decided, who decided it, and the meeting where it happened.
- Customer voiceEvery feature request said on a call, de-duplicated, with the clip.
- Churn reasonsWhy customers leave, in their words, from every cancellation call.
Engineering
- Issue trackingA bug mentioned in any meeting becomes a ticket, with the clip and who hit it.
- Incident timelineThe postmortem timeline, written from the incident call as it happened.
- Design decisionsEach architecture call written up: options weighed, what won, and why.
Support
- Escalation contextThe whole account history, including what sales promised, on every escalated ticket.
- Known-issue spotterSpots the same complaint on five calls and warns before it’s fifty.
- Account memoryEvery call with the client and every promise in it, before the renewal.
Operations
- SOPs from real workWrites the SOP from how the team actually does it, not how the wiki says.
- Action items that chaseEvery action item from every meeting, with an owner and a date, nudged until done.
- Audit trailWho told the client what, and when, for every regulated conversation.
People
- Onboarding from past callsAsk “why do we do it this way?” and get the meeting where it was decided.
- Handover when someone leavesWhat Pau knew, from two years of his calls, for whoever takes over.
- Expert finderWho knows about the billing export? The person who explained it best, and where.
Leadership
- Weekly exec digestWhat every team decided, promised and worried about this week, on one page.
- Project statusWhere each project stands, from the meetings already held. No status meeting.
- Bottleneck finderFinds where work waits, from who keeps asking whom for what.
Powerful features built in
Notes are only as good as their names.
- ?Speaker 214:03:22
If it’s two years we can do twenty-seven.
- ?Speaker 314:03:23
I’ll put that in the contract tonight.
“Someone will send the terms.”helps nobody
- JMJoan Martí14:03:22
If it’s two years we can do twenty-seven.
- LSLaia Soler14:03:23
I’ll put that in the contract tonight.
“Laia sends the terms tonight.”is a task
Every line knows its language.
Your agents know what they’re reading.
- Detected per lineRead from the speech itself, a few seconds at a time, so a switch mid-call is followed straight away.
- Tagged in the outputEvery line carries its language code.
- Fixed if you preferAuto is the default. A company rule can set one language for a team or a meeting series.
[
{ "speaker": "Ana García" , "language": "en" ,
"text": "So the open question is the price for two years." },
{ "speaker": "Joan Martí" , "language": "es" ,
"text": "Con dos años podemos bajar al veintisiete." },
{ "speaker": "Laia Soler" , "language": "ca" ,
"text": "D’acord, ho poso al contracte avui mateix." }
]The best one for each language.
A speech engine turns audio into text. None is best at every language, so _æfer sends each language to the engine that writes it best.
- 01Engine A96in use
- 02Engine C91
- 03Engine B87
- 04Engine E83
- 05Engine D79
- 01Engine C95in use
- 02Engine A92
- 03Engine E86
- 04Engine B84
- 05Engine D77
- 01Engine D94in use
- 02Engine C88
- 03Engine A81
- 04Engine E74
- 05Engine B70
Your company sets the rules. The most specific one wins.
Admins answer four questions once; teams, types of meeting and single meetings refine the answer.
- companyAcmeRecord external calls · people in the call see noteseveryone
- teamSalesAlso share notes with the CRM12 people
- meeting typeCustomer callsSales summary · Englishevery week
- meetingGlobex renewalLanguage: SpanishWINS
- personJoan MartíDon’t keep my voice in one-to-oneshis choice
more specific rules sit lowera person can share less, never be made to share more
- RecordedYes, external callcompany
- Who sees itPeople in the call, Sales CRMteam
- LanguageSpanishmeeting
- SummarySales summarycustomer calls
You decide what happens with your data.
The company decides what happens. Each person also decides what of theirs gets shared: their own switches, a pause, and a way to take back anything they said.
- MeetingsNotes on by your company’s rulecompany rule
- Agent chatsOnly chats about work are kept
- Computer activityApps and browser, never shared
- My voice printRecognise my voice next time
- Take a breakNothing is kept while paused
Private messages and personal moments are never kept. Nobody can change this setting, not even an admin.
We ask people first. Everyone in the meeting is told.
The notetaker joins as a visible guest and says it is taking notes. Everyone sees the notice, and anyone can say no right there.
Harbor Notetaker joined for Ana García and is taking notes. You can say no, right now or later.
Only for this call. Change it any time.
Your notetaker, with your name on it.
It carries your product’s name, avatar and words, in the call and in every email after it. Try a name.
Harbor Notetaker 10:00
Hi, I’m Harbor Notetaker, taking notes for Ana. I’ll send everyone the summary after the call.
Ship with our SDKs
A toolkit to capture company context in your name
Desktop app
Can we hold 27 if it’s two years?
Yes, if they sign this month.
Mobile app
Plaud & Pocket
Components
<Sidebar /><MeetingList /><MeetingSummary />- Two years at 27.
- Laia updates the contract today.
- Marta sends the DPA; signed by Friday.
Transcript
Let’s close the renewal before we break.
Con dos años bajamos al veintisiete.
D’acord, ho poso al contracte avui.
Legal needs the DPA by Friday.
Your schema
type Event = { event: "decision" | "commitment"; owner; due; quote; }
Same four voices. A different transcript.
- Speaker 1Pau Ribas
Legal needs the
endeep paysigned by Friday.Legal needs the DPA signed by Friday. - Speaker 2Marta Vidal
I’ll send it to
enKenny what an a bayatnorth wind.I’ll send it to Kenji Watanabe at Northwind. Speaker 1Laia Soler
encaThe cord, who posed a contract of email.D’acord, ho poso al contracte avui mateix.- Speaker 3Joan Martí
Con dos años bajamos al
esveinte siete.Con dos años bajamos al veintisiete.
The best model. Every time.
You never pick a model. Live scores on real data pick the best one for each language and use case, automatically.
Meetings, calls and rooms, in any of 130+ languages.
Each language goes to the engine that writes it best today.
Our own fine-tuned models, and third-party ones.
Named, timed, in its language.
Behind it, all the time:
Correcting transcripts in real time: the ground truth every engine is scored against.
NetflixElevenLabs
Every engine, language by language, on real meeting audio.
…and the scores pick the engine.
Six people, one phone. Every voice named.
No logins in a meeting room, and voices overlap. Voice prints put a name on each one, even offline.
One voice, wherever it’s said.
A call, a room, a phone, a pocket recorder. The same voice print names Laia in all of them, so her week joins up.
- Zoom · Meeting Bot
“Can we move the launch to May?”
Mon 10:12 - Room 3B · laptop
“Fine, the contract goes out tonight.”
Tue 14:03 - Phone call · mobile
“Northwind signed. Tell legal.”
Wed 17:45 - Plaud · Connect
“Idea: a renewal reminder for every client.”
Thu 08:30
Pocket recorders, in the same record.
Plaud and Pocket recordings go through the same engines and voice prints as your meetings: more accurate than the devices’ own transcription, and filed right next to them.
Laia SolerIdea: a renewal reminder for every client
- Pricing syncAna García, Joan Martí, Laia Soler
Site visit, Harbor’s new officeLaia Soler, Pau Ribas · named by voice
- Call with NorthwindMarta Vidal, Laia Soler
Agent telepathy
The Desktop SDK sees your screen and hears your conversations while you work. You don’t repeat yourself; your agent already knows.
| Client | Northwind |
| Contact | Kenji Watanabe |
| Term | 2 years |
| Price / seat | 27 |
| Clause | EU residency |
Hi Kenji, following today’s call
Sure. Which email, to whom, and what should it say?no context
Done: the renewal to Kenji at Northwind, two years at 27 per seat, EU residency clause kept, as in the sheet you just edited.from your screen, 2 min ago
Screen capture can run on the user’s machine, under company and personal rules.
Agents read. But they’re not in the room.
Every decision worth knowing was said before it was written. Most were never written at all. Agents that only read are working from yesterday.
We love privacy
_æfer listens only where your company and each person allow it.
Your context. Your rules.
Your agents get the work. Nobody gets watched.
| _æfer always | _æfer never |
|---|---|
| Sticks to meetings and workA work filter keeps personal moments out. | Reads private chats or direct messages |
| Tells everyone in the call that notes are on | Listens in the background without people knowing |
| Lets each person say no, pause, review or remove what they share | Keeps what someone asked it not to keep |
| Keeps user rules on, whatever the admin sets | Lets anyone switch them offNot an admin, not a manager. |
| Follows your company’s rules for who is recorded, who sees it and where it’s storedThe most specific rule wins. | Shares with anyone your rules leave out |
Accuracy = autonomy
Agents only act on their own when they can trust what they read. One wrong name, and disaster follows.
For the teams deploying AI at work.
You’re building agents for a company – yours or a client’s. _æfer gives them what was said there, through one API, so you can spend your time on the agent.
Stupid simple to install.
- 010:00Paste
One prompt into your coding agent.
- 020:12Wire
It reads the docs and writes the code.
- 033:52Approve
You say yes to the key.
- 044:51Done
_æfer is in your product.
Context infrastructure for enterprise agents.
Capture the meetings, calls and rooms your rules allow, so agents can act on them. Ship in 5 minutes.