---
title: "Transcript: Granola for Enterprise Teams: From Meeting Notes to Organizational Intelligence"
webinar: "Granola for Enterprise Teams: From Meeting Notes to Organizational Intelligence"
date: 2026-05-06T14:00:00.000Z
duration: "1 hour"
speakers: ["Charlie Cowan", "Nick Taylor"]
topics: ["Why the real value of meeting capture is for everyone who wasn't in the room", "Enterprise Granola: spaces, folders, and templates for team-wide workflows", "Live demo: sales and product meeting templates in action", "Recipes and automations: how Granola turns meeting notes into follow-up emails, action items, and reports with a single prompt", "How Kowalah's AI agents use the Granola API for a daily meeting intelligence digest", "New use cases: customer interviews, product roadmaps, and culture pulse checks for leaders", "Getting started at scale: what a pilot looks like and how to roll out across teams"]
recording: https://youtu.be/ssKJcgaCg8g
canonical: https://kowalah.com/resources/wednesday-webinars/granola-enterprise-organizational-intelligence/transcript
source: Kowalah Wednesday Webinars
---

# Transcript: Granola for Enterprise Teams: From Meeting Notes to Organizational Intelligence

**Recorded** 6 May 2026  
**Duration** 1 hour  
**Speakers** Charlie Cowan, Nick Taylor

## About this session

The value of meeting capture isn't for the person in the room, it's for everyone who wasn't there. Join Kowalah and Granola to see how enterprise teams turn meeting notes into organizational intelligence that powers agents, informs roadmaps, and gives leaders a real-time pulse on their business.

## Topics covered

- Why the real value of meeting capture is for everyone who wasn't in the room
- Enterprise Granola: spaces, folders, and templates for team-wide workflows
- Live demo: sales and product meeting templates in action
- Recipes and automations: how Granola turns meeting notes into follow-up emails, action items, and reports with a single prompt
- How Kowalah's AI agents use the Granola API for a daily meeting intelligence digest
- New use cases: customer interviews, product roadmaps, and culture pulse checks for leaders
- Getting started at scale: what a pilot looks like and how to roll out across teams

## Recording

https://youtu.be/ssKJcgaCg8g

## Transcript

**Charlie Cowan:** Okay, good… afternoon, good morning, depending on where you're dialing in from. Welcome to this week's Kowalah Wednesday webinar. And I'm really, really excited for this one, because it is one of our showcase webinars, where it's not just me talking about what's going on in the world of AI, but we're really excited to welcome in a guest. For those of you that this is your first Kowalah Wednesday webinar, we get together at 3 o'clock UK time every Wednesday, and we have an hour to talk about something that is top of mind, either with our clients, or maybe something that we're working on internally. It's such a fast-moving space, and this gives us a time each week to walk through something that we think is useful, both for you personally and for your business.

**Charlie Cowan:** And, for us, here at Kowalah, one of the things that has really transformed the work that we're doing is a tool called Granola, which we're going to be diving into deeper. For any of you that are in product roles, you may have come across a thing called the Sean Ellis Test, sometimes known as the product-market fit test, and it's a way for companies to measure and assess whether they've got sustainable growth. The question that gets posed is, if this thing was taken away from you, how would you feel? Would you be very disappointed? Mildly disappointed? Not disappointed at all? Or have you stopped using this thing completely? And the test says that if more than 40% of your customers say, I would be very disappointed, then you've got product-market fit, and you're growing.

**Charlie Cowan:** And I was thinking about this, because if someone took away Granola from me personally and from our team, I would be very disappointed. And so with that, I'm gonna introduce Nick. Nick is Head of Customer Success at Granola. He's gonna be walking us through a few bits and pieces in a minute. But Nick, maybe you'd like to say a few words, say hello, and introduce yourself and your role.

**Nick Taylor:** Yeah, thanks so much, Charlie, and what an introduction. My name is Nick Taylor, I'm the Head of Customer Success at Granola. What that means is it's my job, hopefully by the end of this webinar, to have you fully understand how Granola works and how to get the best out of it. Today I'm hopefully going to give you an understanding of what the practical uses might be of Granola, and some tips and tricks along the way.

**Charlie Cowan:** Fantastic. Thanks, Nick. We've got a loose agenda that we're going to go through. We're going to swap screens in a minute and share to Nick's screen a little bit about how Granola uses Granola, but also think about it through the enterprise lens — when we're thinking about our clients who are in a range of different industries, how do they really embed this into their way of working. And towards the end, I'm gonna show you a little bit about how we're using Granola here at Kowalah, not just about our human team members using Granola, but also our Kowalah agents, who are using Granola as well. Then at the end, we'll wrap up with a few lessons learned.

**Charlie Cowan:** I'm sure Nick will have some, and I've got a few thoughts about things we've picked up along the way, so hopefully we can help you, if you're early in your Granola journey, to think through what this might mean for you and your business. Now, we're in Zoom, and I'm sure you've used it before — at the top or bottom of your screen, depending on your device, you'll see a chat bar, so you can chat or ask questions there. There's also a Q&A bar, and I'll keep an eye on that. Caitlin, our human colleague, is also on the call and will keep an eye too. Don't feel you need to wait until the end for questions.

