Q: You’ve described automating meeting notes as the first step on a longer journey. What did that journey look like at the start, and where is it heading?
A: Taking the manual work out of note-taking was always the first step. It was never the destination. We discovered quite quickly that the real value isn’t in the notes themselves, it’s in the context that comes with them.
Today, that context is something you can build on. You can use it in workflows, your agents can draw on it, and it stays useful long after the meeting ends.
Where it’s heading is something like a super brain for your organization: one that doesn’t only capture and hold knowledge, but can act on it. The user always stays in control, so nothing happens without you unless you want it to. Once that’s in place, you can eliminate all kinds of busywork around meetings and get far more out of every conversation.
Q: You’ve mentioned context a few times. Why does it matter so much, and what makes it hard to get right?
A: Without it, knowledge stays with whoever was in the room. I spend a large part of my day in meetings. If I weren’t using Jamie, all that context would only stay with me. Now I can reuse it and make it accessible to my team and my agents.
That compounds over time. If a partner learned something five years ago, a new hire can access it on their very first call, the moment it becomes relevant.
Getting there is harder than transcription, though.
Reflecting what was said word for word is only the start. The challenge is contextualising it across the conversation. A point raised at the beginning of a call might come back at the end, and a useful summary has to connect those moments rather than list them in order. The same problem then repeats at a larger scale: connecting what was said in one meeting to what was said in another, weeks or months apart, by different people. And without a bot, you’re also working out who said what in a room, not just on a call.
Getting all of that into a format that’s actually useful is a real challenge, and it’s one we’ve been solving for years.
Q: Bot-free capture and enterprise governance can look like they’re at odds. How does Jamie handle that?
A: Jamie has been bot-free from day one, unlike others that have shifted to it since. There were two reasons.
The first is atmosphere. When a bot joins a call, it changes the conversation, especially a personal one. People feel constantly watched, and that can stop them talking openly. We’ve all joined a call where the other person isn’t there yet but their bot already is. Nobody likes that experience.
The second is coverage. A bot limits you to online meetings. As soon as a conversation is hybrid or in person, it can’t tell who said what. For the conversations our customers have, that would leave out a lot of what matters.
But bot-free doesn’t mean invisible. Jamie is very open about what it does, and users and admins control how people are notified that Jamie is in use. That can be a consent email before the meeting, a compliance notice in the chat, or admin controls that enforce it across the organisation, so nobody can use Jamie without that consent notice. We also offer transcript redaction.
And then there’s the data itself. We’re a German company, GDPR-compliant, and with all data hosted and processed in the EU. Our customers work under very strict compliance requirements, so we built the controls to match.
Q: MCP has gone from rare to table stakes in under a year. How has that changed what people can do with their meeting context?
A: When we started Jamie, ChatGPT hadn’t launched yet. Today, a huge amount of work happens inside Claude, ChatGPT and other LLMs: drafting, researching, planning, preparing for the next conversation. If your meeting context can’t get into those tools, it’s missing from exactly the place it would be most useful. So for us (and many other vendors…) MCP was an obvious capability.
It’s also essential to the bigger vision. A brain for your organisation can’t live inside one app. It has to be reachable wherever the work happens, and by whatever is doing the work, including your agents.
In practice, that means asking Claude what a client pushed back on last quarter while you’re writing their proposal, or having an agent pull this week’s commitments into a follow-up plan, without leaving the tool you’re in. Alongside our native integrations, webhooks and API, it means Jamie can connect to pretty much anything.
Q: In our first report, the knowledge graph and the live coach sat side by side. One has deep context; the other helps in the moment but has little to draw on. What happens when that barrier collapses?
A: For a long time, you had to choose between speed and depth. A live tool without depth gives you generic prompts. A deep tool that only works after the call gives you great answers too late. Delivering both at the speed of a conversation is a genuinely hard product challenge.
But the demand is obvious, and live, context-rich assistance is what excites me most right now. Imagine: no more making a note to check something later, or scrambling to remember what was said during the call. I’d have more context during the conversation, which makes me better at it and makes meetings far more productive. Ideally, I don’t need to do anything. I just automatically get the right information at the right time, based on whatever preferences I’ve set.
The agentic workflows we’ve recently launched are a step in that direction. They go beyond capture to make sure every piece of information lands in the right place, so you can eliminate more of the busywork around meetings. Briefings, which are already live, are a good example; they put the right context in front of you before the call starts. Live support during meetings is where this goes next.