Connect with the Product Hunt community

Hello guys,

we are planning to implement the Murmell bots. It's an alternative to Grok bots, which can enable the multiprovider thing (using you bots with claude, codex, etc) and also make the bot durable in the cloud.

Everyone's shipping voice agents this year. Receptionists, collections bots, lead qualifiers, support lines. The demos look great.

Then they hit a real phone call.

I lead growth at a voice AI company, so I sit in on a lot of these conversations. And the thing that surprised me is how rarely the LLM is the problem. It's almost always the voice layer underneath it. The latency that was 90ms in the demo, suddenly climbs to 400ms on a real phone call. The voice that sounds great in English and falls apart the moment someone switches to another language mid-sentence. The TTS that reads a pincode like a phone number. Or the per-minute bill that was fine at 10,000 minutes and became the biggest line item at a million.

Always see people buying .com names and making logos before even building the actual tool.

I used to think you need the whole setup ready to look legit, but buying tech stuff early feels like a waste if the idea flops.

How long do you run on free subdomains or cheap placeholders before dropping money on official branding?

Hi everyone,

Attyn is now live on iOS for iPhone and on Android.

When you work a regular office job, you have some natural boundaries.

You finish work on Friday, and there s a whole weekend ahead.

Maybe you have a few drinks on Friday night, stay up late, skip your workout, or just do whatever you want.

And that's fine.

StealthHound just got a little more global.

Swedish language support is now live.

Maker update: Termexo v0.8.3 is out. I maintain this MIT-licensed Windows workbench for Claude Code, Codex CLI, OpenCode and real terminals. If typing has felt delayed while agents are working, this is an update worth installing.

Give keystrokes room to run

Road to 1,000,000 Votap users - Day 83 | Current: 1469

We ve been building ProductBridge as an AI-native alternative to traditional customer-feedback tools.

But we don t want polite founder feedback.

One thing we didn t really have doubts about when launching WIT was the main use case.

Then the Product Hunt community came to check the product out and some of the feedback made us look at that use case from a different angle.

There's a specific moment that happens with almost every project: the agent produces code, it passes your tests, everything's green, and there's a real pull to just move on to the next thing. Totally understandable, the whole appeal of this workflow is speed.

But there's a gap between "this works" and "I understand why this works," and that gap is where the real risk hides. Not because the code is wrong, most of the time it isn't, but because the next time something breaks nearby, you're debugging code you never actually read closely the first time.

during the BC (before ChatGPT) era, this gap barely existed. You wrote it, so you understood it, mostly by necessity. Now understanding is a separate step you have to choose to take, not something that comes free with writing the code yourself.

One habit that closes that gap fast: before merging anything non-trivial, ask the agent to explain its own implementation back to you, line by line, in plain language. Not as a formality, actually read the explanation. Two things tend to happen. Either it confirms your understanding and takes thirty seconds, or it surfaces an assumption you didn't know was baked in, which is usually the more valuable outcome.

three bugs an ai wrote for me this week. every test green. all three would've paged me in prod:

1. webhook retried charged the customer twice

2. subscription.activated arrived before subscription.created they paid, app said not entitled

3. a stale event flipped a canceled sub back to active free access, forever

none of these show up in a 200. you find them from a customer or you fire the ugly event orders on purpose and find them first.

we now throw every ordering + every duplicate at your handler and hand back the exact sequence that broke it.

Hello guys, here is my question :

what project will you do with infinite AI tokens

A credit balance turns every click into a purchase decision. That's the whole problem and it has nothing to do with the price being too high.

In a tool with several studios a video render costs roughly 40x an image. One credit unit spanning both means the user is doing arithmetic before every button, and the arithmetic gets worse as the balance drops. The first render feels free. The third one has a price tag on it. People stop long before the balance hits zero, and that shows up in your dashboard as low usage, never as a complaint about cost.

We just launched Dash to Cart 2.0 on Product Hunt.

That sounds a little strange coming from someone building a subscription management app, but it s probably the biggest thing I learned while working on Subo 1.3.

Of course people need to add, edit and organize their subscriptions.

For a while, we were tracking the usual SaaS stuff like signups, pageviews, DAU, WAU, and retention charts. Useful to know, but none of it told us whether people were actually succeeding with Causo. So we started using PostHog properly and built our own dashboards around the things that matter for our product.

Causo now has two sides:

Causo for Fundraising has a database of 1,000+ funds and 17,000+ investors. It helps founders find the right partner at the right firm, understand why that person is relevant, and write outreach specifically for them.

Causo for Sales uses the same technology to research almost any niche live. You describe the companies you want, and it finds them, checks why they fit, identifies the right people, verifies contacts and writes the outreach.

Hey everyone octoscope 0.30.0 is out, and this one has an odd origin story: three of its four changes were written by one of you.

They came in as a comment under the 0.27.0 launch. He didn't ask for a single feature. Instead he found three places where octoscope's report claimed more than it had actually verified and every one of them held up when I went and measured it. One even turned up a bug that had been sitting in the code for several releases.

Strong claim, hear me out.

Every founder update reads the same now. "excited to share," emoji bullets, fake vulnerability about the rollercoaster. doesn't matter if it's real or not, it all sounds identical.

Noticed this hard while hiring. read every dm myself for a growth role. most were obviously ai-generated, same tone, zero thought put in. the ones that stood out were rough, specific, clearly written by someone who actually looked at the problem first.

Think the same thing's eating founder credibility. people used to trust a post because it sounded like someone actually figured something out.

For me, it is the discovery. I regularly find new products, see how founders present their ideas, and learn from the conversations around each launch.

Launching Meridian made the platform even more meaningful to me. Meridian finished as the #1 Product of the Day, and the support from the community made all the work behind it worthwhile.

Meridian was created to help developers capture their work automatically and make sure their contributions do not go unnoticed. It is open source, so anyone can explore the project, contribute, or follow its progress.

What keeps you coming back to Product Hunt?

https://www.producthunt.com/prod...

Checking on the business is a ritual - daily, weekly, monthly - and today it's entirely manual. You open the same tools, scan the same numbers, and rebuild the same report, over and over. Whatever falls outside that routine goes unnoticed, and by the time something unusual gets investigated, it's often too late to matter.

Scaffolding frontend layouts, Tailwind components, and basic CRUD forms through natural language prompting is remarkably smooth now.

However, once an app requires dynamic, competitive state like handling real-time bids, managing race conditions when two events trigger simultaneously, or verifying payment webhook signatures pure conversational generation starts hitting walls.

@Kilo Code launched a fully native plugin for @JetBrains.

Installation, model choice, pricing, team setup... Here's everything you want to know about it.

The gap most auto-fix tools have

They tell you the bug is fixed. They don't show you. Our rule has always been: make the bug happen on real code, apply the fix, show it stops happening. The gap was we could only do that for bugs we'd scripted in advance. Anything unusual and the honest answer was "found it, fixed it, can't prove this one."

What we built

We taught FetchSandbox to write the reproduction itself, no pre-scripted test required.