WebMCP clearly explained (and how to make $$)

Vinny is back on the pod, and he explains WebMCP. WebMCP puts MCP tools inside the browser UI, so any agent that you bring can read a page and act on it. Vinny demos an espresso gear store where his agent compares two machines, checks the counter width, matches accessories, adds an item to the cart, and applies a coupon. Together we map the agent-native options, from headless APIs to in-app agents, and we place WebMCP in the middle of that map. I close the episode with two cash-flowing business ideas that a semi-technical founder can start today. Timestamps 00:00 – Intro 02:28 – WebMCP Clearly Explained 07:22 – Demo: Conditional Tools And Browser Session Login 09:11 – The Agent-Native Paradigm 12:12 – How Agents Interact with Apps 16:05 – Demo: Accessories, Cart, And Coupons 18:42 – Where WebMCP fits 21:03 – Startup Idea 1: WebMCP Conversion Agency 24:27 – Startup Idea 2: Agent Mystery Shopper 26:11 – Closing Thoughts Key Points WebMCP makes a website agent-readable and agent-actionable through a short, clear list of tools. The browser session carries the login, so tools stay conditional and the setup stays simple. The live store demo compares machines, matches accessories, adds to the cart, and applies a coupon. WebMCP sits between headless APIs and in-app agents, and it keeps the visual UI that most people prefer. Vince says WebMCP launched in February as a joint Microsoft and Google experiment in Chrome. The first markets: complex commerce, SaaS admin consoles, read-only flows in regulated industries, and internal tools. The #1 tool to find startup ideas/trends - https://www.ideabrowser.com LCA helps Fortune 500s and fast-growing startups build their future - from Warner Music to Fortnite to Dropbox. We turn 'what if' into reality with AI, apps, and next-gen products https://latecheckout.agency/ The Vibe Marketer - Resources for people into vibe marketing/marketing with AI: https://www.thevibemarketer.com/ FIND ME ON SOCIAL X/Twitter: https://twitter.com/gregisenberg Instagram: https://instagram.com/gregisenberg/ LinkedIn: https://www.linkedin.com/in/gisenberg/ FIND VINNY ON SOCIAL: X/Twitter: https://x.com/hot_town Youtube: https://www.youtube.com/channel/UCHP5Hdx0X-sM0uv2bl_OOqg

• 0:00Speaker 00

  Think about this, AI agents are about to become a new kind of visitor on the internet. And I think billions of dollars of wealth will change hands in the process. Because millions of AI agents are going to be browsing and buying on the internet. But the internet isn't designed for them to do that. And that creates a really interesting question, which is, what does an agent-ready website or app look like? And how do you actually build one? Well, there's this new little thing by Google called Web MCP. And I'm honestly surprised more people aren't talking about it. The simple idea is that websites can expose cleaner actions for AI agents. So instead of an AI agent trying to figure out a page like a human being,

• 0:44Speaker 00

  the site can basically tell an agent, here's how to search, here's how to book, here's how to buy. So today I have my friend Vinny come on and just clearly explain what Web MCP is, how it differs from MCPs, why it matters, where the opportunities lie. And I give you two startup ideas that I think could cash flow, that you can start today. Enjoy the episode. I hope it gets the creative juices flowing. And if you haven't liked, comment and subscribe. What are you doing? This stuff should be paid. We make it free. I just want to see you win. Let's go and I'll see you at the end of the episode.

• 1:25Speaker 00

  Thank the MRR gods. Vinny is back on the pod to explain something very, very, very powerful. Web MCP, Vince, you actually brought it to my attention. Vinny, by the end of this episode, what are people going to learn?

• 1:41Speaker 01

  All right, they're going to learn how to use Web MCP, which is kind of exactly like it sounds. It's MCP, but in the UI, in the browser. And this is like a brand new experimental feature from Google and Microsoft. So I really think this is a first mover advantage here. So if you can learn this stuff, you're really bringing, you're getting the skills that you need to bring stuff to market that is emerging, that's going to probably be the next big trend. So I think this is a really cool thing.

• 2:09Speaker 00

  So Vince is going to actually explain to you in a clear way what Web MCP is, how to use it. And at the end of the episode, I'm going to share with you two startup ideas, cash flowing startup ideas that I think could use Web MCP that you can build today. That'll be at the end. Vince, you start them off.