**Charlie Cowan:** If there's something that Nick or I are talking about and you want to dive straight into, then ask your question and we'll come to it. So with that, I'm gonna stop sharing my screen — I think Nick is gonna share his — and we're going to get into the tool and learn a little bit about Granola and call transcription.

**Nick Taylor:** Amazing. Yeah, let's dive right in, and as Charlie said, I think let's do the best thing possible, which is get the tool in front of us and get going and learn a little bit more about it. Before I dive into the practical uses of Granola, let's just talk a little bit about what Granola's used for and why it's helpful. I think many of us have used lots of different notepad tools in our journey — some of us are even still writing notes and find that incredibly useful. I think Granola does one of two things really, really well. One, it creates that notepad experience you're probably very used to with something like Apple Notes or Evernote. It also sits in the background of a call that you're part of, and it transcribes all the conversation going on.

**Nick Taylor:** And at the end of the meeting, it will combine your meeting notes — if you've written any — with that call transcription, and generate a summary of the meeting based on that transcript, running it through a few different models we've engineered on our side, and come up with a really nice overview. And what better way to show you that end-to-end than diving right in? Now, Granola is connected to your calendar, so one of the benefits I always hear about from senior leaders I talk to at these enterprises is they're always late for meetings. But when they use Granola, they're actually early, because it reminds you about a minute before the meeting starts, and you can dive right in.

**Nick Taylor:** So, as you can see here, I've got the calendar connected — tomorrow I've got a few events going on in this demo account, and it would remind me just before that call starts: let's hop on and start transcribing. But for the purposes of this, let's just dive in and get a note started straight away. So I'm gonna go into this quick note button here. This experience should seem very familiar to most of you — I am a dark mode user, I'll say, so apologies, it's not as light and bright as some of you may have seen before. I'll go ahead and write some notes saying Charlie kicked us off.

**Nick Taylor:** Remember… oop, I can't type, that's a theme of this demo. Remember some learnings for the end, perhaps, as well. And I should really remember to send a thank you to the team afterwards. I've gone ahead and added a few of these notes — we've talked about Granola for maybe no more than 30 or 40 seconds so far, and it will have listened to that and enhance those notes. But let's take our fingers away from the keyboard and start talking a bit more, so I can include some notes in this process that I haven't typed down. You'll see here at the bottom we've got a little waveform going on.

**Nick Taylor:** If I click into that, you can actually see it, as I'm umming and ahhing, being live-transcribed in front of me. It's a little distracting, but you can see it happening live right here. There's a monologue — you can see I've been talking for a while now, so it's a block of text, but you can also…

**Charlie Cowan:** And Nick, if I'm talking, is that going to come through as well?

**Nick Taylor:** Nope.

**Charlie Cowan:** Okay, cool. So it knows that I'm a different speaker.

**Nick Taylor:** Exactly, and as we developed Granola, we wanted to have, like, a you-versus-the-rest-of-the-speakers distinction, and we pick up — because you're talking, Charlie, on Zoom, I'm pulling that audio in via Zoom as well, so if you're in person or on Zoom, we can capture both. It works for in-person meetings as well as over Zoom.

**Charlie Cowan:** In a meeting when there are multiple people, is there any best practice about identifying different speakers? Should we get people to say, hi, I'm Charlie — does that help?

**Nick Taylor:** Yeah, I think one of the things that works really well is if, at the start of the meeting, you can capture that introductions part of the call — that's always helpful. And when you're wrapping up a call, if you can reiterate the action items, or even ask Granola in the chat what the action items are, or what you've agreed to do, Granola can surface those to you — okay, after this, Charlie is going to make sure this is uploaded to YouTube, and Nick is going to make sure he sends a thank you to the team afterwards, etc.

**Nick Taylor:** Granola will take that — it's in the transcript, so you can see it below — and make sure it's perfectly captured. Bookending the meeting gives it as much context as possible. Well, we've been talking for a little while, so let's get to that magic moment. I'm going to stop the transcript right there — when you leave a meeting it will automatically stop, but here I'm doing it manually — and click this enhanced notes button, and it'll analyze the transcript and start building those notes for us.

**Nick Taylor:** It's building out what we call sections, with a few different sub-bullets and bullets underneath. Here we talked about some key features, some best practices — these were the notes I took from the meeting, and it generated a nice, quick summary for us. At any point, if you want to switch back to just your notes, you've got this My Notes button. If you click that, you go back to your notes, and you can make changes — like, actually, there are some action items, right? I'll type one square bracket, another square bracket, and a space, and get a little to-do button.

**Nick Taylor:** If you do that, you can add in your own to-dos. I can also add a dash to get bullets, and format with italics, bold, or underline. Those are all your notes, so you can format them really well, and Granola will try to pick those up and make them apparent in the generated notes as well. Now, when we were talking, Charlie, we said, what happens if I've forgotten the takeaway items at the end of the meeting? So let's ask Granola: what are the takeaways from this meeting? We have an agentic search — it'll look through the transcript, run a quick summary, and give that to me.

**Nick Taylor:** So here it's talking about exactly how we think about Granola, what we talked about, some concrete reminders I saved in my notes, and a quick summary. And I can say, what are the follow-ups? And it'll say: send a thank you, capture the learnings, start with introductions, and restate the action items. I can even ask it to write a follow-up email — this, we'll come back to a little later, is called a recipe. It's like a pre-written prompt, a really quick way of getting a lot out of Granola.

