The Blueprint Engine Explains Itself | Aug 24

Elena Reyes: Okay, so three episodes into planning this, and I still don't have a good answer for, wait, are we recording? Blake: We're recording. Elena Reyes: Cool. Okay. So here's the thing. If you're brand new, you might be sitting there going, "What even is this?" Blake: Fair question. Elena Reyes: This is Made on Mato. Every week we walk through what shipped on the platform, why it shipped, and what it actually means for you if you're running a show on it. Blake: That's the whole pitch. No fluff. Elena Reyes: I'm Elena. Blake: I'm Blake. And, um, no anchor here, no sidekick there. We're just two people who look at the same change log and sometimes disagree about it. Elena Reyes: Which happens more than you'd think. Blake: It does. Elena Reyes: And we're not gonna smooth that over for you. If we land somewhere different, you'll hear both sides. Blake: That's kind of the point of having two hosts instead of one. Elena Reyes: One more thing before we go further. This show is produced with AI. We're not hiding that. Blake: Yeah. The scripts, some of the voice work, a chunk of the editing, that's the process. Elena Reyes: Which is honestly kind of the perfect first topic. Blake: Because the platform we're talking about is the one that built the show that's talking about it. Elena Reyes: Right. It's a little recursive. Blake: A little. So before we get lost in that loop- Elena Reyes: Let's just say what Mato actually is. Blake: Yeah, let's start there. Elena Reyes: So Mato itself, founded in 2024 right here in LA by two guys, husbands actually, Alexander and Edward Benz. Blake: Founders behind their own product on their own show. Kind of an odd flex for episode one. Elena Reyes: Maybe. Mato's press kit calls itself the AI podcast engine. Blake: Which means what exactly in practice? Elena Reyes: An AI host does a live interview with a real human guest, someone actually sitting there answering questions. Blake: Real guest, AI interviewer. Got it. That's still a strange sentence to say out loud, isn't it? An AI conducting the interview. Elena Reyes: It is. But it's also kind of why we're doing this show, to actually watch it happen episode by episode. Blake: Fair enough. Elena Reyes: And after that, Mato handles the rest, editing, transcripts, clips, cover art, and pushes the finished episode out to more than 150 platforms. Blake: 150. That's Spotify, Apple, YouTube, and then 147 places nobody's heard of. Elena Reyes: Pretty much, yeah. Blake: Why does the platform count even matter for a show this size? Elena Reyes: Because distribution is usually the boring manual part, submitting your show everywhere one at a time. Madeo apparently automates that. Blake: So is the interview the actual selling point here, or is it everything that happens after? Elena Reyes: Bit of both, honestly. But the after part is where the time savings really show up. Blake: Okay, give me a number I can hold onto. Elena Reyes: The press kit says the whole thing, from recording to a finished, published episode normally takes eight to 12 hours of human work. Blake: A full workday, basically. Elena Reyes: More than one if you count editing on its own. And Madeo claims it does the same thing in about 30 minutes. Blake: 30 minutes. Elena Reyes: Yeah. Blake: That's the number I want to actually poke at later because that's a big claim to just take at face value. Elena Reyes: Fair. Blake: But before that, I want to sit on live interview for a second because that phrase is doing a lot of work. Elena Reyes: Go for it. Blake: Live to me means the AI is actually listening to what the guest says and picking the next question off that, not reading down a fixed list. Elena Reyes: That's the claim. Yeah. Blake: Picture an actual episode. Guest says something like, "Well, it's complicated." Does the AI actually ask why, or does it just move to the next line on the sheet? Elena Reyes: That's exactly the kind of thing I want to watch for as we keep doing this. Blake: Because if it's stitched together after the fact and just labeled live, that's a different show than the one being pitched. Elena Reyes: And if it's actually reacting in real time, that's a pretty different product than what most people picture when they hear AI podcast. Blake: So which is it for us specifically for what we're actually doing right now, recording this? Elena Reyes: Knowing the founders, the pitch, the platform count, none of that tells you what actually happens week to week on this show. Blake: Founding story. Guest promise distribution numbers. None of it is the workflow. Elena Reyes: We'll know it when we see it, a real follow-up on tape versus something that just sounds like one after editing. Blake: That's the test I want to hold this show to. Honestly, not just Madeo's guests. Elena Reyes: Right. So next, let's walk through what a Madeo week actually looks like, start to finish. Okay, so we know what Madeo is now. Founders, the guest thing, the platforms, got it. Blake: Got it in theory. Elena Reyes: Sure. But what does this show actually do with all that week to week? Like, what are you tuning in for? Blake: Three things, basically. First one's the change log. Every time Mato ships something, a new feature, a fix, whatever, we talk about it here. Elena Reyes: And not just here's the new button. We want the why. Who was annoyed enough to ask for it? What it used to do before. What broke when they turned it on? Blake: Because something always breaks a little. Elena Reyes: Always. Blake: Give me an example, actually. Something concrete, not hypothetical. Elena Reyes: Sure. Say a feature ships that lets you swap host voices mid-series. We talk about who asked for that, what limitation it papered over, and whether it actually holds up in practice or just looks good in a demo. Blake: Second thing is the blog. If Mato posts something, we're not gonna read it to you. Elena Reyes: God, no. Blake: We're gonna talk about the stuff that got cut. The paragraph that didn't make it, the number that got rounded off, the internal argument behind a decision. Elena Reyes: Right. The stuff a blog post can't really carry because it has to sound clean. Blake: Exactly. A post has to commit to one version of the story. We don't. Elena Reyes: And then the third piece, most weeks we're not doing this alone. Blake: A customer joins, somebody actually running a show on the platform. Elena Reyes: And we ask them the boring questions like, how long did booking a guest actually take you? What did your team do with the transcript afterward? Which clip actually got views versus which one you thought would? Blake: The stuff that never makes it into a testimonial. Elena Reyes: Yeah. Nobody puts the clip I hated did the numbers on a landing page. Blake: Probably should, though. Elena Reyes: I mean, think about it from a listener's side too. If we only ever hear the wins, we don't actually learn anything about running a show. Blake: Right. The failures are where the actual lessons live. Anyone can post a win. Elena Reyes: Okay, so changelog, blog, guest. That's the shape of the show. Blake: That's the shape. But I wanna flag something because it's been sitting with me. Elena Reyes: Go for it. Blake: Mato makes this show about Mato using Mato. Elena Reyes: Right, the recursion thing again. Blake: So how does anyone listening know this isn't just marketing wearing a headset? Like, why would we ever say something's broken if the company making the podcast also makes the product? Elena Reyes: That's fair. I don't think we resolve that today. I think we just keep it in view. Blake: Same bucket as the Live interview question from before. Elena Reyes: Two threads. Is the AI actually reacting in the moment? And is this show actually honest about its own company? Blake: Neither one goes away because we said the word transparency once. Elena Reyes: No, it doesn't work like that. Blake: It's easy to say we'll be honest in an INTRO episode. Harder three months in when something ships broken and it's embarrassing to talk about. Elena Reyes: That's exactly the test. If we ever go quiet on a bad ship, call us on it. Blake: So here's how I'd answer it. At least partly, the show itself is supposed to be the proof. Today's episode is an example of the thing it's describing. Elena Reyes: Wait, meaning what exactly? Blake: Meaning the process that built this episode, the planning, the structure, that's not hidden. We can open it up and show you. Elena Reyes: Like, actually show the mechanics. Blake: Yeah. And it turns out there's a fresh one to point at. Something changed in how this got produced, and it shipped this week. Elena Reyes: Wait, this week? As in this episode? Blake: This episode. Elena Reyes: Okay, now I'm actually curious. Don't just tell me, show me. Blake: That's the plan. Let's open it up. So the fresh example is Alexander's post. It went up on the site this week called Introducing Blueprint. Elena Reyes: Wait, our own Blueprint, like this episode's Blueprint? Blake: This exact one. Elena Reyes: Okay, that's a little wild. Blake: Alexander's post lays out that every episode now starts as a typed plan before a single line of script gets written. The plan, meaning what exactly? Elena Reyes: Meaning the structure gets locked first. Blake: Meaning the structure gets locked first. Segments, points, sources, all of it before anything sounds like a podcast. Elena Reyes: So the plan comes first, then the words get poured into it. Blake: Right. And the post says the arithmetic in that plan, like segment lengths, gets checked in code, not eyeballed. Elena Reyes: Checked in code. So if a beat's supposed to run three minutes and it doesn't add up- Blake: It gets flagged before a generation even starts. Elena Reyes: Huh. Blake: It also means catching a smaller mistake, like a segment that reads long but actually times out short once it's read out loud. Elena Reyes: Which is a pretty specific kind of bug to design for. Blake: And after the script exists, it gets reviewed against the sources it's citing, so the claims have to trace back to something real. Elena Reyes: That's the part I actually care about, not the timing math, the fact-checking part. Blake: Same. According to the post, if the script can't back a claim, the system Refuses to run it. Elena Reyes: Refuses how? Like, it just stops? Blake: The post doesn't get into the mechanics, just says it won't ship what it can't support. Elena Reyes: Fair enough. I'll take it at face value for now. Blake: There's also a before answer in there. Same show, once without the plan, once with it. Elena Reyes: Oh, I wanna hear that. Blake: I haven't listened side by side yet, but that's apparently the point of posting it. Elena Reyes: Let people judge instead of trusting the description. Blake: Exactly what it's there for. Elena Reyes: Even without listening side by side, just knowing that comparison exists changes how I read the rest of this. Blake: Same. It's one thing to say trust the process, it's another to actually let people check your work. Elena Reyes: Okay, so this is the thing you flagged earlier. Blake, remember at the top you weren't sure if the AI host was reacting live or if it all got put together after? Blake: Right. And I think this is the answer, or at least an answer. The plan is the mechanism that's supposed to keep the whole show honest. It decides what gets said before anything gets said. Elena Reyes: See, I'm with you until the Refuses part. A refusal rule is only as good as what it's checking against. Blake: Meaning? Elena Reyes: Meaning if the evidence it's citing is thin or wrong or just one blog post from the company itself. Blake: Like the one we're literally citing right now. Elena Reyes: Exactly like that one. Itll confidently Refuses to say something false, sure, but it can still confidently say something true and shallow. Blake: Thats fair. Discipline in the process doesn't guarantee depth in the sourcing. Elena Reyes: Right. It just guarantees the math checks out and the citations exist. Blake: Which honestly is still more than most shows can claim. Elena Reyes: Low bar, but sure, I'll give it that. Blake: And to be fair, that- that's a low bar we're both climbing over too, citing one company blog post to explain a company blog post. Elena Reyes: Sure, but at least we're saying that part out loud instead of pretending it's neutral. Blake: So where does that leave us on trust? Elena Reyes: Genuinely, I think it's better than nothing. It's not blind faith, and it's not full transparency either. It's somewhere in between. Blake: I can live with somewhere in between. Elena Reyes: Okay, so process-wise, this actually sounds pretty Discipline. Plan first, math checked, sources reviewed. Blake: Sounds like it. Elena Reyes: But none of that tells me what it costs or how long it takes to go from a blank plan to something we'd actually put out. Blake: That's a fair thing to ask about next. Elena Reyes: Okay, numbers. I'm ready. Blake: Mato's About page puts traditional podcast production at fifteen to twenty-five dollars a finished minute. Elena Reyes: Per minute? Blake: Per minute. So a 30-minute episode, they're saying eight hundred to two grand depending on who you hire. Elena Reyes: Wait, that's just for editing and stuff, not even the mics? Blake: That's the range they cite. Studio time, editors, someone cutting clips, it adds up fast. Elena Reyes: Okay, so where does Mato land in that? Blake: Fifty bucks flat per published episode according to the How It Works page. Elena Reyes: Fifty. Not fifty an hour. Blake: Per episode. Elena Reyes: That's a rounding error compared to the other number. Blake: Although fifty dollars a episode doesn't tell you what happens if you want more than the baseline. Extra revisions, a longer episode, more channels. The page doesn't spell that out. Elena Reyes: Right. Flat rate can still hide a bunch of tiers underneath it. We should ask about that too. Blake: It is. And that same About page calls the company a third way, sits between the expensive human crew and the cheap AI slob nobody trusts. Elena Reyes: Right. That's the pitch on the tin. Blake: The How It Works page also lays out the actual steps. Six of them, idea to published, and they say the whole thing takes about thirty minutes of your time. Elena Reyes: Thirty minutes for the user, though, not thirty minutes total. Blake: That's the distinction I wanna sit on. Elena Reyes: Because the machine's still chewing on it in the background. Blake: Right. So what is a customer actually doing in those thirty minutes? Are they picking topics, approving a script, sitting through the interview live? Elena Reyes: Or are they just clicking six buttons and walking away while something else does the work for an hour? Blake: Because thirty minutes of your time and thirty minutes and the episode's done are two completely different products, even if the price tag is the same. Elena Reyes: One of those is a genuinely fast workflow. The other one's just a fast checkout screen. Blake: That's what I wanna ask the next guest we bring on. Not the marketing version, the actual timestamped version. What did you do? When? For how long? Elena Reyes: Because fifty dollars sounds great until you find out it took someone four hours of babysitting to get there. Blake: Exactly. Or it sounds great because it actually is thirty minutes and the rest runs itself. Elena Reyes: Either way, we should ask every single guest that. Blake: Everyone. Same six questions, roughly. Elena Reyes: We're gonna sound like we're doing an audit. Blake: Kind of the point. Elena Reyes: Fair. Blake: It also matters for expectations. If someone signs up expecting thirty minutes total, and it's actually thirty minutes of clicking plus an hour of waiting, that's not a lie exactly, but it's not the full picture either. Elena Reyes: Which is exactly the gap between a marketing page and an actual workflow log. Blake: So we've got the cost, we've got the claim time, and we've got the internal process from the blog post. Elena Reyes: Right. The whole documented refusal thing from before. Blake: All of that's fine on paper. Elena Reyes: But paper isn't a show. Blake: No. So the process is fast. The reasoning's written down somewhere. Does any of it actually hold up when it's a real show with a real guest being made for real? Elena Reyes: That's the only thing left to check. So does any of this actually hold up outside a blog post? Mato put out a press release recently. Blake: Ooh, receipts. What's it say? Elena Reyes: Their founder, Alex Benz, is quoted saying they crossed ten thousand listeners across all their shows in thirty days. Blake: Ten thousand in a month? That's not nothing for a platform this new. Elena Reyes: Right, and it's the CEO's own number, so take it as a claim, not an audit. Blake: Fair. What else is in there? Elena Reyes: Same release says four enterprise customers, something like ten thousand dollars a month in recurring revenue. Blake: Okay, so real money, but small money. Elena Reyes: Small money. It also says over thirty active AI-hosted shows running right now, and a seed round they're calling pending for this year. Blake: Pending meaning not closed. Elena Reyes: Meaning not closed. I'd want to see that actually land before I count it. Blake: Same. Numbers that haven't happened yet don't count as numbers. Elena Reyes: Exactly. But thirty shows and four enterprise deals, that's a company with actual customers, not just a demo. Blake: Thirty shows is also useful context for us specifically. It means we're not the only experiment running on this thing. Elena Reyes: Right. There's a whole portfolio out there we could eventually point to instead of just Mato's own numbers. Blake: Speaking of customers, their homepage has this one case study I keep thinking about. Elena Reyes: The Wealth one? Blake: Yeah. It's called The Wealth Conversation. It's on their business tier, and the guests are local CPAs and estate attorneys. Elena Reyes: And? Blake: The site says those episodes convert two to three prospects into actual clients every month. Elena Reyes: Two or three clients a month from a podcast. Blake: From a podcast. For a CPA, one new client can be worth way more than fifty bucks an episode. Elena Reyes: So the math isn't download counts at all. Blake: No. It's whether the guest walked away with business. Elena Reyes: That's the number nobody puts on a slide, though. Nobody brags about downloads to their accountant. Blake: True. Downloads don't pay your mortgage. Elena Reyes: And that's really the whole shift, isn't it? For a business show, the download count was always a proxy for something else. Turns out the something else is bookable. Blake: Which is a very different pitch than look how many people pressed play. Elena Reyes: So if we're bringing customers on this show- Blake: We ask about that. Bookings, how long it took to land the guest, whether they got a client out of it, whether they came back for a second episode. Elena Reyes: Not just did the episode publish. Blake: Right. Did it do anything? That's the standing question for every guest segment going forward. Elena Reyes: We should probably ask the same thing about ourselves eventually. Honestly, whether this show is actually moving anything for Motto beyond just existing. Blake: Yeah. Add that to the pile of things we're supposed to keep checking on. Elena Reyes: All right. I think that's the traction picture as it stands. Blake: A young company, some real revenue, one strong case study, and a lot still to prove. Elena Reyes: Which feels like a fair place to hand this to you for the wrap. Blake: I'll take it from here. So if you want the actual change log, the blog posts, all of it written down, that's himotto.com. Elena Reyes: Yeah. We're not gonna read you every line item every week. Go look. Blake: And if you're a podcaster, or you're on a marketing team, and you're running a show on Motto or thinking about it, email hello@himotto.com. Elena Reyes: We want you on here. Not as a favor. We want the boring details. Booking time, transcripts, what clip actually got watched. Blake: Real numbers, not just ours. Elena Reyes: And if you've got a number that contradicts something we said today, send that too. We'd rather hear it now than keep repeating it. Blake: Seriously, that inbox is not just for guest pitches. Elena Reyes: Right before we start grading our own homework every week. Blake: So that's the ask. Subscribe wherever you're listening and come back next week. There'll be another thing that shipped, another reason behind it. Elena Reyes: Honestly, I came in kind of skeptical an AI show could report on its own company straight. Blake: And? Elena Reyes: I still want to see it hold up over a few more of these, but today it did. Blake: That's fair. That's all we're asking anyone to do. Watch it hold up. Elena Reyes: See you next week.