Mato takes Mucker Capital funding | Sep 8

Elena Reyes: Okay, so this week, Mato shipped a drag and drop calendar that rebalances your whole publishing week for you, and it builds a heat map out of your own playback data. Blake: Which sounds small until you realize it's telling you exactly when your audience actually shows up. Elena Reyes: Right. I'm Elena. Blake: I'm Blake, and this is Made on Mato. Elena Reyes: So the calendar page says it does this burst-tail thing, front-loading clips across platforms. Blake: Burst-tail, meaning heavy at the start, then it tapers off? Elena Reyes: That's basically it. Yeah. Blake: Huh. Elena Reyes: And apparently, it just skips Saturdays by default. Blake: Wait, why Saturday specifically? Elena Reyes: I don't know yet. That's the thing we're getting into. Blake: Okay. Also, there's the SMS QA mechanics we should touch on. Elena Reyes: Smaller item. Yeah, we'll get there. Blake: And the actual headline this week isn't a feature at all. Elena Reyes: No, it is not. Blake: Mato took funding. Mucker Capital. Elena Reyes: Which changes how we should be reading everything else in this episode, honestly. Blake: We'll hold that thought too. Elena Reyes: So the calendar, the heat map, what it actually replaces day to day. Okay, so the calendar rebalances your week. We covered that. But the part that actually got me was the posting pattern underneath it. Blake: The clip distribution? Elena Reyes: Yeah. Mato's own page on this says clips go out front-loaded like a bunch right up top, then a tail trailing off across the rest of the week instead of just dumping everything at once. Blake: So it's not spray and pray. It's more like a wave that breaks early and then settles. Elena Reyes: Exactly. Big splash Monday, small ripples through Friday. Blake: Who actually asked for that shape, though? Like, why front load it? Elena Reyes: I think it's just how audio actually gets consumed. People bite on new stuff fast, then it decays. The page doesn't explain the reasoning in detail. It just states the pattern. Blake: Fair. And there's a default baked in too, right? Elena Reyes: Right. The scheduler treats Saturday as a day off by default. No posts land there unless you tell it otherwise. Blake: Wait, why Saturday specifically? Elena Reyes: No idea. That's the thing. It doesn't say. It's just a quiet day default, presumably because most shows see dead air on Saturdays. Blake: But that's the exact thing their own heat map is supposed to catch. Elena Reyes: Right. Blake: If my show's playback data shows Saturday's actually my second-best day, why is the tool overriding that with a blanket rule? Elena Reyes: I mean, come on. That does feel backwards. You build a heat map off my listening data and then ignore it for one day of the week. Blake: It's not that Saturday defaults are wrong for everybody. Some shows genuinely go dead on weekends. Elena Reyes: Sure. Blake: But it should be a one-click override, not something you have to dig for. Elena Reyes: Do you know if it even is one click? Blake: I didn't test it, honestly. The page doesn't say how buried the toggle is. Elena Reyes: That's the gap for me. Great, you built the default off aggregate behavior. Now let me override it off my own numbers just as easily. Blake: Yeah. Defaults are fine as long as the exit is fast. Elena Reyes: Otherwise, it's just a rule wearing a suggestion's clothes. Blake: That's a way to put it. Elena Reyes: Let's make this concrete for a second. Say I've got five clips for the week. Blake: Okay. Elena Reyes: Front-loaded means what? Three go out Monday, and the other two trickle through the week. Blake: That's the shape the page describes, yeah. Heavy at the front, tapering toward Friday. It doesn't give you the exact split, just the pattern. Elena Reyes: Right. So I couldn't tell you if it's three and two or four and one. No. Blake: And it doesn't say whether that ratio is fixed or adjusts based on how a clip performs early on. Which would actually be the more useful version. on how a clip performs early on. Elena Reyes: Which would actually be the more useful version. A static front load doesn't know if Tuesday's clip is dying. Blake: Exactly. That's the open question for me. Does the burst-tail pattern mean a fixed shape or one that reacts to your numbers as the week goes? Elena Reyes: For now, I just want the fixed version documented, so I'm not guessing which day to load up on. Blake: Same. If it's static, tell me static. If it's adaptive, tell me what it's adapting on. Elena Reyes: Anyway, that's the calendar. Front-loaded posting, quiet day defaults, argue with your heat map if you want. Blake: There's another inbox thing that shipped this quarter too, and it's a smaller item, but it's got its own headaches. Elena Reyes: The text one? Blake: Yeah. Listeners can text questions in now, and somehow that turns into audio in an episode. I want to know how that actually works mechanically. Elena Reyes: Same, because on paper it sounds simple, and I don't think it is. Okay, so the other inbox thing, texts. Listeners can text in a question to the show's number. Blake: Right. And there's a step people skip past. You actually have to confirm you want in. Elena Reyes: Yeah. You reply YES or START first. It's not just fire off a text and you're done. Blake: Double opt-in. Standard stuff for texting programs, but it's still a step. Elena Reyes: Which if you've ever tried to get someone to do two things instead of one- Blake: You lose some of them right there. Elena Reyes: Totally. And then Mato's terms page lays out what happens after that. You might get an update if your question gets reviewed. Blake: Or answered or actually featured in an episode. Elena Reyes: Right. So three different outcomes, three different texts potentially. Blake: Plus the boilerplate message and data rates may apply. Reply STOP to opt out. HELP for help. All the stuff carriers make you say. Elena Reyes: Which nobody reads, but it has to be there. Blake: I mean, for a show trying to build a habit out of this, like get people texting in every week, that opt-in step is friction. Elena Reyes: It's small, but it's real. You're asking someone to do two things before their question even gets read. Blake: Right. Worth watching whether shows that lean on this actually keep people opted in. Elena Reyes: Here's what I keep picturing. Someone driving. Hears the show, fires off a text with a question. Blake: Right in the moment, that's the best version of this feature. Elena Reyes: But then they get the auto-reply asking them to text YES or START, and by the time they're somewhere they can actually do that, some percentage of them just don't. Blake: Because the impulse already passed. Elena Reyes: Exactly. The terms page doesn't say what fraction of people actually complete that second step, so we don't have a real number here. Blake: No, we're speculating on the size of the drop-off, not the existence of it. The friction is real, we just can't quantify it from what's published. Elena Reyes: Fair. I just want to show hosts to know going in that the SMS version is the one Mato ships with, not one you can currently simplify away. Blake: Right. Plan your call to action around it. Don't tell listeners, "Text your question," without also telling them they'll need to confirm. Elena Reyes: Speaking of things worth watching, this feels like a good spot to mention who's actually paying the bills here. Blake: Smooth. Elena Reyes: This show is made on Mato, and if you've been sitting on the idea of starting a podcast for your company, now is actually a decent time to do it. Blake: For a limited time, when you sign up for Mato, they throw in a custom cover design, white glove onboarding, an actual custom jingle, and a spot on their promotional list. Elena Reyes: That whole package is worth five thousand dollars. Blake: Head to hemato.com to get started. Elena Reyes: Okay, so texting in a question, that's the small feature. Blake: There's a bigger thing this week, though. Elena Reyes: Yeah. Before we go back to more feature stuff, there's actual company news that landed. Blake: Not a change log item, a funding thing. Elena Reyes: Which changes the whole flavor of the episode, honestly. Okay, so company news. Mato took money. Blake: From Mucker Capital. Elena Reyes: Yeah. Press release dropped September second, out of Los Angeles. Blake: I read it twice. Elena Reyes: Same. It's got that whole, "AI-native platform for turning expert conversations into scalable business media," line in there. Blake: Mm-hmm. Elena Reyes: Which is a lot of words to describe us, basically. Blake: Right. That's the thing. It's describing the company that made this podcast. Elena Reyes: Wild to read your own tool described like that in a press release. Blake: It reads like it's for investors, not for us. Elena Reyes: Well, it is for investors. Blake: Sure, but I want to know what changes. Does a check like this mean the scheduling calendar we just talked about gets built faster? Does the SMS thing get fixed? Elena Reyes: Or does it just mean the language changes and nothing on the product side moves at all? Blake: That's my actual question. Money coming in doesn't automatically mean the backlog moves. Elena Reyes: I mean, sometimes it does. Hiring more engineers, things ship quicker. Blake: Sometimes it just buys a bigger stage for the same pitch. Elena Reyes: Okay, cynic. Blake: I'm not being a cynic, I'm being specific. An AI-native platform is a category claim. It's not a feature. Elena Reyes: Fair, but companies do talk different once they've raised. Have you noticed that? Blake: Totally. The vocabulary shifts before the product does, every time. Elena Reyes: So which is this week? Did Mato actually change or did Mato just get a new way to talk about itself? Blake: I genuinely don't know yet, and I don't think we should pretend we do. Elena Reyes: Yeah. I'm not resolving that one today. Blake: Me neither. I'll say this, though. A Los Angeles dateline and a named investor is a different kind of announcement than a change log post. Elena Reyes: Way different tone. One's an engineer writing what shipped. The other's a founder writing what the company's becoming. Blake: And that second one is aimed at other investors way more than it's aimed at us. Elena Reyes: Can we make that concrete, though? Like, what would actually change if I'm a podcaster on this platform today? Blake: Best case, some of that capital goes into fixing the actual rough edges, the Saturday default thing we were just complaining about, the double opt-in friction. Elena Reyes: Worst case? Blake: Worst case, it goes into more press releases like this one, and the product roadmap doesn't move any faster than it already was. Elena Reyes: There's no way for us to know which one it is from a press release alone. Blake: Two, a funding announcement tells you money moved. It doesn't tell you where it's going. Elena Reyes: Which is sort of the whole problem with covering funding news as a product show. The thing we actually care about, shipped features, isn't what this document is for. So who's actually behind this thing, Blake? Blake: Mato's press kit lays it out. Founded in two thousand twenty-four by two guys, Alexander and Edward Benz. They're married, and they run it out of Los Angeles. Elena Reyes: Wait, husbands running the company together? That's kind of sweet, actually. Blake: It is. Alexander's the one with the marketing background. He'd already started an agency called Blikket before any of this. Elena Reyes: Blikket. Never heard of it. Blake: Most people haven't, but here's the part that got me. He didn't set out to build a podcast platform. He started building Mato just to promote Blikket. Elena Reyes: Hold on, so Mato was basically a side tool? Blake: According to the press kit, yeah. A promotional thing that turned into the whole product. Elena Reyes: So the tail wagged the dog. Blake: Pretty much. And then Edward's side is engineering. He's the one behind the live interview architecture, the actual guts of how the AI hosting works. Elena Reyes: Okay, so one husband's the marketer, one's the builder. Blake: Right. And once you know that split, the pitch makes a lot more sense. Elena Reyes: Meaning what? Blake: Meaning the guy who wrote the September release calling this an AI-native initiative platform. That's a marketing founder talking, not a neutral third party describing the company. Elena Reyes: Sure, but every founder markets their own company. That's not exactly a scandal. Blake: No, it's not. I'm not saying it's dishonest. I'm saying it explains the register. You start an agency, you learn how to write a press release that sounds bigger than the actual feature list. Elena Reyes: Right. Right. It's just good marketing instincts showing up in the marketing. Blake: Exactly. Which is fine. It just means we shouldn't read the pitch as some independent assessment of where the product actually is. Elena Reyes: Does the press kit say anything about what Blikket actually did? Or is that as far as it goes? Blake: That's as far as it goes. It's named as a marketing agency. Nothing more granular than that. Elena Reyes: Fair enough. So we're not going to pretend we know more about it than we do. Blake: Right. We're not going to invent a client list here. Elena Reyes: Please don't. Blake: I do think it's worth sitting with the shape of it, though. The same guy who once wrote copy to sell an agency services is now writing the copy that sells Mato to investors. Elena Reyes: Which isn't a red flag by itself. Blake: No Founders selling their own company is the whole genre. I just think listeners should know the pitch and the product are being described by the same person who spent years getting good at describing things persuasively. Elena Reyes: And on the engineering side, Edward's the one actually building the live interview piece, so that's a separate skill set holding up the other half of the company. Blake: Right. One half builds it, one half sells it. That's a pretty normal founder split, honestly, and it just means when we read the big claims, we should remember which founder is likely holding the pen. Elena Reyes: So basically, we know why it sounds the way it sounds. Now the question is whether the substance backs it up. Blake: That's the move. Mato's put out numbers before in their own releases before Mucker was ever in the picture. Elena Reyes: Oh, like actual claims we can go check? Blake: Yeah. Older press stuff. Download counts, listener figures. Their own words, not ours. Elena Reyes: Okay. Now, I want to go pull those up and see if they still hold. Blake: Let's do exactly that. Elena Reyes: Okay, so I pulled up an old release, May 2026. This year, but before all the Mucker stuff. Blake: What's it say? Elena Reyes: Mato says podcasts on its platform crossed 10,000 total listeners in 30 days. Blake: 10,000 across the whole platform or one show? Elena Reyes: Whole platform. And they list four enterprise customers, something like $10,000 a month in recurring revenue, and more than 30 active AI-hosted shows. Blake: 30 shows producing 10,000 listeners total. That's not even 350 listeners a show. Elena Reyes: Yeah. When you spread it out, it's a lot less impressive than the headline number. Blake: Right. And monthly recurring revenue of 10 grand across four enterprise clients, that's 2,500 a customer, roughly. Elena Reyes: 2,500 a month per enterprise account. Is that a lot for what they're getting or priced low for an AI-native media company? Blake: No way to know from the release. There's no tier pricing listed here, just the aggregate number. Elena Reyes: Fair. We're not going to reverse engineer their pricing sheet from one line in a press release. Blake: Right. What we can say is four customers at that blended rate isn't a lot of enterprise logos four months in. Elena Reyes: Compared to what, though? We don't have another company's numbers to stack it against. Blake: True. I don't wanna pretend we've got a benchmark we don't have. It's just four. On its own, that's still early. Elena Reyes: Early isn't a knock necessarily. Blake: No, it's just early. That's the whole point. This is a snapshot from four months ago, not a verdict. Elena Reyes: There's a quote in here too. Alex Benz says the milestone shows audiences, quote, "Are willing to engage with AI-hosted interviews." Blake: That's a big claim to hang on 10,000 listeners spread across 30 shows. Elena Reyes: I mean, it's not nothing. It's just not proof of a trend either. Blake: So what do we actually have that's more recent than May? Elena Reyes: Their own homepage right now points to one case, a show called The Wealth Conversation. Blake: What tier is that on? Elena Reyes: Business tier. And it says that show generates two to three client prospects a month, interviewing local CPAs and estate attorneys. Blake: Two to three leads a month for one show. Elena Reyes: One show. Not a platform average, not even a second example alongside it. Blake: Wait, that's the only customer story they've got up right now? Elena Reyes: I mean, it might just be that it's their best story right now, not that it's literally the only customer. Blake: Maybe, but if there were three more sitting behind it, you'd think a homepage would show at least one more logo. Elena Reyes: Fair point. This is what they chose to put front and center. Blake: Which tells you it's probably close to their strongest current example, not a weak one they forgot to swap out. Elena Reyes: That's the one they lead with. Blake: So four months ago, it's 10,000 listeners and 30 shows. Now the pitch is one CPA podcast generating a couple leads a month. Elena Reyes: Different kind of proof. One's a volume number, one's an outcome number. Blake: I keep coming back to whether a four-month-old self-reported number is even the right thing to hold up next to a funding announcement that just happened. Elena Reyes: You don't think it's fair game? Blake: I think it's fair to ask about. I don't think we can say it still holds. Nobody's published anything newer. Elena Reyes: So we're stuck with old numbers and one anecdote. Blake: Basically. Somebody could go ask Mato for a September number and actually get an answer. Elena Reyes: Until then, it's a milestone from before Mucker was in the picture, and a legend story for one accounting adjacent show. Blake: Yeah. Draw your own conclusion. Elena Reyes: That's the rundown for this week. Blake: Quick word from the folks actually paying the bills on this feed, and we'll be right back. Elena Reyes: Okay, so where does that leave us? Blake: Honestly, watching next week, whether the product catches up to the pitch, that's the thing I wanna see. Elena Reyes: Same. I'm not saying the raise is fake. I'm saying the receipts are old. Blake: Right. And a new investor doesn't rewrite the receipts. Elena Reyes: No, it does not. Blake: So we'll come back to it. Elena Reyes: One more thing I wanna flag before we move on. It'd genuinely be worth someone calling Mato directly for a September number instead of us just guessing at where things stand now. Blake: Agreed. If Mato wants to publish something newer, we'll cover it exactly the same way we covered the old one. Numbers on the table. No spin, whichever direction they point. Elena Reyes: That's really all we're asking for, honestly. Blake: Same standard either direction, whether the news ends up flattering them or not. Elena Reyes: We will. All right, quick housekeeping before we go. Blake: Go ahead. Elena Reyes: If you want the full changelog, every post, all the detail we didn't read out loud, that's at hiMato.com. Blake: And if you're running a show on Mato and you wanna come on and talk about it, actually talk about it, not just get name checked. Elena Reyes: Emails, hello@himato.com. We read those. Blake: We do. Elena Reyes: And obviously, subscribe wherever you're hearing this. Costs you nothing, helps us a lot. Blake: It really does. Elena Reyes: All right, that's the week. Blake: Go check the receipts yourself. Don't just take our word for it. Elena Reyes: See you next week.