**Nick Taylor:** So it's written me a quick email — you'll see, thanks for joining, here's a next step, looking forward to staying in touch. My name's not Lucy, but this is the demo account for all intents and purposes. And I get a few questions sometimes — we talked about this a bit, Charlie — like, what models do you use? We have a lot of the leading models available; you'll see everything from the big three, and you can switch between them. We'll default to whichever model is performing best at the time.

**Charlie Cowan:** Nick, a quick question from Andy about offline, in-person meetings. Can this handle that?

**Nick Taylor:** Yeah, definitely. Granola will be available for in-person meetings. What I'd say is you'd still need an internet connection for us to transcribe, since we're sending the audio off to a third party. So if you don't have internet access, it won't be able to transcribe or record during that meeting. But if you're not connected to a Zoom call, you can still have an in-person meeting — you bump into a colleague and think, let's just get Granola started, and have it run in the background.

**Charlie Cowan:** Yeah, definitely, Andy. I use the iPhone app a lot, so whenever I'm in an in-person meeting I'll say, do you mind if I Granola this? And I'll physically put my iPhone on the table so people know it's recording, and I find that really useful. We'll get into some other use cases in a minute, but for complex customer discovery meetings, someone explaining a process we're going to build something around, Granola-ing all the way and using the phone on the desk is super helpful.

**Nick Taylor:** Yeah, agreed. The mobile app, which is a little different from the desktop app, even lets you make outgoing calls using Granola. I have a number of customers I talk to — one told me he was doing a house renovation and would call his builder on the phone, because he'd always have a record of what was discussed, and could always send those notes through to keep everything on track. This is an initial note, quickly created, but there are a couple of things to point out. First, as you said, you can chat with the meeting. Second, you can always share the meeting directly with people.

**Nick Taylor:** So here in this demo account, let's say I want to share that with my colleague Zara, one of these fake users here. I can share it with her — if Zara has an account, this will pop up as something shared with her, and she'll have full access to read the notes and chat with the transcript. If she doesn't have an account, this would invite her if we're at the same company; if you're not at the same company and want to share notes publicly, you can copy this link and share it, giving them access to a webpage that's pretty much the same view, with the ability to chat with the note as well.

**Nick Taylor:** You can, of course, restrict sharing to only people who've been invited, or people in your domain — we have some security features around that — but you're able to share notes with customers, contractors, or external parties quite easily, all through Granola.

**Charlie Cowan:** As well.

**Nick Taylor:** Yeah. There's a bunch of integrations we have, but a couple I find really helpful: you can connect Slack to Granola and fire out a quick message into a Slack channel. For example, we've connected it to a Slack channel for our demo here, and you can just post the meeting there, and then anyone who has access to that link, or has been invited directly, can jump in and see those notes. So it's a very easy way to share company knowledge with each other.

**Charlie Cowan:** We've touched on this a little with me saying, when I'm in a meeting room I'll say, do you mind if I Granola this? Are you able to touch on permissions and privacy — the differences between this and note-takers that join meetings?

**Nick Taylor:** Yeah, I think one of the benefits of Granola is that it doesn't join the meeting, and a lot of our users like it for that. Obviously, in Europe and in certain US states, there are laws regarding being recorded without authorization, so it's always best practice, as you mentioned, to say, hey, I'm going to transcribe this with Granola. We have a bunch of handy features we can enable for enterprise and business customers, where you can give people a heads-up before the meeting, or — I have this new feature I'm testing internally — have your webcam show a little marker saying Granola is recording. I think you saw that the other day, Charlie. So we're working on features to make it more explicit if you want, but the key thing is making sure you've gotten consent and announced Granola in some way. We provide different methods to do that.

**Charlie Cowan:** Mmm.

**Nick Taylor:** Yeah, it's something you can always call out at the start of the meeting if you're ever worried, and I think it works pretty well. Most people don't

**Charlie Cowan:** Yeah.

**Nick Taylor:** interact with it much, and just move on afterwards.

**Charlie Cowan:** The way I've been phrasing it, and you might tell me I'm wrong, is that with something like Gong, or a similar tool that's actually recording the meeting — recording the audio and video of the person — certain laws apply. With Granola, it's not recording the video, it's not recording the audio, it's taking notes, and there's a difference in how the law treats those two things. So when it's just recording in a meeting like this, I haven't been explicitly saying, by the way, I'm transcribing. Is that incorrect, or is there a differentiation because you're not actually recording the other people?

**Nick Taylor:** Yeah, I'm obviously not a legal expert, I'll highlight that, but…

**Charlie Cowan:** Yeah, caveat.

**Nick Taylor:** the common piece, to your point, is that Granola is transcribing, and we're not storing any recording, and we're not making available any video of the call. We're simply sending the audio off to a third-party provider who gives us text, and we're storing that text as a transcript. So we're not necessarily subject to things like wiretapping laws. But we always advise, if you're ever worried, to be on the safe side and call it out at the start of a call.

**Charlie Cowan:** Yeah.

**Nick Taylor:** We're not under the same sort of banner as the other tools.

