Two years ago, Lovon was made for couples who were already in a relationship.

We offered packs of psychology-based questions, quizzes, and mini-games. They helped partners talk about hard topics like trust, jealousy, and intimacy.

Six months ago, I was stuck in a relationship that looked good on paper.

My partner was loving and kind but my feelings were gone.

I didn t want to hurt her.
But staying was hurting me.

AI is everywhere right now - from copilots and chat assistants to analytics, research, and planning tools. But beyond the hype, I m curious about what s truly useful in day-to-day product work.

From a PM or founder perspective:

• Where has AI genuinely saved you time?

• What tasks do you trust AI with - and what do you never delegate?

• Has AI changed how you write specs, manage roadmaps, or talk to users?

• What AI use cases sounded great in theory but failed in practice?

Personally, I see a lot of potential, but also a lot of noise. I believe that in the future, AI should help us much more. Create good roadmaps, convert product specs into concrete tasks, prioritise them, assign people, push for realisation, and much more.

We re usually very good at creating to-do lists for work.
But what about everything outside of work?

I ve started turning my personal habits into a checklist to build discipline and make these habits non-negotiable over time.

Here s mine:

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.