How to Manage a Portfolio of Indie Apps Without Losing Your Mind
Four Stripe dashboards open in different tabs. Three Linear workspaces. Revenue coming in across two currencies. A Notion doc full of goals that hasn't been opened in weeks. Money is coming in, but how much? And is any individual project actually profitable once you subtract hosting, domains, and the seventeen SaaS tools each one depends on?
If you're running multiple side projects, this probably sounds familiar.
The indie hacker community has broadly accepted that the portfolio approach works. Instead of going all-in on one idea and praying it hits, you run two, three, maybe five small bets simultaneously. Some will fail. Some will plateau at a few hundred dollars a month. Occasionally one takes off. The economics of this are sound. You get diversification, so a bad month for one project doesn't tank your income. You get cross-pollination, where an idea from project A solves a problem in project B. And you get emotional resilience, because when one project stalls and you're losing motivation, you can switch to something that's actually moving.
What nobody talks about enough is the operational chaos this creates.
The mess nobody warns you about
When you're running a single project, you can keep most of it in your head. Revenue is one number. Your roadmap is one list. Your error monitoring is one dashboard. Scale that to four projects and suddenly you're context-switching between completely separate universes, each with their own metrics, their own bugs, their own users asking for things.
It's easy to spend the first hour of every day just figuring out where things stand. Checking Stripe for each project. Scanning Sentry for errors. Opening Linear to see what you left half-finished on Friday. By the time you actually start building, you've burned through your best focus hours on administrative overhead.
Spreadsheets help for a while. A Google Sheet pulling revenue from Stripe, a separate one for expenses, a third one for goals. It works right up until it doesn't. The formulas get fragile. Currency conversions are always slightly wrong. And nobody ever opens the goals sheet after January.
The core problem with managing multiple SaaS projects isn't any individual task. It's that there's no single view of "how am I actually doing across everything?" You end up with information scattered across a dozen tools, and the mental overhead of synthesising it all is genuinely exhausting.
Revenue tracking is the foundation
If you're going to get one thing right, make it revenue. Specifically, MRR. Monthly recurring revenue is the heartbeat of any SaaS project, and when you're running a portfolio, you need to see it aggregated across everything.
This sounds simple until you try it. If you're selling in dollars and euros, you need currency conversion that actually updates. If you're using Stripe (and you probably are), you need to decide whether you're syncing automatically or entering numbers manually. Automatic sync is obviously better, but most tools that offer it only handle one Stripe account, and plenty of us have separate accounts for separate projects.
The number that matters most isn't revenue though. It's profit. It's surprisingly common to run a project for months thinking it's doing well because MRR is growing, only to sit down and realise the costs eat almost all of it. Between Vercel, a managed database, third-party APIs, and the domain, a project can barely break even. When you track revenue across projects without tracking expenses alongside it, you're flying blind.
What you actually want is a monthly P&L across your whole portfolio. Not just "Project A made £400 this month," but "Project A made £400, cost £120 to run, and netted £280." Then you want to see that next to Project B and Project C and get a real picture of your indie hacker portfolio as a business, not as a collection of side projects.
Goals that actually mean something
Most goal-setting systems fail for solo founders because they're designed for teams. OKRs, quarterly themes, annual targets — they assume you need alignment across departments. You don't. You need to know whether you're on track.
What works better is portfolio-level targets with per-project milestones feeding into them. So instead of "Project A should hit £1k MRR," you set "total portfolio MRR should hit £3k by June," and then each project has its own contribution target. This matters because it changes how you allocate time. If Project A is ahead of schedule and Project C is behind, you know where to focus without agonising about it.
The other thing that matters is tracking progress automatically where possible. If your MRR goal is £3k and your dashboard already knows your current MRR, it should just tell you where you stand. Manual progress updates are a tax on your attention, and you'll stop doing them within a month.
Planning without drowning
Roadmaps across multiple projects are where things get properly chaotic. You've got feature ideas, bug reports, user requests, and your own grand plans, all competing for the same limited resource: your time.
A simple framework that works well: everything goes into one of three buckets: NOW, NEXT, and LATER. NOW is what you're working on this week. NEXT is what you'll probably pick up in the next couple of weeks. LATER is the parking lot for good ideas that aren't urgent. The key is that this spans all your projects. Not four separate backlogs. One prioritised list of work across your entire portfolio.
This also solves the "losing great ideas" problem. When you're deep in Project B and you have a flash of inspiration for Project A, you need somewhere to capture it that you'll actually see again. If it goes into a separate tool, it's dead. If it goes into a unified view alongside everything else you're working on, it has a chance.
The weekly review
The single most impactful habit for portfolio founders is the weekly check-in. Every Sunday evening, twenty minutes reviewing each project. How's revenue trending? Any errors that haven't been dealt with? What shipped this week? What's the plan for next week?
It's also worth tracking how you're feeling about each project, which sounds soft but is genuinely useful. Three weeks of dreading working on something is a signal. Maybe the project needs to be wound down, or maybe it needs a different approach. Metrics alone don't capture this. A project can be growing while making you miserable, and that's important to catch early.
The weekly review is also where problems get caught before they become crises. A slow decline in MRR is easy to miss when you're looking at daily numbers. But when you see three weeks of slightly-down revenue in a row, you know something's off and you can investigate before it gets worse.
Knowing where things are heading
Forecasting feels like a luxury when you're a solo founder, but it's actually one of the most grounding things you can do. If you know your current MRR, your growth rate, and your churn, you can project where you'll be in three, six, twelve months. It's not going to be exact. But it transforms your relationship with your business from "hope things keep growing" to "at this rate, the target lands in four months, or something needs to change."
Multi-project forecasting is even more interesting because you can see which projects are driving growth and which are plateauing. That directly informs where you spend your time, and when it might be right to sunset something that's flatlined and start a new bet.
What we built to fix this
This exact problem is why we built Shipchart — a SaaS portfolio management dashboard designed specifically for indie hackers and solo founders running multiple projects.
It does the things described above: unified MRR tracking for indie hackers across all your projects, multi-currency revenue with Stripe sync, expense tracking so you see actual profit, portfolio-wide goals with auto-progress, roadmaps that span projects with NOW/NEXT/LATER planning, weekly check-ins with mood tracking alongside metrics, and revenue forecasting based on your real growth data.
It also connects to the tools you're already using. Linear for issue tracking, GitHub for code, Sentry for errors. The idea is that instead of opening six tabs every morning, you open one indie dev dashboard and know exactly where everything stands.
There's a free tier, so you can try it without committing anything. We built it because we needed it, and it turns out a lot of other people running multiple side projects needed it too.
The actual point
SaaS portfolio management isn't about adding another tool to your stack. It's about reducing the cognitive overhead of running multiple projects so you can spend more time building and less time just figuring out what's going on.
The portfolio approach to indie hacking is powerful. Running multiple small bets is one of the smartest strategies available to solo founders right now. But it only works if you can actually manage the complexity. Otherwise you end up spread thin, context-switching constantly, and slowly burning out while your revenue sits in four different dashboards that you check less and less often.
Get your tracking right. Review regularly. Know your actual numbers, not just your revenue but your profit. Set goals at the portfolio level. And build the habit of stepping back every week to look at the whole picture.
Your future self, the one who isn't frantically tab-switching between Stripe accounts at 11pm, will thank you.