**Charlie Cowan:** I think we'll move off this topic in a second, but one of the reasons I think this is so important is I've worked in teams where — and I love Gong, it's a great tool for sales teams — and then maybe you've got other call-recording bots that join meetings, and the behaviour I see is people immediately trying to kick their own call recorders out of the meeting. Oh, sorry about that, because they recognise they're not going to have the conversation they want, because it's quite visible that a third of the screen is taken up by "I'm recording," and everyone's on edge. That's one of the reasons we fell in love with this non-invasive, I'm-here-to-take-notes approach that doesn't take up a third of the screen. If anyone watching is wondering why they'd use this over something else — it's a bit of human behaviour, and it's something we've certainly seen. One quick question from the chat about an Android app — do you have any intel or updates?

**Nick Taylor:** Good question. Internally, we have a version of the Android app working — we hired an Android developer about a month ago, and have been quietly working on an MVP internally, so I can't give exact dates, but I've seen and played with an Android app.

**Charlie Cowan:** I have seen it live.

**Nick Taylor:** I have, and maybe, hot off the press, even a watch app — an Apple Watch app.

**Charlie Cowan:** Huh.

**Nick Taylor:** which would be fun. So, different peripherals we're playing about with internally, and those are the two next up.

**Charlie Cowan:** Brilliant. So what's next? We're in our meeting, we've got our notes.

**Nick Taylor:** Exactly. We've shared this with a few people, and I should say that by default your Granola notes are private to you — you're in control of them, and where you choose to share them is the next piece. I've shared this note directly, with Zara in this case, and copied the link over to someone. Let's return to the home screen — you'll see this demo meeting I just did, by default in the list of meetings, marked private. Let's move over to the sidebar on the left — I'll collapse a couple of things to help explain this.

**Nick Taylor:** You have this concept of what we call spaces, and by default everything goes into the My Notes section. If we jump in here, this is where your private notes are, where you can create private folders — you'll see this demo ends up here. It's a question of what do you want to do with that meeting, where does it belong, do you want to share it with a group rather than a single person, or send a link? I'll explain why folders are important in a second, but maybe we can think about some folders for it too. You'll see I have a few different folders on the left-hand side, and it's very easy to create one — I'll do this here.

**Nick Taylor:** I can choose some icons or emojis, set a quick description, and create it. For example, I have a One-to-Ones folder here. My colleague Zara, who I mentioned, seems to be having lots of conversations with, or being part of conversations with, Zara. When we have many conversations in one folder, we can ask questions across many meetings, not just a single one. So let's assume I'm a manager of Zara's and want to know what's top of mind for her — maybe I'm prepping for our next one-to-one and want to sense-check what she's working on.

**Nick Taylor:** So here, the agent looks ahead through all the meetings with Zara and comes up with a quick summary based on the latest coffee chat. There are some deals Zara seems to be working on, so we can assume she's a salesperson. You can see Greywood has stalled due to a reorg, so maybe something to ask is what can I do to unblock Greywood — it seems Dom couldn't champion anything. We've recently made our chat a lot more agentic, which allows us to look not just at the notes here, but also at other notes outside this folder that we have access to, adding a lot more context.

**Nick Taylor:** So here we've got the notes in this folder, but also a few additional things — some action items, a few people who seem new to me based on previous context, and some suggestions from Granola that aren't from the notes here. It's May now, maybe it's been a while, let's re-engage with Dom, maybe things have changed — if we're still blocked, maybe we go to Claire Yates. So our chat is getting smarter and smarter, even pulling in context outside those folders, but folders really help us think about how to slice and dice our meetings, and how to get the most out of them.

**Nick Taylor:** So the benefit of sharing in the My Notes section with folders is you can work on a project together, work in one-to-ones, or folderize your meetings around a specific company, and get the ability to chat across them.

**Charlie Cowan:** When you think about structuring folders — say I'm a manager with 8 people in my team, I can see you've got a One-to-Ones folder there. How do you think about that versus having a folder for each team member, or a folder for the team overall? Are there any trade-offs?

**Nick Taylor:** Yeah, maybe let's jump ahead a little, because to answer that there are some really helpful views hidden at the bottom of the page. We have four little icons at the bottom, and two of them are perhaps the most powerful views we have in Granola, but also some of the most unknown. If I click this view, this is a view of people — people I've spoken to, or who've been part of notes shared with me via the calendar invite. Here you can see Zara, with 21 notes. There's a person called Jonathan who seems different.

**Nick Taylor:** If I click that, I have a few different meetings I'm part of that Jonathan is either part of, or that I've had directly with him, or that have been shared with me. I have a daily stand-up with Jonathan as part of the sales calls, more daily stand-ups I'm part of, the team meetings folder, a product council with Jonathan, and a one-to-one or handover with him. That's a way of getting a good view of what someone is doing across many different meetings, not just in a folder you've built.

**Charlie Cowan:** For them.

**Nick Taylor:** And to compound that, when you think about companies, we have this company view that helps you search across different companies. If I type in Meridian, I can see all the different calls that have been had with Meridian, from an initial introduction all the way to closing a deal in this demo. I can do things like — I built a little recipe for myself called a handover, and I can just run this pre-written prompt. As someone in post-sales, this is my biggest bugbear — I think you used to work in sales, Charlie, so I'm sure you've had to do many handovers in your life.

**Charlie Cowan:** Yeah.