• 2:27Speaker 01

  All right, cool. So let me start from like a problem I had myself. When I heard about Web MCP, the first thing that came to mind is this shop that I've got here. It's an espresso machines and gear shop. So I was buying an espresso machine and it has like a lot of specifications. It's got a lot of gear and accessories. And figuring out which one's right for me and also which accessories fit was kind of a pain. So it was a lot of back and forth, Googling, also putting stuff into an agent or ChatGPT or whatever. And like, does this fit? Will this work? So I thought, oh, cool. This is a great use case for something like this,

• 3:09Speaker 01

  where we could build a shop with Web MCP tools in it that your agent can talk to. So you can bring any agent that you're using, which is whether it's like Claude Code or ChatGPT cowork, whatever these, whatever agents are out there, maybe Grokbot. And you can talk to the website and ask it stuff. So let me just show an example real quick. And so I want to upgrade from my current Mara X machine. And I want to get one that's able to make two flat whites a day easily and fits on my counter space, which is about 32 centimeters wide.

• 3:46Speaker 00

  By the way, in simplest, like in the simplest form, correct me if I'm wrong, Vince, but Web MCP is basically just websites with agent buttons. So you're, we're making websites agent readable and agent actionable. Is that right?

• 4:02Speaker 01

  Exactly. And it's not like this wasn't available before, but it was available in a lot like clunkier way. So you've got computer use or you've also got agents that can kind of browse and use a browser and go through websites, click buttons. But before they had to do it in a very not so efficient way. So they're, they're getting the entire DOM, which means they're getting all the code from the website. And they're like scanning through it and finding where to click, taking screenshots and stuff. But look at that, what just happened right here on the screen. It manipulated the, the website, was able to find two machines, put them side by side. And then it highlighted, really cool feature, highlighted what features

• 4:45Speaker 01

  or what specs about the machines fit my request that I just had. So it's like the port of filter fit, which is going to fit like an accessory you have. And then will it make the two flat whites like you asked? And does it have the right width? Will it fit on your counter spot? So like, that's really cool. And before, to do all that, well, first of all, it wouldn't be able to manipulate a page in this way as easily. And also it'd have to go through all this scanning, all this code reading. Whereas this now with Web MCP, there's a set of tools, like the ones that are just popping up on the screen here. And those are the ones that you make available to the agent. So it gives it a really efficient, concise list of things that it can do on the website.

• 5:29Speaker 01

  And it knows how to do that and it can just do it easily. And, and you can do some really cool creative stuff with this.

• 5:37Speaker 00

  Yeah. And I think like, one of the reasons I think this actually matters is if you think about SEO, right? It was like, can Google understand the page? And then we had AEO, which is can AI cite the answer? And now we're entering this Web MCP era, which is basically can the agent finish the job? And we're, what we're learning is that websites aren't really optimized. And I think that's why Google and Microsoft decided to build this thing, right? Because they don't want a broken internet to exist. And I think as like a founder, like, why does this matter? Is because there's, there's, you know, billions, billions of dollars changing hands on these tools, right?

• 6:22Speaker 00

  Or on the internet. And if we can optimize some of these websites, you know, there's just, there's a lot of opportunity.

• 6:31Speaker 01

  Yeah. And I think, I mean, maybe the people like you and I and the people listening, they're more agent native or they're more this kind of early adopters of new technology. But we have to remember that the web has been around for a while. People are used to UIs and browsing websites and stuff like that. And people don't really want to, the majority of web users don't want to use just like a CLI tool or, or an agent in the terminal like this. They want to be able to interact with something visual. So this Web MCP really makes it the best path to do that. So will really allow for kind of normal, the average consumer to adopt agent tools.

• 7:16Speaker 01

  So it's kind of like meeting them in the middle, right? With the new agent technology and the stuff that they're used to.

• 7:22Speaker 00

  Cool. What else do we need to know about it?

• 7:25Speaker 01

  So like, one of the big things is, like I said, is that it's not scraping and parsing the entire DOM. So it doesn't have to, it's more efficient in the way it works. But the other thing that's really cool is that these tools, you can make them conditional. So like, you see here in this list, we have tools that are always available versus logged in. And this is all happening through the browser session, right? So I've logged in, you can see I'm up here, I've logged in. These are the tools available. And if I log out, well, then we'll see there's only three tools available now, right? So this is really cool because one of the big hurdles to doing other kind of agent native approaches,

