First of all, I want to thank you for voting for us in yesterday's launch - you still can, the week is not over. HERE

Second thing, I summarised some things that I realised, reflected on, and maybe should have known sooner:

Hey everyone,

I've built my product around traditional SaaS pricing (monthly tiers), but I m starting to wonder if that model is getting outdated, especially with more AI-powered and compute-heavy tools entering the market.
That shift requires real architectural changes, instrumentation, metering, billing logic, and UI changes, not just pricing tweaks. It s something I m starting to seriously think about for my own product.

In particular, AI usage has real COGs (every prompt costs money), and I m seeing more platforms experimenting with usage-based models, or hybrids like SaaS base + usage + overage.

For those of you building AI or compute-intensive tools:

New AI models pop up every week. Some developer tools like @Cursor, @Zed, and @Kilo Code let you choose between different models, while more opinionated products like @Amp and @Tonkotsu default to 1 model.

Curious what the community recommends for coding tasks? Any preferences?

We re officially in nominees season for the Orbit Awards: AI Workflow Automation.

Since I haven't been able to meet my work goals very well in the last few quarters, I now plan to approach them more systematically and not push myself too hard on work goals, as that ultimately led to problems that made my plan less sustainable.

So here is my structure and list: