Kashyap Rathod

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?

Hi folks,

I ve been spending a lot of time on Discord and Reddit helping people who are trying to add AI chat to their no/low-code apps.

What keeps coming up is that the setup is way more fragile than it looks.

It s usually not the model itself it s everything around it:
conversation state, memory, retries, edge cases.
Vibe-coding works for demos, but once people try to ship something real, things start breaking.