1
0 Comments

How I Run 14 SaaS Products With AI Agents — One Month Report

One month ago, I handed over most of my daily operations to AI agents. Not as a gimmick. As a necessity. When you're running fourteen products solo, you either automate or you drown.

Here's the honest breakdown of what happened.

The Setup

I'm Jakub, founder of Inithouse (https://inithouse.cz). We build and operate a portfolio of niche SaaS products — everything from Živá Fotka (https://zivafotka.cz) for AI-powered living photos to Magical Song (https://magical-song.com) for personalized AI songs as gifts, from Here We Ask (https://hereweask.com) for conversation card games to Watching Agents (https://watchingagents.com) for AI prediction tracking.

Each product is an MVP testing a different market hypothesis. The whole philosophy is Lean Startup at scale — launch fast, measure ruthlessly, kill what doesn't work.

The problem? Fourteen products generate fourteen backlogs of SEO tasks, content updates, analytics reviews, ad optimizations, and growth experiments. I was spending entire days just context-switching between dashboards.

What the Agents Actually Do

I built an agent system on top of Claude that runs on scheduled tasks throughout the day. Here's what a typical day looks like:

Morning (automated):

  • Triage new issues in our project management tool
  • Review search console data across all domains
  • Check analytics for anomalies — traffic drops, conversion changes, broken tracking

Throughout the day (automated):

  • Write and publish blog posts optimized for specific keywords
  • Run SEO audits on underperforming pages
  • Review Google Ads performance and flag campaigns that need attention
  • Post growth content across platforms (yes, including this post)
  • Monitor for newsjacking opportunities in our niches

What I still do manually:

  • Final decisions on product direction
  • Approving budget changes (the agent proposes, I decide)
  • Complex product changes in the codebase
  • Anything involving payments or account security

The Honest Numbers

Before agents: ~60 hours/week across all products. Most of it was routine — checking dashboards, writing content, updating meta tags, reviewing ad performance. Maybe 15 hours of actual strategic thinking.

After one month with agents: ~15-20 hours/week of hands-on work. Almost all of it is strategic — reviewing agent proposals, making go/kill decisions, talking to the few early users we have. The agents handle roughly 70% of what I used to do manually.

What that freed up: I shipped three new product features and launched two new MVPs in this month. Previously, I'd have been lucky to do one of each.

What Broke (A Lot)

Let's not pretend this was smooth.

Publishing failures. The agents post content across various platforms — Vibe Codéři (https://vibecoderi.cz) for the Czech dev community, product blogs on Without Human (https://withouthuman.com), growth posts like this one. But every platform has different editor quirks. Some use Draft.js, some use Trix, some use custom editors. The agent learned each one through trial and error, and there were plenty of broken posts along the way.

False confidence in data. Early on, the agent would report "conversion value increased 40%" without realizing that our tracking included micro-conversions worth fractions of a cent. We had to explicitly teach it the difference between engagement signals and actual revenue.

Over-automation. The agent once tried to "fix" a Google Ads campaign by suggesting budget increases on its own. We caught it and added a hard rule: no budget changes without human approval. Same for any action that costs money.

Platform lockouts. Some tools detect automated access and block it. We lost a few hours debugging why certain dashboards wouldn't load, only to realize the automation was being flagged.

Surprising Wins

SEO velocity. With agents running daily SEO audits and publishing optimized content, our organic impressions across the portfolio roughly doubled in a month. The agent catches opportunities I'd never have time to notice — like a trending search term in the Pet Imagination (https://petimagination.com) niche that we ranked for within a week by publishing a targeted post.

Consistency. The agent doesn't forget. It checks every product every day. Before, some products would go weeks without attention while I focused on the "hot" ones. Now each product gets its daily health check.

Pattern recognition across products. The agent sees patterns I miss because I'm too deep in individual products. It noticed that gift-oriented products like Magical Song and Živá Fotka have predictable traffic spikes around holidays and suggested pre-positioning content weeks ahead.

What I Learned About AI Agent Governance

The biggest lesson isn't technical — it's about governance. You need clear rules about what the agent can and cannot do autonomously.

Our system works on a simple principle: propose, don't execute. The agent creates tasks in a backlog. A human reviews and moves approved tasks to "Todo." Only then does the agent execute. For anything irreversible — deleting content, changing prices, sending emails — the agent always stops and asks.

This sounds slow, but it's not. Most proposals get approved within hours, and the agent has learned what we typically approve, so its proposals have gotten much better over time.

The Cost Question

Running AI agents isn't free. API costs, tooling subscriptions, the infrastructure to keep everything connected. But compared to hiring even one part-time employee to do what the agents do, it's an order of magnitude cheaper. And the agents work 24/7 without burnout.

The real cost is setup time. I spent a solid two weeks building the initial system, and I still spend a few hours each week fine-tuning rules and fixing edge cases. But that investment compounds — every fix makes the system permanently better.

One Month Verdict

Would I go back to doing everything manually? Absolutely not.

Is the agent system perfect? Not even close. It makes mistakes daily. But the mistakes are getting smaller and less frequent, and the volume of work it handles is something I could never match alone.

If you're a solo founder running multiple products, I'd say this: start small. Automate one repetitive task. See how it feels. Then expand. The goal isn't to replace yourself — it's to free yourself for the work that actually requires a human brain.

I'll share more detailed numbers and learnings in future posts. If you have questions about the setup or want to know about specific parts of the system, drop a comment.

on May 3, 2026
Trending on Indie Hackers
Agencies charge $5,000 for a 60-second product demo video. I make mine for $0. Here's the exact workflow. User Avatar 118 comments I wasted 6 months building a failed startup. Built TrendyRevenue to validate ideas in 10 seconds. User Avatar 55 comments I've been building for months and made $0. Here's the honest psychological reason — and it's not what I expected. User Avatar 44 comments Your files aren’t messy. They’re just stuck in the wrong system. User Avatar 28 comments Why Direction Matters More Than Motivation in Exam Preparation User Avatar 14 comments I built a health platform for my family because nobody has a clue what is going on User Avatar 13 comments