• 8:07Speaker 01

  like an MCP server or an API, is that you have to deal with tokens, credentials, people sending, sending their, their identity through, you know, API keys and tokens and things like that. Whereas this, you just log in, right? So I can log in with my username and password. And it has access to the entire browser session there. So the fact that I'm logged in, the agent has to, doesn't have to do anything special. We don't have to connect an MCP server and authenticate and all that stuff like you have to do with, you know, a typical MCP server or with an API or things like that.

• 8:46Speaker 01

  So it's like the least technical approach to making an app or a website or a web store agent native, but with the most flexibility and the most features. So this conditional tool calling, all this stuff just happens because of the browser state. And that's a really nice thing.

• 9:03Speaker 00

  Yeah, that's really cool. That's just like built in. I mean, it makes sense, right?

• 9:08Speaker 01

  Yep, it's using the whole browser session, so that's really nice. Alright, so I saw this tweet the other day, and I've seen this going around a lot, where people are saying, "I don't want to use your product's agent. I want my agents to be efficiently enabled to use your product." And that's exactly what we're getting with Web MCP, and especially for things like web stores and stuff like that, for e-commerce, or maybe even, you know, other examples that we'll look at later that you have prepared for us. So, this is a sentiment that's going around on Twitter a lot lately. And what does Dylan from CloudFlare mean by this? So, we have these like, different ways an agent can meet an app, right?

• 9:52Speaker 01

  And let me go zoom in real quick, because we have a lot of them. And they're going from headless, you see at the bottom here, it says "headless." So basically, running an app via your agent without ever seeing the app. That's what headless means, right? There's no app in the browser, there's no website. So, you bring your own agent, you can hit a raw API. But there's, like we said, there's lots of things. You have to deal with authentication, and the agent has to hold an API key and things like that. But then you can bring your own agent, and you can use MCP, which is a typical MCP server. But that's another layer on top of your app's backend. And then, your agent can't manipulate the UI, right? Like we just saw. So, those are completely headless ways.

• 10:37Speaker 01

  They're a little, add a little bit more complexity to your app or to your product. Now, we have computer use, which is where the bots or the agents literally have a computer that they can use, whether it's your local computer or a computer in the cloud. And they're running through screenshotting stuff and clicking stuff on the computer, on the UI, like you would. And this isn't really the most efficient, because of, like we said before, you've got to go through, you've got a screenshot, or the agent has to screenshot all this stuff. So, this is slow and fragile at the moment.

• 11:12Speaker 01

  We have browser MCP, which is similar to computer use, where, like we were talking about, where you get the whole code from the website. And it has to kind of figure out through the HTML code, and where it can click, and what it can do. Again, that's a little bit more fragile. Web MCP kind of comes now to be somewhere in the middle of that, or the things we just mentioned. And an in-app agent, which is what the tweet was complaining about, right? Which is that, like, you build an app with a little agent sidebar, and your, the agent in that app is the only thing that can communicate and deal with it, right? So, what they're saying is, they want something where they can bring their agent,

• 11:55Speaker 01

  and they can use your product efficiently. And that's where I think, especially for traditional apps with a front-end storefront, whatever, that they can then use, bring their agent, and use your app efficiently. So that's what's really cool about it. Does that make sense?

• 12:13Speaker 00

  So, if I'm getting this right, so Web MCP, you've got your agent, there's a set of tools, or things that you can do, basically, on the website or the app. And then, and it's sort of limited to that. The in-app agent, you have your, you know, the vendor's agent, and the app's agent, right? And that just interfaces with the app's logic and data back and forth. And the app is, like, isn't that like the best end state of where we think things are going, right?

• 12:53Speaker 01

  The in-app agent, you mean?

• 12:55Speaker 00

  Yeah.

• 12:56Speaker 01

  Well, I mean, you can look at it from two different perspectives, right? That it's nice to have like a little in-app agent there. But you're responsible then for configuring everything, you're responsible for the tokens, right? You're responsible for setting it all up. Whereas with Web MCP, Web MCP is like this really nice middle ground, where you don't have to work, you don't have to pay for tokens. You're giving the app agent capabilities, but the user is bringing the app, the agent that they used. And any agent will work with it. So, if we're moving quickly to this world where everyone has an agent that they use at work, that they use for personal preference, you know? You don't have to then separate them from that.

