If you use AI dev tools daily, you ve probably felt this:

You start a new session and immediately have to re-explain:

• what the project is

• what you already tried

• why certain decisions exist

• what not to repeat

Not because the AI is bad.
Because the workflow forgets.

Hi all, Dan here. I'm developing my home improvement computer vision website as a side project in my spare time. I love the idea of monetising it, but in all honesty it is a brilliant hobby. It is a great break from work and feel energised every time I push an improvement live!

Using @Claude Code and astounded by it's capabilities. I'm a Head of Data for a UK hospitality chain and keen to chat about all things, AI, data and more.

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?