Who's Inithouse for? Builders who ship 16 products instead of perfecting one.

Everyone tells you to focus. Pick one idea, go deep, iterate until it works.

I tried that. Spent 8 months on a single product back in 2024. Built it carefully, polished the UI, wrote the docs. It didn't find PMF. All that time, gone.

So I tried the opposite. What if I treated early-stage products like a portfolio? Instead of betting everything on one idea, I'd run a bunch of small experiments in parallel. Ship fast, measure what sticks, kill what doesn't.

That's Inithouse. Right now we're running 16 live MVPs across AI tools, consumer apps, and niche SaaS.

How it actually works

Every product starts as an MVP built in 2-3 days. I use Lovable for the frontend and Supabase for the backend. Same stack across all 16 products, which means I'm not learning a new framework every time. Auth patterns, database schemas, deployment scripts: all shared.

The portfolio covers a pretty wide range. Audit Vibe Coding runs automated code quality checks on AI-generated apps. Be Recommended tracks how well your brand shows up in AI assistants like ChatGPT and Perplexity. Then there's party games, a pet portrait generator, a personalized song maker, tarot readings. Different markets, different audiences, same underlying infrastructure.

Some are growing. Some are flat. Two got killed already. That's the point.

The math behind it

If each MVP has a 10% chance of finding real traction, running 16 gives you about an 81% chance that at least one hits. Running just one gives you 10%.

VC funds diversify across 30+ companies for exactly this reason. Seed investors don't pick one startup and pray. They build a portfolio and let the winners emerge.

I'm applying the same logic as a builder instead of an investor.

What I didn't expect

The biggest surprise was how much shared infrastructure saves. When I build a better onboarding flow for one product, the pattern transfers. Same for analytics dashboards, email templates, SEO setups. The 16th product took maybe 30% of the effort the 3rd one took.

The hardest part is context-switching. Sixteen products means sixteen different user bases and growth channels. I've had to automate a lot of the monitoring and reporting just to stay on top of it.

And some products I shipped too early. Launched before the landing page even explained what the thing does. That's a real cost of moving fast: sometimes you skip the basics and have to circle back.

Who this isn't for

If you're building the next Notion or Figma, this approach is wrong. Products like those need years of deep focus.

Inithouse is for a different kind of builder. The kind who'd rather test 10 ideas this year than spend the year perfecting one. Who treats failed experiments as data, not failures.

If that sounds like you, the whole portfolio is public at inithouse.com. What's growing, what's flat, what we dropped. All of it.