I run 14 products. This is the tool I wanted for them.

My apps and sites span iOS, Mac and the web. For years my Monday routine was Stripe, RevenueCat and Google Analytics open in separate tabs, one product at a time, and a spreadsheet to add up ad spend and hosting. I still ended up working on whichever product was loudest, not the one that paid.

Plask puts those sources side by side for every product, subtracts the costs you enter, and on Pro gives you up to three Focus cards a week on what needs you. My own portfolio is its first user, so every rule runs on my real numbers first.

Who builds Plask?

I have spent more than 15 years building Android and iOS apps, plus the backends and infrastructure behind them, and I lead an engineering team by day. My own products are small apps and sites for iOS, Mac and the web, each with its own revenue and costs.

• March 2026. Plask starts as a Google Analytics dashboard with traffic alerts for my own apps.
• October 2026. Version 2 turns it into a P&L per product: revenue from Stripe, RevenueCat and the app stores, costs subtracted, weekly Focus cards, an opt-in public board and an MCP server.

How I build it

• Read-only access. A restricted Stripe key, a RevenueCat secret key, and read-only Google Analytics. Plask cannot change anything in those accounts. Keys and tokens are encrypted at rest with AES-256-GCM.
• Aggregates, not people. It stores daily totals per product, not your customers' names, emails, cards, or individual visitors.
• The numbers are computed, not generated. The arithmetic and the rules are plain code. A language model only writes the one-line explanation on a Focus card, from numbers that are already worked out.
• Plain pricing. Free for one product, Pro when you have two. No sales calls, no seats.

Elsewhere

The other products are listed on tskulbru.dev/portfolio. I write about building software on tskulbru.dev, and I'm on LinkedIn and GitHub. You can reach me at [email protected], or see the contact page.