• 13:40Speaker 01

  That's the agent they know, and they can just use it with your tool via Web MCP. So it's kind of like the nicest, because it makes it easy for you, and it makes it most comfortable for them.

• 13:50Speaker 00

  Yeah, I guess the in-app agent was sort of like a transitionary piece of software

• 13:59Speaker 00

  that needed to exist for a certain amount of time, but we're like, kind of growing out of it. Like, the idea of like, you know, use, you know, Intercom Fin, right? Which is basically like, I think, a customer support agent. Like, that experience is really, really good. But now, in a world where it's pretty clear that over the next 24, 36 months, everyone, consumers are going to have their own agents. It just makes sense that these agents are going to need places to interface with the internet at large, and the internet is just not designed for those agents yet. So, you know, that's why Web MCP, you know, exists.

• 14:40Speaker 01

  Yeah, I think there is this place for in-app agents, right? Like, if, in Notion, for example, they offer both. But like, if there's something that is, like CloudFlare Dashboard, they have an in-app agent. And this is, so it's like very, it's gated to only use their tools, and not to change preferences too much, so that you don't do anything kind of hazardous. I can see where in-app agents might make sense, but we're moving into this world where it's like, we're doing so much with agents, and we want them to keep their context. So, you want one tool that kind of has the context and knowledge and memory of everything that you do. And to be able to bring that one agent with all that context to different tools is really powerful. And I think that's where you're going to see people, they're going to kind of get stuck

• 15:25Speaker 01

  on one agent, one kind of agent product, whether that be GrokBot, or Claude CoWork, or ChatGPT Work, or whatever. And then, they're just going to kind of access the internet and interface with the, with different things on the internet through those agents. So, that's where I think Web MCP is really powerful. It's also just like a great companion for when you're shopping with, for complicated things. You can use an agent if you need to kind of help you out, figure out which specs, what thing's right. And you don't have to build in this big bloated, you know, in-app agent into your, into your app to get some better customer experience for you.

• 16:05Speaker 00

  Can you show an example, another example?

• 16:08Speaker 01

  Yeah, sure, so, I could say like, yeah, so you suggested the Lolita Bianca. What are some really nice accessories I should add that will fit the Lolita Bianca? So, this is something that like bugged me a ton, was, I found the machine, now I need a grinder, now I need the right portafilter, I want a new basket. They're all different sizes, they all use, one might use a measurement, one might use a name, or some kind of like, brand name. And parsing through all that information as a customer can get really tedious. So, just to have an agent that can do that, and then let you know, is perfect. Because it has all the context here from the store. It knows what I've ordered, it has different tools here.

• 16:51Speaker 01

  Like, if I scroll over here, it can see, "Get my gear" is one tool, so it knows what I've ordered from here. It can get the cart, it can add coupons, right? So it can apply a coupon on checkout and all this stuff. So here, it's just saying, "The first thing you should buy is this Lolita Water Softener 2-pack." So I'll just say, "Cool, add that to my cart, that sounds great." Right? So, the nice thing is, is that I could tell it, highlight that on the UI, or I can just say, you know, whatever, I like the sound of that, go and add it to the cart, and it'll do all that stuff in real time, and I have visual confirmation of that. I can see the things, right? And I think that's pretty cool.

• 17:32Speaker 00

  That's really cool. I mean, come on, that's really cool.

• 17:35Speaker 01

  Yeah. So, and even tell me here, you have, Softener is in, you have a Barista 10 coupon, 10%, adding it for the rest. So.

• 17:47Speaker 00

  I don't know if it's just because I'm a coffee aficionado, you know, I love coffee, you know, you can see my coffee setup back there.

• 17:54Speaker 01

  Yeah.

• 17:55Speaker 00

  That this is just hitting for me so hard. But like, to me, it's like, it makes so much sense. Like, we're, as customers, we're going to be using agents. We're going to want them to go and do stuff for us. We want to make sure that the things that they do, it actually is able to complete the tasks. And to see this work just so seamlessly just is awesome.

• 18:16Speaker 01

  Yep. Yeah, it's really cool. I think, so, this is a great example, but you can think about anything where it kind of gets complicated. You know, technical stuff, if you're buying hard, like, hardware, and, I don't know, you need to, you're doing like hardware hacking, and you need to write the right battery for, for the development board, or car stuff, and you need the right parts, like, all this stuff that can be really complicated like that, this is a great use case.

