Sam Liang

The reason I use a meeting-centric, the reason is interesting is that traditionally when people think about knowledge base, they only think about the written documents, like documents in Google Doc, Notion, emails for Slack message, or some data in MySQL CRM.

People rarely think about voice data because traditionally all the voice data is all lost.

But now with Otter, we help people capture that voice and meeting data.

And we create this workspace to help you organize it so that you can find the content in the right relevant channels.

Or you can search globally.

In our company, you can almost find anything in any team.

Oh, wow.

No matter where you work.

So most of our content is actually public.

The idea is that to reduce information silos.

Again, in the past, almost no meeting is captured.

But now some meetings are captured, but most people still keep it online.

to themselves, keep the meeting notes to themselves so that each team, there's still a wall between each team.

It really slows down information dissemination or propagation.

That slows down the operation of your team.

They create a lot of inefficiency.

So we see this is why it's important to create a meeting-centric knowledge base.

Another reason is this, if you think about it, number one, for most enterprises, actually meetings is the most expensive activity.

Most people didn't realize that.

Just think about how much time all the team members spend in meetings.