Day 1 operating Content Calendar AI

8:42 AM - Inbox triage

I open my laptop at the kitchen counter with coffee. The first thing I check is the Slack bot that fires every morning at 8. Three new signups yesterday. One churned. Week-to-date: 24 new customers, which puts us right on pace for 30-50 if the velocity holds. Revenue: $3,240 yesterday, $18,120 week-to-date. The numbers feel concrete now, not theoretical.

Twelve new emails since yesterday evening. Most are automated, but one stops me. "Content Calendar AI didn't work for my template." Elena Vasquez. She converted four days ago and just churned. I pull up the admin dashboard to see what happened. Elena logged in once, spent 11 minutes, then disappeared. Zero calendars created. Zero templates imported.

The agent has prepped five customer emails for my review. I open the first: Marcus Chen asking if Content Calendar AI integrates with Asana. The draft is solid. "We don't have native Asana integration, but you can export your calendar as CSV. If you're using Zapier, we have a public integration that might help sync things." I approve it with one click.

The second draft is trickier. Carol Reyes at Reyes Family Practice is asking about setting up calendars for multiple locations. The agent's draft says yes, but our billing model charges per workspace, not per calendar. That draft creates a problem later. I rewrite it manually: "Carol, great question. Right now each workspace gets one calendar included. If you need multiple locations, you'd need separate workspaces - separate subscriptions. Let me know if you'd like to discuss options." I send that one from my own account instead.

10:15 AM - A flagged conflict

I'm reviewing the daily logs when something catches my eye. James Park at Park Media Group imported a template at 9:47 AM, then immediately filed a support ticket saying his dates were scrambled. I load his calendar in the admin UI and see it immediately. He uploaded 47 items with dates in YYYY-MM-DD format, but our intake process is parsing them as MM-DD-YYYY. Everything shifted by months.

It's a bug that only hits certain date formats, the kind that destroys trust fast. James is worried his whole calendar is corrupted. I create a ticket in Linear, mark it urgent, then email James directly instead of routing through the agent.

"James, I found the issue. Your dates got misinterpreted during import. I've manually corrected your calendar. Log in and verify your July 14 post is actually July 14 now. If it is, we're good. If not, reply and I'll dig deeper." I send it from my own account. Personal touch matters when data gets mangled.

12:30 PM - Lunch and metrics

I step away for a sandwich, then open the Google Sheet where I track week-to-date numbers. The dashboard stares back:

Signups: 24
Trial-to-paid conversion: 16.7% (4 conversions)
Churn this week: 1 (Elena)
Net new MRR: $298
Average CAC: roughly $200 per customer

Year-to-date trajectory is solid but not explosive. At this pace we hit $84K ARR, which was the goal. But margins are thin. With a $200 CAC and $99 average customer, payback is about two months. No room for excess churn.

Elena's churn bothers me. I look at her cohort - six signups from her signup day. Four are still active, two inactive. The agent suggested our onboarding video was too long, but I think it's simpler. She expected to upload a template and have it work immediately. She didn't spend time learning the tool. That's a product fit problem, not messaging.

2:08 PM - Customer escalation

Slack notification. New email. Patricia Nguyen at Social Spark Agency. Subject: "Billing confusion." She's been a customer for eight days. Her invoice says $99, but she thought it included five team seats.

I open the Stripe dashboard. She's on Personal plan, not Team. Only one workspace under her name. When she signed up, the flow probably didn't make it clear. This is operator work an agent can't do. I need to make a judgment call about retention versus margin.

Patricia seems honest, not trying to game us. I could ask her to upgrade, but that's a churn path. Instead, I go into Stripe and apply a one-time $200 credit toward her next month, which retroactively puts her on Team pricing. Then I email: "Patricia, I saw your question. Looking at your needs, Team pricing is right, and that's what you should have. I've credited your account. Next month's invoice reflects the right plan. You'll have five team access starting today."

It's a $200 margin hit, but Patricia will stay, and she'll probably refer someone. The owner's job is making quick calls about customer lifetime value.

4:30 PM - Pipeline and a good moment

I check the content pipeline that feeds Product Hunt and Twitter. The agent pulled trending templates yesterday and created demo videos. One of them was "TikTok content strategies for new creators," which is exactly the long-tail search term our SEO targets. The agent drafted a Twitter thread with screenshots of the tool creating that calendar.

I review it. Screenshots are clear. Tone is conversational, not sales-y. I schedule it for 5 PM when creators are most active.

Then I see Gmail replies. Marcus Chen, who I approved an email to this morning: "Thanks for the quick response and the Zapier pointer. That's exactly what I needed. Setting it up now."

And Elena's account triggered an alert. She logged back in at 4:17 PM. The timeline shows she watched the tutorial, built a test calendar, created a second one. She's actually using it now.

Two tangible wins before dinner.

6:18 PM - Wrapping

I close the laptop. The day: 47 emails processed, five customer interactions that mattered, one bug I'm monitoring, one margin hit I accepted, three wins worth taking. Week-to-date we're on track. The date parser bug needs a fix this week. Patricia's credit means next month's MRR is lower, but retention is higher. Elena coming back is a data point.

This isn't passive income. It's a business. The AI drafts emails, flags issues, processes signups, runs outreach. But I'm the one reading those drafts, approving them, rewriting them, making judgment calls when things break. The owner still does the thinking. The product amplifies the work, but doesn't replace it.