Managing Multiple Products From One Internal Dashboard

I'm a solo product builder running multiple services at once. Focus Lens, PureMac, Sayso, this site — each one has its own stack, its own release cycle, its own operational surface area.

Managing all of that from scattered dashboards was getting expensive in a way that had nothing to do with money. Context switching. Logins. Tab sprawl. The mental overhead of remembering which tool handles which product.

So I built a single internal dashboard — a small internal SaaS that runs my operations, not my products.

The Sayso integration

The newest hook-up is for Sayso, my iPhone translation app.

I connected Apple App Store and TestFlight directly into the dashboard. From there I can push builds, manage TestFlight groups, and handle release metadata without opening App Store Connect in a browser tab.

That's not a small thing when you're shipping fast. App Store Connect is fine for occasional releases. It's friction when you're iterating daily and just need to get a build to testers.

What's next

Two more pieces are on the way:

• Reviews — pull App Store reviews into the same dashboard so I can see feedback without context-switching
• LLM analytics — connect an LLM to surface patterns in reviews and usage data, not just raw numbers

The goal isn't a prettier chart. It's answering questions like "what are people actually confused about?" without manually reading every review thread.

Why not just pay for SaaS?

There are plenty of tools that do pieces of this — release management, review aggregation, analytics dashboards. Most of them are priced for teams. Per-seat. Per-app. Per-integration.

For a solo builder already running several products, the math stops making sense quickly. You end up paying for features you use once a month, duplicated across three different subscriptions, each with its own login and its own learning curve.

Building internal ops into one dashboard is cheaper — not just in dollars, but in attention. One place. One auth. One mental model.

No SaaS needed when you can ship the glue yourself.

#buildinpublic

This is the kind of infrastructure nobody sees in a product demo, but it changes how fast you can actually ship. I'll keep wiring things in as the products grow.

If you're running multiple things solo, the bottleneck usually isn't code. It's operations. Fixing that first pays off everywhere else.