8:42 AM - The Dashboard
I open my laptop with my second coffee. The PodcastAI dashboard loads and I can already see the overnight activity. Three new signups. One from a subreddit thread I seeded two weeks ago in r/podcasting, another from a Podchaser forum link, and one that came through an affiliate partner at Buzzsprout. The Slack notification I got at 6:47 AM is still pinned to my phone. It's good. Not explosive, but steady. This is week two of month two, and I'm learning that "steady" is the baseline I should expect.
Revenue so far today: $47 from one of the new free trials converting to the $25 monthly plan last night. The customer is someone named Derek Kimball who runs a true crime podcast network and apparently decided mid-Monday that he couldn't keep doing manual transcript editing himself. I make a note to check on his onboarding later.
The inbox has seventeen items. Fifteen are automated agent notifications. Two are actual customer emails. This is the rhythm now: the AI agent handles the detection work, the initial response drafting, the flagging of patterns and edge cases. I handle the judgment calls and the humans.
9:15 AM - Agent Review
I click into the Scheduled Outreach tab. The agent drafted eight onboarding emails overnight for new users who haven't opened the product yet after signup. This is one of the core loops: the system tracks user behavior, detects people who might churn, and prepares outreach. I'm the final check.
The first draft to Carol Reyes at Reyes Family Practice is solid. She runs a wellness podcast and has a free trial active for three days. The agent's draft acknowledges her podcast topic, mentions the specific pain point (she noted "60 minutes of editing per episode" in her signup form), and walks through the first feature she needs: batch transcription. I approve it with a one-word edit - change "We help thousands" to "We're trusted by" - and it goes out.
The third draft is worse. The agent addressed Marco Chen (who runs a comedy podcast collective) with language about "streamlining your workflow." That's generic corporate template language. I delete that draft entirely and write my own version. I mention something specific I found in his podcast about repurposing clips for TikTok - clearly something he cares about. I point him to our clip-generation feature. It takes me four minutes. The agent's version would have been ignored.
Two of the drafts are correctly flagged with yellow warnings: customers who signed up with team email addresses but haven't created separate accounts for all team members. These are likely to stall. I make a note to add "team accounts" to our help documentation. The agent has no way to move these forward; this is a product gap, not a customer support gap.
10:47 AM - The Conflict
A Slack alert comes through with a red flag. A customer, Lisa Tanaka (runs a scripted fiction podcast production company), hit her monthly transcription limit on day 12 of her billing cycle. The agent marked it as "possible billing misunderstanding" because her plan shows she added a second podcast feed two days ago but didn't upgrade her tier.
I open her account. The agent is right. She's got two feeds running against a single-podcast plan. The agent already drafted a proactive email explaining the upgrade path and the cost. But I notice something else: she's using a special plugin for diarization (speaker identification) that's only available on our higher tier, and she's not on it. That's the real issue. She's paying for a plan that technically doesn't include what she's actually using.
I don't send the agent's standard upgrade email. Instead, I write to Lisa directly. I explain what I'm seeing, acknowledge that the interface could have been clearer about tier features, and offer her two options: a one-month credit that covers her overage while she decides on a permanent upgrade, or a downgrade back to a single-feed plan if she's not ready to scale. This is the kind of thing that keeps people or loses them forever. I'm betting on keeping her.
I also flag this in our Linear project under "Product." The tier explanation needs to be redesigned. The agent logs this automatically, but I add a comment about Lisa's specific path to the bug. These details matter when the designer fixes it.
12:23 PM - Metrics and Lunch
I open the Stripe dashboard while I eat a sandwich. Week-to-date signups: forty-one. Week-to-date MRR from new customers: $612. Churn this week: two customers. One was inactive from day one (I recognize the name - they were probably just browsing). The other is a customer named James Park who I notice signed up on April 15th. He lasted exactly three weeks. I click into his account.
He used the product once, uploaded a single episode, and never came back. No support requests, no complaints. Maybe the transcription quality wasn't good enough for his use case. Maybe he found something else. Maybe he realized he didn't have the time. I'll never know unless I email him directly, and there's a risk of annoying someone who's already decided. I add him to a "Win Back" sequence the agent maintains, but I lower the priority. Some churn is just churn.
The Podchaser affiliate link is converting better than Reddit. I make a note to deepen that relationship. Reddit gets me volume; Podchaser gets me quality.
My pipeline is twelve people currently in a free trial (down from eighteen last week - some have converted, some have churned, some are still evaluating). The conversion rate this month is tracking at 31 percent. Month one it was 22 percent. That's the product working better, or my onboarding emails working better, or both.
1:47 PM - A Bug and a Fix
I notice something in the Slack alert stream. Three invoices failed to generate this morning for customers renewing their monthly billing. This is bad. It means the Stripe webhook isn't properly parsing the custom field I added last week for plan tier documentation. It's a small bug but it breaks the payment flow.
I open the codebase. I can code, but I'm slow. It takes me eighteen minutes to find the issue (the Stripe request is passing a nested JSON object when it should pass a flat string) and fix it. I test it against a sandbox invoice. It works. I push it to production. This is the kind of work I didn't expect to do anymore when I bought this engine, but it's also the kind of work that's impossible to fully automate. I need to own the system.
I send the three affected customers a quick email letting them know the issue is resolved and their next invoice will process without issue. Two of them are people I've communicated with already (Derek Kimball, and Carol Reyes). The personal touch matters.
3:15 PM - A Customer Thank-You
An email comes in from Yuki Sato, who runs a history podcast and has been a customer for six weeks. She says, "This tool has genuinely changed how I work. I'm spending 6 hours on an episode now instead of 13. I'm telling everyone I know about this." She's not asking for anything. She's just saying it.
I respond to her directly. I tell her thank you, I ask what feature she uses most (it's the transcript-to-blog-post conversion, I learn), and I ask if she'd be willing to be a reference customer if others ask. She says yes. This is the work that doesn't show up on dashboards: the relationship building that turns a customer into an evangelist.
I add her to a "Happy Customers" list in a Slack channel. This is for me, for morale. On the days when the bugs feel endless and the churn emails come in, I'll read this list.
4:52 PM - Pipeline Reality Check
I look at the twelve people in trial. I send a personalized check-in to three of them who are on day 8 of their trial - old enough that they've tried the product, not so old that they've definitely left. Derek Kimball gets a note asking how his network is liking the batch transcription. Carol Reyes gets a question about whether the onboarding covered what she needed. Marco Chen gets a request for feedback, because his draft email was weak and I want to know if it was a fluke or if there's a real customer service issue.
These emails take maybe ten minutes total. But they're the difference between someone who comes back tomorrow and someone who just forgets about us.
6:08 PM - Close
I close the laptop. Today: three signups, one conversion, one customer churn, one bug fixed, two manual emails written, six agent-drafted emails reviewed. The Slack alerts are quiet. Lisa Tanaka hasn't responded to my email yet. Derek Kimball's account looks healthy.
I'm the entire operator right now. The agent does the detection work, the drafting, the flagging. I do the judgment, the empathy, the fixing, the deciding. It's not passive income. It's a job. But it's a job I own, and the pace is sustainable, and the product is actually helping people. In month one, I wasn't sure. In month two, I'm starting to believe this could work.
Tomorrow I'll do this again. Same rhythm, different details.