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

With the advent of clawdbots, it's as if we've all lost our inhibitions and "put our lives completely in their hands."

I'm all for delegating work, but not giving them too much personal/sensitive stuff to handle.

This post is actually inspired by a tweet from @sandradjajic + an update here on PH from @chrismessina.

A few days ago I saw this:

As usual, Y Combinator came up with segments that are worth investing:

1. Cursor for Product Managers
2. AI-Native Hedge Funds
3. AI-Native Agencies
4. Stablecoin Financial Services
5. AI for Government
6. Modern Metal Mills
7. AI Guidance for Physical Work 8. Large Spatial Models 9. Infra for Government Fraud Hunters 10. Make LLMs Easy to Train

After our first launch on Product Hunt, our team spent a little over a month upgrading the product. There were major changes to the UI and several new features added, so the process took time from discussions and redesigning the interface to testing, fixing bugs, and updating AI prompts.

We re also a very small team, so everyone had to push themselves to give 200%. Time and resources are limited, and at the same time, we also had to work on securing funding for the next six months to keep the team running and continue developing the app.

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:

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?

Hey PH

We're launching Rover on Feb 25th, but the preview is live right now and we want your honest takes before we go big.

What it is: One script tag on your website your users get an AI agent that takes real actions inside your UI. Clicks buttons, fills forms, runs checkout, guides onboarding. Through conversation.

<script src="https://rover.rtrvr.ai/embed.js"></script>

All,

I've been quiet, and I won't apologise for this, It's because I've been making Clarity better than ever.

Today I read in TechCrunch that Airbnb says a third of its customer support in the US and Canada is now handled by AI.

Many CRM-focused platforms are following suit, automating support with their own AI bots for example, Crisp, Chatbase, and others.

Hey there creative ad people. We're working non-stop to make marketfunkers the best as it can be, and feedback is very valuable.
So if you're into performance marketing/paid social/copywriting - give the platform a test and let me know what you think.
- Gligor

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:

This is rooted in psychology.

When you show that there is enormous interest in something, a crowd of people will flock and want to see it.

I woke up this morning, and X was full of this message:

Today I received a question about proper launch preparation:

Nika, how long should this take us?

And I didn t have a clear answer.

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:

Yesterday, I came across a post saying that OpenAI projects a $14 billion loss in 2026. They ve gone through several funding rounds, offer monthly subscriptions, and are now planning to integrate ads into search results (which means another revenue stream).

Realistically, I don t think this loss will be covered in the short term, and profitability might only come over a longer horizon (if at all).

As a measure of the impact of vibe coding and the need to focus on positioning, narrative, and marketing and distribution, I noticed that that 610 products were submitted to the Product Hunt leaderboard today, but only 16 were featured which is less than 3%.

The previous high was just over 500 products in December.

We've objectively tested Safari, Chrome, Firefox, and Edge to determine which offers the best:

Speed,

Standards Compliance,

This is something I ll find out in just a short while, one week from now (Jan 28), as I m about to re-launch a digital detox app. If you want, follow, maybe you will be on watch of my steps and activities

However, that s not the main point of this post.

I used to think the hardest part of building a product was building the product.

Turns out, creating superfans is harder.

The real challenge is getting people to love your product:

It took longer than it should have, mostly because it kept getting deprioritized in quarterly planning. And the annoying part is: the longer you wait on dark mode, the bigger it gets. More components to adjust, more edge cases, more workflows to test.

So we stopped debating it. No justification, no comparisons. We just shipped it.

After launching Sway on Product Hunt, we read every single comment.

Some of you were excited. Some curious. Some skeptical. That was good.
Because Sway is built for reflective thinking and that starts with us.

Here s what we changed based on your feedback:

Our team is planning to launch a new version of our product on Product Hunt next week, after a period of optimization and improvements. As we get closer to launch day, I realize there s a lot to prepare, and I m curious about how other teams usually approach this process.

So far, here s what we ve been focusing on:

• Most importantly, making sure the product works well and delivers real value

• Continuous testing to ensure performance and stability

• Designing clean and clear product screenshots

• Preparing a summary of what s been updated, fixed, or optimized

• Writing launch content (tagline, description, first comment, etc.)

• Maintaining good health and a stable mindset for the launch

• Expanding our network and connecting with other makers

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.

We are currently improving the integration and features of the mobile application.

I would like to know which functionalities you have always expected the app to have to make it easier to manage your OpenClaw assistant.