Connect with the Product Hunt community

Our users have been asking for this integration since day one, especially after Krisp added an AI note taker to its Voice AI app. In fact, it got 6x more votes than the second most-requested integration.

Which naturally leads to the next question: why did it take us so long to build?

A small but very nice update from the murmur corner of the internet:

A week after launch on Product Hunt, murmur got the ElevenLabs startup grant! Given that it's built around practicing awkward, important, and often slightly dreadful phone calls out loud, this feels especially fitting.

Just wanted to say thank you again to everyone here who supported the launch, upvoted it, commented, or gave it a try. Product Hunt gave the app a real push early on, and this is one of those moments that makes the whole thing feel a bit more real.

The grant should help me keep improving the voice side of the experience and give the app a bit more room to grow without immediately putting the brakes on everything.

Today I received a question about proper launch preparation:

Nika, how long should this take us?

And I didn t have a clear answer.

A story and an experiment have been spreading on X: Scientists uploaded the brain of a fruit fly into a computer, and now it lives freely in its own simulation.

We managed to clone the physical form of animals more than 30 years ago (for example, the cloning of a goat using SCNT in 1999). There was even a controversial case in China where a scientist was sued after attempting to create gene-edited babies in 2018.

Here we go again!

I started setting new goals every 3 months and then checking in on how well I was doing.

One recurring issue we ve been seeing with Supabase setups is not the database itself, but how credentials are managed across environments. The common pattern looks something like:

• credentials stored in .env files or secrets managers

• multiple environments (dev, staging, prod)

• manual propagation or duplication across those environments

It works, but over time it seems easy for things to drift:

• a key gets rotated in one environment but not others

• a redeploy misses an env var

• credentials get misconfigured during setup or migration

Source.

We ran an experiment 2 weeks ago.

Control group: a two-hour roadmap review meeting. Six people in a room (virtual). We debated features. We argued about timelines. We discussed dependencies. We left feeling productive.

Test group: We fed the same roadmap into Claude. No slides. No politics. No one trying to protect their pet project. Just the raw plan. The prompt: "Analyze this roadmap. Identify the three most likely failure points. Use first principles reasoning. Assume we will follow your recommendations without ego. If you need more data, ask for it."

The results were not symmetrical.

Three months. Two developers. One feature nobody used.

I knew it was bad when I checked the analytics and saw that the only person who used it more than once was me. And even I stopped after the second week.

Here's how I knew it was a waste of time. Not in hindsight. In the moment. I just ignored the signs.

The first sign: I couldn't explain it in one sentence.

Hi everyone,

After launching Telea here, I received a lot of valuable feedback from the community. One recurring point was the need to try the product in a real workflow before committing.

Based on that, I ve just introduced a free trial.

AI workflow automation tools help you design, run, and evolve workflows that actually take action not just suggest what to do next. Some use AI to make workflows easier to build. Others embed AI directly into execution so workflows can handle ambiguity, make decisions, and adapt as they run. The strongest tools do both.

This definition excludes tools where AI only generates static workflows and then steps aside. It also excludes general assistants that never meaningfully participate in end-to-end execution.

Six months ago, I launched a product.

Beautiful landing page. Great onboarding. Real customers. Solid retention.

One problem: AI never mentioned it.

Not in ChatGPT. Not in Perplexity. Not in Gemini.

Testing between the two - would love to know your thoughts!

I noticed I was opening full GIS software dozens of times a day just to answer:

"what's in this GeoJSON?"

Hey guys, I'm opening this thread to collect your questions, feedback, and curiosities about Clico. Whether it's about how it works, what's coming next, or how to get the most out of it. Drop it below and we'll answer everything here.
Keep clicooooo!

Hey! Quick building-in-public update on what we shipped today:

- Privacy Policy & Terms of Service pages (finally legit)

- Collapsible FAQ on the homepage cleaner, less clutter

- AI-friendly setup so ChatGPT, Perplexity & Claude can discover and recommend us

A few years ago, getting a VC check was the ultimate shortcut. The fastest way to scale. The signal that you'd "made it." But with AI is a little bit different.

Global VC funding declined 30% in Q1 2024. One of the lowest quarters since 2018. And bootstrapped startups are quietly catching up. Recent data shows bootstrapped businesses are growing as fast as VC-backed startups, while spending only about one-quarter as much on customer acquisition.

Hey PH community, looking for feedback.

Hello Inbox is an email deliverability platform helping businesses reach the inbox (think GlockApps).

Everyone is talking about vibe coding right now. Let AI handle the code while you focus on the vision. It sounds revolutionary. So we tried it.

For one week, our team at Murror used AI coding tools for everything. New features, bug fixes, refactoring. We wanted to see if it could genuinely speed up our development cycle or if the hype was getting ahead of reality.

Hey PH!

AI memory is personal by default. Your context, your preferences, your saved info, none of it is visible to anyone else.

Which is great for privacy. Terrible for collaboration.

My partner and I are avid travellers. I plan, he executes. Last year I sent him more AI chat links than memes trying to get us on the same page for trip planning. It was absurd.

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.

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:

We're enhancing Rankfender's Content Generation Engine (RCGE) and v2.2 is coming in the next few weeks. Before we lock things in, we want to know what actually matters to people who use content generation tools.

Here's what RCGE already does:

• Intelligence. It analyzes the top 10 ranking articles for any keyword and identifies patterns. What structure do they use? What headers? What formatting? What makes them get cited by AI? Then it builds a brief based on what actually works, not guesswork.

• Structure control. You can add, remove, and reorganize H2s before generation. No fixed templates. You decide the flow.

• Inline images. Generated articles include images, not just text walls.

• Regeneration. Mess up one paragraph? Regenerate just that part. Not the whole article.

What we're adding in v2.2:

In a discussion forum with @monatruong_murror , we talked about how AI can help us learn things that aren t naturally familiar to us, like programming.

The biggest challenge was/is:
Getting AI to guide you toward a solution, instead of just giving you the answer.

Two conversations. Same week.

First founder said,
Really interesting product. Love what you re building.

Great energy. Smart questions. Strong validation.

We never heard back.