**Nick Taylor:** You can pre-write one automatically using the context across that company in Granola.

**Charlie Cowan:** Yeah, cool. I guess it's implicit in what you're saying, but with the caveat that you'd need access to those calls, either being shared with you, for it to be able to pull that.

**Nick Taylor:** Exactly, and that's the important piece. This team space here — this shared team space — is something shared with your entire workspace. So if you're putting notes here, everyone in your current Granola workspace has access to them. Things like one-to-ones wouldn't go here, or sensitive information, but at Granola we use this space for things like user interviews from our product and engineering teams, customer conversations from our sales team, stand-ups, and product decisions. As someone who joined Granola at the start of the year, I was able to go in and ask, what are our top 5 pain points for our customers today? What are the most recent decisions we've made?

**Nick Taylor:** certain areas of the product — and pull all that context without going to ask a bunch of people. I can just chat to Granola and get that information immediately, because it's shared in this team space and I have access to everything. And again, you can create folders here to help manage that process. There are a couple of other things I wanted to show — let's head back to that meeting quickly. This comes to a situation where you're having lots of meetings that are probably a little repetitive, and you want to think about how to get more from them. There are two distinct things I'd recommend investing time in. The first is if you head to this little sparkle at the top.

**Nick Taylor:** You'll see a drop-down, and we have a few different templates we provide out of the box. If I click this demo template — keep in mind, take a quick snapshot of what's on the left here for how we've laid out the notes — I'll click that, and it will regenerate the notes in front of you. You can see what the purpose is, some key features, and as we scroll down, some additional information we've captured, and you'll see how the notes are restructured, with a lot more context added. Templates are a really good way of thinking about how to get the most out of your meetings, and how to reformat them without having to worry about it a lot.

**Nick Taylor:** So you'll see it's a quick template I made earlier — I'm running a demo, it's a simple meeting, what's the purpose, what are the key features. We also provide things like a one-to-one template — what's top of mind for the other person, any updates or wins, etc. These are really simple to build, and we provide a bunch out of the box — hiring templates, product demos, and so on. It's also really simple to build your own template — you just give Granola the context, choose the sections, and the context at each section.

**Nick Taylor:** You can have as many sections as you like, and then publish it to your whole workspace if you want everyone to use that template. I think templates work really well — I use them a lot, for example when I'm hiring and want everyone across the same scorecard, or for user interviews where I want to keep the same format across the board, or one-to-ones where I want to make sure I cover everything. Templates are very powerful, and I actually get Claude to help me build some of them — I have it write the context and the sections it thinks might be useful, and I just copy and paste that into Granola.

**Nick Taylor:** I have that top of mind.

**Charlie Cowan:** Yeah, we're loving templates, and I'm a stickler for every meeting having an agenda — we shouldn't be meeting without one. For so many recurring meetings, whether it's a one-to-one, hiring, or a common one for us — I'll maybe show this later when I share my screen — a project launch workshop, we've got a very structured agenda with a series of topics we go through. You pair the agenda shared in the Google Calendar invite with the corresponding template in the meeting, and the two things come together beautifully — the meeting follows the agenda, and at the end you click, use the project launch workshop template, and it breaks everything down exactly as discussed.

**Nick Taylor:** That's definitely — yeah, people love to see an agenda with everything written out underneath it, it's the perfect meeting at that point, you've hit everything to a T. There's one more thing I wanted to showcase, which is recipes. We've talked about them a little — they're pre-written prompts, and we provide a number out of the box. I'm a person who always craves coaching, really in-depth, sometimes very critical feedback. One I recommend, if you're a bit like me, is Coach Me Matt, based on a guy called Matt Mockery, a very famous business coach.

**Nick Taylor:** I think he coaches Sam Altman, for example, and we've translated his method into a prompt. Don't worry, you don't need prompts as complex as this, but you can see the amount of work that's gone into building it. When you run it — just slash coach-me-matt — you get a very in-depth review of the last 7 days and where you can improve. That's the big, complex version, but it can be super simple too — there's one I absolutely love where you can just type slash joke, and Granola will come up with a joke for you on the spot.

**Nick Taylor:** Or if you're a busy, hard-working person jumping between meetings — maybe your kids need something, or a parcel gets delivered partway through — there's What Did I Miss?, which gives you the last 5 minutes of what's happened in the meeting, so you can catch up immediately. The way to think about recipes is whether you want to run a query across multiple meetings, or look at one specific meeting — we batch those across meetings, before, during, or after. There's a bunch I'd recommend checking out, and we also use a bunch we've built internally — for example, a post-call wrap-up I built the other day.

**Nick Taylor:** This is a very in-depth recipe, but in actuality — and to give you a little secret — I get Claude to build all my recipes for me. I tell Claude, look, I want to build a prompt for this, and I'm doing it in Granola — can you come up with a good version? It builds it, and the best bit is you can try it on a previous meeting — I'll try this on this demo, and you'll see it's built me some next steps, some things in a CRM, etc.

**Nick Taylor:** So you can just iterate, and I don't know about you, Charlie, but I'm a bit of a builder, I like to see progress and keep things moving, so for me that worked really well.

**Charlie Cowan:** Yeah.

**Nick Taylor:** Get a hold of stuff.