• 18:42Speaker 00

  I mean, I'm just curious, you know, where MCP, in your mind, where MCP fits? Which I think is like another way of saying, you know, how do you, like, in which sectors, niches, should you be implementing Web MCP? Because there's going to be, like, some, some industries are going to be last to implement it, right? And I think from a founder perspective, I care about the, the ones that have the highest priority. So which are those and why do they matter?

• 19:12Speaker 01

  Yeah. Yeah, I think, like, like I said, these compatibility-driven commerce, right? So it's like, all those things, camera systems, any kind of web, web store that's complicated, that'll be a great thing. You could do it in SaaS admin. So like, any kind of admin board, or console, or analytics, or marketing tools, you can add these things in to make it easier for, you know, your marketing team to, to deal with these things, and, and set up features and stuff like that. And even like regulated industries, like, the nice thing is, is that you can't use API keys. So you don't want to go to, you don't really want to use MCP servers or APIs. You maybe want to set up a few, and that's the great thing about Web MCP.

• 19:55Speaker 01

  It's like, a few tools that are using the browser state that can, can be read-only, so they don't actually touch anything. So let's imagine like, insurance or banking self-service. Like, you could set up some Web MCP tools that are read-only, or only touch very non-sensitive settings. And then that will help the user figure out where they need to go to enter something, or where they need to, to go to, to get the right information. Or it can even summarize and pull the right information for them via their agent. So, stuff like that. I even think, internal tools, so building internal tools at a company.

• 20:35Speaker 01

  So if you're, like, a entrepreneur, you don't necessarily need to use Web MCP right away for your customers. And there might be a really great solution for you in-house. Like, your internal tools, stuff for your, for yourself, for your employees. That's where I think there's a lot of potential.

• 20:54Speaker 00

  I love it. All right, let's, let's go to some business ideas that people can implement. I'm curious your take on it, too. So, let me share my screen.

• 21:02Speaker 01

  Yeah.

• 21:03Speaker 00

  All right, Vinnie, so, Web, Web MCP is here. I wanted to come up with two business ideas that I think are cash-flowing, that I think are, anyone non-technical can set up, or, or somewhat non-technical. You just don't need to be like a hardcore engineer. The first idea is a Web MCP conversion agency. And I bet you there's probably some domains that are available, like, webmcp.agency, or something like that, that someone can go and grab right now. So, the, the big idea is, how can you make boring business websites agent-ready? So you have these boring businesses, like law firms, and home service, and HVAC, you know, med spas, dentists, and you just go and create these, you know, V1 tools for them.

• 21:48Speaker 00

  So that can be like requesting a quote, or booking consults. And you're just selling them, on this idea that, that there's going to be a new class of citizens on the internet. These are going to be these AI visitors. And these AI visitors, these agents, are going to book jobs, right? So you sell them on maybe a $2,000 to $10,000 setup. And then you charge, you know, could be $500 a month, or a few hundred dollars a month, $700, depending on who it is, is it a big law firm, a small law firm, on monitoring and evals. And then you, you build this retainer that, you know, is building cash for every single month. And you just update it, and that sort of thing. What do you think of this idea?

• 22:33Speaker 01

  Yeah, I actually think it's a really good idea. I see stuff on the web floating around where they're showing that, things like you said, dentists or law firms are starting to use agents at their offices. And so I think they'll get it. And it's good that you bring this up, because I think it's worth mentioning that Web MCP is an experimental feature in Chrome right now. So it launched in February, joint effort from Microsoft and Google. But it's still in early days. But that's why I think there's real potential here. Because we talked about this package, I showed the diagram of, you know, from headless to bound to UI, the different types of agent-native approaches you can use to connect to apps, right?

• 23:18Speaker 01

  So, you could do this as a package, where it's not only Web MCP, but other tools, maybe a MCP server for them. And you tell them that, like, look, this is new emerging stuff. Or, you're learning this because it is this new emerging stuff, so that when it does get adopted, you're the first mover, you have the first mover advantage. And so you can sell it as a package, like, we'll, we'll put in MCP, we'll put in Web MCP, we'll, we'll create, you know, whatever, all this stuff that, that aligns with their vision. You can make whatever they want available, and you can show them the different approaches. You have one that uses a UI, one that is headless, and you're the expert there.

