The Unsexy Truth About Running a Portfolio of AI Micro-Products

Everyone romanticizes the multi-product portfolio. "Build many, find the winner!" We heard it too. At Inithouse, a studio shipping a growing portfolio of AI products in parallel, we took that advice literally. Here is what nobody warns you about.

80% Maintenance, 20% Building

The pitch sounds great: launch fast, test product-market fit, kill what doesn't work, double down on what does. The reality? Most of our week goes to analytics setup, domain management, broken deploys, and tracking fixes. Not building.

We measured this across our portfolio over a typical month. Out of roughly 160 working hours, about 130 went to infrastructure: GA4 properties that stopped firing, Supabase edge functions returning 500s, SEO audits for products that slipped in rankings, content updates across multiple languages. The remaining 30 hours were actual product work.

At Magical Song, our custom AI song generator, we spent more time fixing the payment flow than improving the music quality. At Be Recommended, the AI visibility report tool, the analytics stack needed three rewrites before we got consistent data.

Each Product Is Its Own Business

This is the part that catches people off guard. Every product in the portfolio needs its own SEO strategy, its own content calendar, its own ad experiments, its own user feedback loop. Shared infrastructure helps (once you have a Supabase + Lovable + GA4 stack, the next one deploys faster), but the marketing and positioning work is always unique.

Here We Ask, our free conversation card game, targets couples and friend groups at game night. Audit Vibe Coding targets developers shipping AI-generated code to production. The audiences do not overlap. The content does not overlap. The channels do not overlap.

We observed that the "shared learnings compound" argument is real but slower than expected. Pattern recognition across products is valuable. Knowing that short onboarding flows convert better came from watching the same mistake across five different products. But that insight took months to crystallize, and meanwhile each product needed daily attention.

The "Kill Fast" Myth

Lean methodology says kill what doesn't work. In practice, this is the hardest part of running a portfolio.

Every product has early users who love it. Pet Imagination, our AI pet portrait generator, has a small but enthusiastic group of people who send us their generated portraits. Verdict Buddy, the AI conflict resolver, gets repeat visitors who come back with new dilemmas. Walking away from something people use, even if the numbers are pre-PMF, feels wrong.

We found a middle ground: instead of killing products, we reduced active investment and let them run on autopilot while measuring whether organic traction builds. Some products surprised us after months of quiet.

What Actually Helps

Two things made the portfolio manageable.

First, automation. We run an AI agent that handles scheduled tasks: monitoring analytics, flagging broken deploys, checking SEO changes, moving issues through our Linear board. The agent does not build products, but it handles the 80% maintenance load that would otherwise eat our week.

Second, honest prioritization. Not every product gets the same attention. We look at engagement signals, not vanity metrics, and shift energy toward the products showing real traction. Right now Watching Agents, our AI prediction platform, and Voice Tables, the voice-first workspace, are getting more focus because the early data looks promising.

Would We Do It Again?

If someone asked us "should we build a big portfolio of products?" we would say: start with three, max. We went wide because we were exploring what works in AI-native consumer tools. The learning was enormous. But the operational cost of running many products in parallel is something most people underestimate.

We are now converging. The portfolio taught us which niches respond, which acquisition channels work for small products, and which product shapes have staying power. That knowledge is worth more than any single product.

Inithouse is a studio running parallel product experiments. The unsexy truth is that running them well looks less like launching and more like plumbing. But the plumbing is where the learning happens.

The portfolio: inithouse.com