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 ve worked in two other eco-systems (India & France), and each has clear strengths and trade-offs in terms of talent density, cost of building, access to capital, speed of decision-making, and openness to risk all vary a lot.

Curious to hear from founders and operators who ve built outside the US:

• Which ecosystem punches the most above its weight today?

• Where do you see the best balance between talent, capital, and customer access?

• Are there cities/countries that are especially strong for specific stages (0 1 vs scaling) or specific verticals (AI, fintech, climate, SaaS, deep tech)?

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:

As users, we all want to try a product before committing. As builders, we want to show real value without over-engineering and investing time 'just for show'. Finding that balance is harder than it looks.

I just shipped my demo for Rewo (https://rewo.app), and intentionally went with a live, real demo:

• Fully functional product (same codebase as prod)

• Uses demo data instead of real integrations

• Some interfacing + sync pieces are disabled

• Auto-resets on a schedule so anyone can jump in fresh

Not really much, and it annoys me a bit. In exactly 14 days (28. 1.) we will launch the product, and the only thing I do is talk about it.

But yes, there are points that I still want to master by then, e.g.:

• Create an informational newsletter inviting people to follow our product page

• Create a list of people who could support us and ask them for help

• Announcements on social networks

• Inform Kickstarter backers who supported us with updates this is also an audience

• Publishing a Product Hunt badge on the landing page

• Continually grow and maintain a personal brand which should be a long-term goal, not just for launch purposes.

I keep going back and forth on this, so I m curious how others think about it.

At what point do you start taking non-English markets seriously?

• only after you feel solid PMF in English?

• when inbound users from certain regions show up?

• by picking one market early (Japan, LatAm, etc.) and committing?

• or do you just keep pushing it off to stay focused?

If your launch does not go as planned, do not judge it too quickly.
Avoid the instinct to immediately add more features or pivot the product.

Instead, pause and evaluate what already exists.
Check whether the core features are clearly communicated, fully polished, and genuinely solve the intended problem.
Often, the issue is not the idea, but the execution, positioning, or user experience.

Refine what you have. Improve clarity, usability, onboarding, and messaging.
Then relaunch with focus and confidence.

Many products fail not because they were wrong, but because they were unfinished, unclear, or rushed.

Let's play a bit of Nostradamus! What are your thoughts on 2026 changes in vibecoding tools capabilities, market dominance etc?
Here is mine:
From prompt app to ideate define plan build.
The winners won t start with a random prompt. They ll start with structure: clarity, scope, flows, acceptance criteria then build.
A whole services ecosystem will form around vibecoding.
Two obvious categories:
= Make it release-ready (engineers finishing the last 20%: architecture, edge cases, compliance etc)
= GTM for the masses (hundreds of thousands of apps shipped and most builders won t know what to do next)
Also: hackathons + internal workshops inside enterprises will become the new sexy way to learn AI. The best vibecoding companies will run these as growth loops.
Enterprise will enter heavily the chat.
Big players will optimize for ENT prototyping + internal tooling, where budgets exist and good enough fast is a real superpower.
Pricing will drop (or evolve).
A real reason people leave vibecoding tools for Cursor is simple: cost (even 20/month is a friction point at scale). Expect pricing to shift in favor of users and monetization to get more creative.
Influencer-educators will become distribution.
The value of an army of consultants/influencers who teach AI via workshops will compound. A strong professional ecosystem can 100 your reach.
Micro-SaaS stories will explode.
We ll hear hundreds of mom & pop businesses doing $1 5k/month not unicorns, but real freedom businesses from non-tech people.
Mobile becomes a priority for almost everyone.
The next wave won t stop at web prototypes. People will want real mobile products.
Niche wins again.
As broad tools saturate, builders will go specialized: video-only landing pages with AI type products or what I m personally obsessed with: native iOS apps and building modaal.dev
Meanwhile, AI companies will keep shifting upmarket to bigger deals and stickier customers.
Curious what you re seeing what would you add / disagree with?

On June 14, 2023, the European Parliament officially voted to ban unpaid internships.

This honestly made me happy, because I remember how, during college, I was expected to spend a full 2 months working full-time at an advertising agency as an unpaid intern (Spoiler alert: I fought for and got some pay ), but that wasn t the norm.

Yesterday was a big day for us, and we re still processing all of it.
TinyCommand finished as #2 Product of the Day, and for a small team that s been quietly building for months, it genuinely meant a lot.
We started TinyCommand because we kept seeing the same problem everywhere, people spending more time stitching tools together than actually doing their work.
Workflows breaking silently, data scattered across apps, forms living in one place and automation in another it never felt as simple as it should be.
That s the gap we wanted to close.
Seeing so many of you understand that instantly and even share the exact struggles you face made the launch feel meaningful beyond the ranking.
Thank you for the comments, the feedback, the upvotes, and the honest conversations throughout the day.
It helped more than you know.
There s a lot ahead for TinyCommand, and yesterday gave us even more clarity on what matters next.
#AllItTakesIsATinyCommand

I just upgraded my meme generator agent on @MindPal from Nano Banana to Nano Banana Pro and the results were INSANE

Crazy how these memes were generated WITHOUT any reference images.
What have you been using Nano Banana Pro for? Share your use cases below Let's see what its limits are.

I am curious how people actually do it.

There are tons of stories about founders launching SaaS products without an existing audience. No Twitter following, no newsletter, no community, nothing. Yet some still manage to get early traction and even hit real MRR.

If you have started from zero, I would love to hear:

• How you got your first users

• What channels brought the earliest traction

• Whether cold outreach works or not

• If content played a role or if you focused mainly on building

• What you would do differently if you had to start again

I ve been building full-stack applications for about 14 years mostly with Python, a few with Node, PHP, and Ruby.

Lately, my workflow has changed drastically.

With tools like Cursor, Claude Code, Codex, and Gemini CLI, generating reliable, production-ready code has become incredibly fast. These AI coding agents don t just accelerate development they often remove the friction entirely.

I keep hearing wildly different answers from teams at different stages. Some say a day. Others say two weeks because design, copy, approvals, and dev cycles stack up. I am trying to understand the real bottlenecks teams face when shipping something as simple as a landing page. Curious to hear how things actually work inside your team.

I've noticed that more and more founders are building their personal brand and prioritising it over building their company's brand (the company account then just reposts the founder's thoughts).

I notice this especially with solo founders.

Many brands have their long-standing mascots (McDonald's, Mr Clean, Michelin), etc. But with the development of AI, physical forms are moving online, and AI avatars look promising in this.

On one hand, it feels less human (authentic), on the other hand, AI influencers are a "cheaper" solution.

We ve always aimed to make data ridiculously easy to use. This release takes a massive step toward that goal. We ve built an entire data workflow that lets you connect your data, clean it, analyze it, and share it, all through a simple conversational interface. For me, that s the most exciting part. This is a true data platform workflow, built for everyone.

Let s break down what s new and why it matters so much.

Connect and Go: Your Data, Now in One Place

I'm doing research on which OS is worth making an educational app for, and jotted down some pros/cons for both iOS and Android.

Android:

It is known that there are more Android users, so you can potentially have a larger testing/user base.

Hi everyone, I m Bigyan, founder & CEO of The Drive AI.

Over the last few years, I ve noticed something strange we have AI that can write essays, code apps, and even generate videos but when it comes to files, we re still stuck in the past. We create them, rename them, move them, share them, and organize them manually one by one like it s 2005.

That s why we built The Drive AI the world s first agentic workspace, where your files can actually work for you. Instead of just storing them, our AI agents can:

Last week, OpenAI announced a full-year free subscription for Indian users starting November 4.
On top of that, they ve rolled out a Learning Accelerator program offering 5 lakh ChatGPT licenses to students and educators, and begun hiring engineers in Bengaluru.

So why the sudden focus?

Here s my take:

• India is now OpenAI s 2nd-largest user base, and probably the fastest-growing.

• By locking in early brand trust and language familiarity, OpenAI is essentially building a moat for the next billion users.

• The country has 700 million + internet users, but very low per-capita SaaS/AI spending. That s a huge conversion opportunity.

• Local competition is heating up as Perplexity, Gemini, and even smaller Indian startups are fighting for daily-use adoption.