• 24:02Speaker 01

  And that's the way that you make money.

• 24:05Speaker 00

  Yeah, maybe it's just agent conversion agency. And then Web MCP is just one of the, the technologies that you use.

• 24:12Speaker 01

  Yep. Or like we were saying before, internal tools. It doesn't only have to be about customer-facing stuff. You can show them how they can make processes in their office better for them and their employees using stuff like Web MCP.

• 24:25Speaker 00

  Totally. Cool. Startup idea number two. I'm calling it the Agent Mystery Shopper. So, it's testing whether agents can complete the most important user journeys. So, if you think about a user journey, maybe it's a Shopify store, you know, you want to buy a hoodie. If it's a, you know, consulting company, it's booking a console. If it's an insurance company, you're filing a claim, requesting quotes, ordering items, all these different things that you want the agent to do. So the agent is going to run a bunch of tests, and you, the customer, get a report back. Where did the agent get stuck? Were there bad descriptions? Were there missing tools? Conversion risk?

• 25:08Speaker 00

  And then you're basically selling, you know, agent reports, maybe it's monthly, weekly, and you turn the repeated fixes into software. So I like this business because it's pretty simple. It's almost like, you know, just a, a report, like a credit report almost, on, you know, how your, how your, your website and your apps are around implementing things like Web MCP. And then you can charge a few hundred dollars a month, or a hundred dollars a month for something like this. What do you think about this idea?

• 25:41Speaker 01

  Yeah, I think also, a cool thing, it makes a lot of sense. And the cool thing is, is that you could even pair approaches like this to your agent conversion agency, right? So it's like, you can go and run these agent tests and evals, and you can be, and you can show them that, hey, this might work better if you used Web MCP on top of it. You're only using X, why not check out this as well? So you can kind of combine the approaches, I think, here. So that's a really cool idea.

• 26:09Speaker 00

  I like it.

• 26:11Speaker 01

  Yeah, so I just also wanted to mention that, I showed a couple examples here, but there are 16 different tools that you can use with your agent via Web MCP. On this example, Espresso Machines and Gear Store. And you can do that right now. You can go to Crema and Co. client, fly.dev, we'll put the URL in the show notes and stuff. And you can test it out there. One thing you should know is that, like we said, it's experimental stuff, early days. So, go into Chrome Flags, enable Web MCP support, and go into Chrome Inspect and allow remote debugging. So, these are the things that you will want to enable, so that you can start using these experimental features.

• 26:52Speaker 01

  And if you want to build your own app like this, you can also click on the GitHub repo button down there next to the Web MCP Tools pill. And you can clone this repo, and you can play around with it, make your own version, whatever. It's free for you to start playing around with cool business ideas. So, those are two important things I think are worth mentioning. And yeah, it would be, it would be cool to see what other people do with this repo, what other people do with these ideas. So people should definitely share those online with us. I think that would be awesome to see.

• 27:26Speaker 00

  Yeah, we'd love to see it. And I think, you know, there's, I can just see the comment of someone saying, well, it's an experimental, it's, you know, it's so experimental, like, it's so, it's way too early. Like, why even bother playing with this stuff? And I, you know, you know me, I love playing when things are experimental. Because when, you know, the arbitrage exists when, when it's experimental. Like, I love trying things, getting my hands dirty, and, and seeing what I can build now. Because when it's going to be, you know, super popular, that's when that window starts closing.

• 28:02Speaker 01

  Yep, definitely. Think about when ChatGPT came out, or when GPT, I think it was GPT-2 and 3 came around, and people were playing with it and going, and it was just two years before ChatGPT launched, and people were going, ah, this is crap. This is, we're way off, we're years away from AI being like a serious thing, a serious tool. And then boom, the explosion happened just a year or two later. So like, shouldn't pass this stuff off as, you know, just like experimental stuff that's not going to get implemented. I mean, we're talking about Google here. They have pretty good foresight. This is something that they've been talking about for a few years now. They made the proposal two years ago, they launched it at the beginning of this year.

• 28:45Speaker 01

  So, I wouldn't, I wouldn't fade this personally. And I'm excited about it, so that, that's enough for me.

• 28:52Speaker 00

  All right. Thanks for coming on, Vince, sharing, bringing the sauce, and I'll see you next time.

• 28:56Speaker 01

  Yep.