**Charlie Cowan:** That's great. I know in a minute we're going to jump into things like MCP and accessing this data, but I just want to wrap up this bit about capturing information. Certainly the journey I've been on — when I worked in sales teams maybe 4 or 5 years ago, it was all about rolling out call recording, who on the team would have access to it, and getting permission from the client, almost having to sell them on why it was useful for us to record the call. I think we've moved into a new world where everything is transcribed — there really shouldn't be any meeting, internal or external, that isn't.

**Charlie Cowan:** I really think that when I'm speaking with a vendor today, if I'm explaining my process and my team, and spending two hours talking them through it, I want more than the little doodle in their notebook as a record. I want it transcribed, so I don't have to explain it to someone else again. I see a bit of a trend there. And as we're going to talk more about MCP in a minute — it's everyone's responsibility to transcribe the meetings they're in. If these conversations are happening and not being added to the organization's collective intelligence, that's a bit of a miss.

**Charlie Cowan:** I don't know if you're seeing this with your enterprise clients — it moving from call recording being something for a few select salespeople, to something we need to gather from everyone and every client.

**Nick Taylor:** Yeah, I think everyone's moving towards that second-brain initiative, for want of a better term — getting company context across the whole company, not just in silos, like in sales teams. You want it in one format, one source, and available. People are building agents off the back of that, using it for automations, etc., but you need to pipe that context somewhere, or have a reliable source of it, and I think Granola is seeing itself as a bit of that context layer going forward — particularly for meetings and internal conversations, we can provide a lot of rich context to these tools, which we'll talk about in a second.

**Charlie Cowan:** Let's switch gears then — this also ties into a question from Kai. What are some of the different use cases for Granola, MCP, and Claude, versus just setting up a recipe within Granola?

**Nick Taylor:** Great question. I think the question to ask yourself is whether you should use the MCP or build a recipe — what do you want to do inside Granola, and does Granola have access to all that information today? If the answer is you want to combine lots of different sources of information, you can probably do that in something like Claude. Or if you want to create an artifact or document, you'd probably build that in Lovable or Claude as well. So, to your question, let's jump into Claude.

**Nick Taylor:** I had this in front of me today — one of the customers we talked about was Meridian Analytics, and I wrote this while we were talking: look at my Granola notes for this company, summarize everything so I can hand over this deal to the post-sales team, a bit like the recipe we saw earlier, and highlight some key information and stakeholders. A quick and dirty prompt for Claude, but it's going to look at the Granola meetings — I'm giving it access to those. The way our MCP works, it queries Granola, looks at the meetings that may be relevant, and when it finds the ones it wants to pull information from, it goes and gets that. We'll give it a couple of seconds.

**Nick Taylor:** I've pre-prompted this in the background while we've been waiting, so we can jump over to it — it takes about a minute or so to fully get that context.

**Charlie Cowan:** While it's doing that — we saw a minute ago that you've got the actual transcript, and then the AI note. What's it looking at, the summary or the raw transcript?

**Nick Taylor:** It's looking at the transcript today. If, for whatever reason, you don't have access to that — some customers delete transcripts after a while because they don't want to hold onto them — it'll just grab the note instead, so you're not losing out even if there's some privacy consideration in play. So here it's giving me a quick deal snapshot, some questions to ask, and asking whether I want to put this in a Word doc. I actually followed that thread a bit while we've been talking, and you'll see it's giving me the same snapshot here.

**Nick Taylor:** And then I got it to draft a Slack message to send to someone, assuming a quick handover, and you'll see this nice Word doc here covering the information in more detail — basic information and internal handover notes. You can even format it for something like Salesforce. It's as powerful as you want to prompt it. I've used our Granola notes to build a demo tool for our internal sales team — when they log in, I've vibe-coded something that says, I'm talking to a sales team, I've got 30 minutes, and I'm speaking to, say, a VP of Sales.

**Nick Taylor:** It builds a run of show, tells our sales team the recipes and templates to use, but also pulls in the Granola context and adds any conversations they've already had with that team, enriching it — you told this VP that, so why don't you re-highlight it? That's the kind of real power you can add to what you're building in Claude — pulling in historical context, the questions you've been asked, and the rich information from those calls, and adding it all to everything you're already building in Claude. I did actually go ahead and build something in Lovable, which I think would be really interesting.

**Nick Taylor:** I asked it to look at my Granola notes for Meridian Analytics and come up with a small pitch deck for this fake company, LoopNote. I didn't know what this would look like, but I'm pretty pleased with the outcome — it came up with a whole sales pitch. LoopNote is a similar style of business to Granola, and it's come up with the why-Meridian angle, the hidden tax, fitting that narrative we've had throughout a bunch of calls with Meridian, and it's even got the pricing we'd talked about. A really nice way of building a deck you could almost send to a customer immediately.

**Charlie Cowan:** What this opens up is so many new use cases for transcription, outside of my original world of sales calls where I need to take down all the notes and description. Once you expand this out — customer success meetings, product review meetings, legal negotiation meetings, finance negotiation meetings, supplier meetings, absolutely everything. I think of call transcription like a dash cam — you're not looking to record something specific, but later, when you need to look back at something, you've got the transcription there. If a company is transcribing everything, then at some point in the future…

