Hi Product Hunt community, I m Artin, founder of SUN.

Ask me anything about how we got into a16z Speedrun, the product, fundraising, team building, or our Product Hunt launch.

Happy to chat and share what s worked (and what didn t).

I did it. I one-shotted a Lovable app - and not a simple one.

I built a branded, Netflix-style hub of AI tools for my audience. Think: a website where people land, browse a library of AI agents and workflows trained on my expertise, sign up, fill in their profile, and start using the tools - with every tool knowing who they are and personalizing its responses based on their profile. The hub handles auth, onboarding, usage tracking via webhooks, a paywall that kicks in after a free tier, full run history with resume, dark mode, and an admin dashboard. 9 pages total.

@MindPal builds the AI agents and workflows trained on your knowledge.

@Lovable builds the interface from one generated prompt.

Curious where the line is for people here:

If you had to delegate just one real task today, what would you trust an AI developer with first?

Bug fix, refactor, tests, docs, or a small feature?

Launched Lokuma Design Agent today.

Now I want to ask something more practical:

what s a design skill you wish your AI tool had, but still doesn t?

Last month, I did something that felt slightly insane.

I took our product description, fed it into ChatGPT, and asked it to build a competitor. Not a parody. A real competitor. Better features, better positioning, better everything. I told it to be ruthless.

It did!

The output was polished. Confident. Structured like a real go-to-market plan. It named features we don t have. It positioned itself against us. It looked like a threat on paper.

Curious how builders here think about this:
Would you trust an AI developer to work on a real production codebase today? Not just autocomplete or code suggestions, I mean actually taking a scoped task and shipping code updates.
What would make you comfortable trying that, and what would be the biggest red flag for you?

If you re still sitting on your launch, this is the push.

YC made a special exception for this community: one or more companies that launch tomorrow will get a YC interview and potentially funding. A YC partner will review every eligible launch.

We've been building Naoma for over a year. Pivoted from a sales analytics platform, rewrote the product from scratch, ran pilots, iterated, broke things, fixed them.

Tomorrow we launch on Product Hunt.

The idea is simple: B2B buyers shouldn't have to wait 5 days to see your product. Naoma runs a live AI demo the moment they click qualifies them, walks through the product, routes the right leads to sales or checkout. No scheduling. No waiting.

If you're a product owner, founder, or builder reading this, I want to talk about something that's costing you money right now.

You probably don't know it's happening.

Here's what I've learned after analyzing 500+ SaaS products, tools, and digital products at Rankfender.

The Mistake

Let me start from the creator s perspective:
I personally don t have a product (apart from hiring people for creative work or offering personal consultations).

But as a creator, I constantly share content, insights, and information, value that helps me build trust (for free). Based on that perceived expertise, people eventually decide to work with me (a paid service).

I've been a professional developer for 10+ years (WordPress ecosystem, and React, TypeScript, Node, the whole stack).

Now I'm building my own SaaS and I'm genuinely torn.

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.

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:

AI dev tools are evolving crazy fast , every few weeks there s a new must-try for vibe coders.

Some people are building full products with @ChatGPT by OpenAI and @Replit , others swear by @Cursor and @Claude by Anthropic , and a few are mixing @Lovable + @v0 by Vercel + @bolt.new to ship apps in record time.

I ve been refining my own vibe stack lately, trying to find that sweet spot between speed, control, and creativity.
It made me wonder ,what does your setup look like right now?