**Charlie Cowan:** someone in product is going to ask, across all of our customer calls, what are customers asking about? Legal is going to ask, across all our customer calls, what are people pushing back on that isn't making it to legal, so we can build an FAQ and take a cycle out? It's like this dash cam — if you capture everything, you give people who never considered themselves consumers of call transcription access to it. I'm seeing lots of examples of product teams building MVPs because they sat in a room with a couple of customers, and eight minutes after the call someone says, something like this? How do you do that?

**Charlie Cowan:** Transcription into Lovable, or v0, and away you go.

**Nick Taylor:** Yeah, that exact example happened a few weeks ago — I was on a call with a customer, and one of our PMs stepped out and built an MVP in about 15 minutes, then shipped it on a Slack channel to a customer: how does it look, how does it feel? And the customer asked, had you built this already? And I said, no, I just used my Granola notes, connected them to Claude, and off we went. It's something we just built.

**Charlie Cowan:** Yeah.

**Nick Taylor:** Its speed to delivery is amazing with stuff like that.

**Charlie Cowan:** When we're doing customer discovery meetings, in person or otherwise — like the example with the iPhone on the table — I think of it a bit like a police interview: for the purposes of the tape, can you confirm your name? I'll make a bit of a joke with clients — right, for the purpose of the tape, can you explain your process in detail? And I'm interviewing them, maybe we're drawing pictures on a whiteboard, but it's gathering all that detail, and any question I don't understand, I'll ask them to explain it a bit more, because I know Granola is capturing all of it. Then when we get back to building out our solution, we've got this rich content to work from.

**Nick Taylor:** Yeah, exactly. I think the one thing I find myself doing more often is going into that quick note we did at the start, and just chatting to Granola about a bunch of stuff on my mind.

**Charlie Cowan:** Hmm.

**Nick Taylor:** I've got to do this today, I want to do this, make sure I do XYZ — I use it as a way to keep myself honest, pulling some of those ideas into tools like Claude. A prime example: I had to chat with someone about the consent features we talked about earlier, so I said to Claude, here are the last three conversations, this is my brain dump, take that, take a few of the customer conversations, and build me a Notion page summarizing everything with some next steps. Honestly, that would have taken me a day or two.

**Charlie Cowan:** Yeah.

**Nick Taylor:** to put together, and it took me 20 minutes or less. Pretty powerful.

**Charlie Cowan:** I've got tons of questions — I'm going to focus on some of the enterprise side of things. For those watching who aren't familiar, MCP stands for Model Context Protocol, and it's basically the way you give AI tools access to information in other systems — think of it as a connector. One of the reasons we're loving using it in Claude is that, whilst the Granola UI is lovely, Claude is where the work is happening for me, because it's acting as the hub. Granola is a lovely spoke, Google Docs is a lovely spoke, Google Calendar is a lovely spoke, HubSpot, our CRM, is a lovely spoke.

**Charlie Cowan:** Canva, Linear, all of these spokes — we're able to have this conversation, and while the demo Nick did was about chatting in Claude and pulling in the Granola notes, the richness we get when preparing for an upcoming customer meeting isn't just the Granola notes, it's the deal details from HubSpot, the proposal from Google Drive, the last emails the customer sent. You really feel like you've got a real partner as you're prepping. Ten minutes to go — that was the connector for an individual. Are you able to touch on the API, which I know is fairly recent, and how enterprise-level companies might be thinking about it?

**Nick Taylor:** Yeah, we have a couple of different APIs. The MCP is really good for quick access today. We have a personal API, which provides a similar experience to the MCP, for users who want to build out a bunch of automations without relying on the MCP and its rate limits — good for holistically building cron jobs you might want to run automations on. The enterprise API is built to pull everything in that team space — everything that's publicly available to everyone. You can ingest all of that into Salesforce, other tools, or your own local database.

**Nick Taylor:** One customer has essentially built an agent for every individual employee, making all that context available via the API. In that agent, they can query a bunch of information that's publicly available in Granola, plus additional context from their pricing solution, their CRM, etc., all connected in this internal agent — very powerful. We have fantastic documentation on our website if you want to know more. I see a lot of enterprises moving towards that second-brain initiative…

**Charlie Cowan:** I mean.

**Nick Taylor:** I spoke about, and the use cases end up being: I want to build an agent for my employees, or I want a database of shared context I can index for automations, or to save people's time — you've had a meeting, let's pull those notes out and put them in Salesforce. As you said, you used to be a salesperson, so I'm sure you spent a ton of time updating notes in a CRM.

**Charlie Cowan:** If you.

**Nick Taylor:** If you've gotten away from that, you would have, and now people are able to, with those notes available via the API.

**Charlie Cowan:** Well, that's a great segue. Let me share my screen and show you how we're using it. Nick was talking about templates earlier, and I mentioned our project launch workshop template — we go through introductions, how we're going to communicate with each other, how we're going to store documents and deliverables, and so on. This is essentially a complete copy of the agenda we run through with clients in a Google Doc, so when the template comes through, the notes mimic it directly — it's worthwhile building the agenda first for all your internal and external meetings, and then building the corresponding template. What I wanted to show in these last five minutes is our agent hub.

**Charlie Cowan:** This is internal to Kowalah — we've got humans in our team, in an org chart, and agents in our team, in an org chart. Here I am, the founder and CEO. There's Charlotte, who's human, as Operations Director, and then a series of different agents we've built across revenue go-to-market, delivery, operations and people, and finance. We're continuing to build these out day by day — we've got a backlog of about 8 more to add to the team. Every time someone says, I need to hire someone, I say, we're going to build an agent first. I'll talk about Brian, since you mentioned sales and updating the CRM — this is Brian, an agent. Brian's got an actual email address at Kowalah, since we set him up on Google Workspace.

**Charlie Cowan:** That means Brian's got email, Google Chat, and his own Google Drive folders where he can create proposals and read various things. It also means our team can chat with him via Gchat — I spend a lot of time just chatting to Brian: hey Brian, can you update this proposal? Hey Brian, we just got this lead in. I'll give him screenshots of LinkedIn, forward him emails if I get an inbound — Brian deals with HubSpot, so I don't need to. I've given him a system prompt that explains all of his roles, what he needs to do, how he should create opportunities and everything in HubSpot. Brian's got a couple of skills, and one I want to show you is his daily deal sweep.

**Charlie Cowan:** I'm busy going call to call, making lots of commitments to customers, going straight onto the next call, haven't done anything about those commitments. At 7:30 in the morning, Brian runs his daily deal sweep skill: step one, scan HubSpot to familiarize himself with all the deals in the pipeline; step two, scan Granola for all the notes from meetings I was part of yesterday; step three, go and scan each deal's recent emails, both via HubSpot and in my Gmail inbox. At this point, Brian knows just as much about everything as I do, because he was effectively in those meetings and emails too. What he then does is merge it all, assess it, and go and create new deals in HubSpot where I haven't, or update deals where I haven't.

**Charlie Cowan:** So the first thing I know, at around 7:30 in the morning, is I get pinged: you're the new deal owner of this, you're the new owner of that, because Brian's set it all up. This is Brian using the Granola API. Let me go to Tools here — Brian's got access to all of these tools, which are all API connections: Gmail, so he can send email; his own calendar, if we invite him to meetings; Gchat, so he can do all sorts of things there, and spaces, where we can mention him; Google Drive, so he can create his own folders; and, importantly, Granola — he can get a note, list notes, and search meetings by attendees.

**Charlie Cowan:** So if I'm — and this happens all the time — I just chat to him like a member of the team: hey Brian, I've got a meeting with Nick at Granola tomorrow, can you help me prep for it? I don't need to say anything else, and Brian will go and look at HubSpot and Granola, pull everything back, and say, here's what I've got, what do you want the theme of the meeting to be? We'll chat a bit, and Brian will build out the agenda and everything else. Brian is really acting as a colleague — he can do everything other than physically go and meet the client. We're really excited about the potential of these agents.

**Charlie Cowan:** But it's only by giving them access to tools — in this case, through the Enterprise API, giving Brian access to every meeting anyone at Kowalah has had, that's been put into the team folder — that Brian has as much knowledge about these meetings as anyone on our human team, through that API. So, nearly at time, I've got a couple of minutes for some lessons learned, and maybe you can add anything you want to this too, Nick. Three things I've really taken away from our journey so far. Number one: transcribe everything. Think of the dash cam — you don't know the value of a meeting until later, when someone's trying to get these meetings at scale. So, in our view, every meeting should be Granola'd, internal and external.

**Charlie Cowan:** It's not just for the people in the meeting, and it's not a case of saying, can't they take their own notes? It's for the people who weren't there. And it's not just better for you — it's better for the client. If I'm going to spend an hour telling you about my process, I want more than a doodle and a notepad taken back to the company. Number two: templates and recipes — someone in your team should be responsible for owning this, so there's consistency across the company. And the third is feeding your non-human colleagues — they weren't in the meeting, because they don't exist, so they definitely weren't there. How do we feed them somehow? This is where the Enterprise API comes in, or potentially the MCP. One minute to go, Nick.

**Charlie Cowan:** I don't know if there's anything else you'd add as a lesson learned, or any final thoughts.

**Nick Taylor:** Yeah, I think for me the thing that resonates most is that feeding your agents is really important. Thinking of Granola as a food source isn't just in the name — it's fuel for your agents and agentic workflows. The possibilities are huge, and I'd urge you to try using the MCP, and a bunch of the templates and recipes within Granola, to level up the amount of work you don't have to do off the back of it. Over the next year or so, you'll see a lot of tools becoming a lot more expansive, and I think context is going to be one of the key things that lets you do more with those tools.

**Charlie Cowan:** That's brilliant. Thanks so much, Nick. I started off by saying, if I was asked what would happen if you could no longer use it, I'd say I'm very disappointed, and hopefully what Nick has shown you builds up why that's the case. Nick, thank you so much, and thank you to the Granola team for joining the webinar. Thanks to everyone who joined, either live or on YouTube. If you want any other support, you can find Nick on LinkedIn, and via the Kowalah team as well. We'll see you next week.

**Nick Taylor:** No worries, thank you so much.

---

This transcript is published by Kowalah, a UK Anthropic Implementation Specialist.
Webinar page: https://kowalah.com/resources/wednesday-webinars/granola-enterprise-organizational-intelligence
All transcripts: https://kowalah.com/resources/wednesday-webinars/transcripts