Rajiv Ayyangar

Quick, easy email integration to build flows that include email notifications.

Great for voice data - text to speech, speech to text, or any workflows that involve creating or analyzing voice data.

Clean, organized interface for writing directly to your Notion page via MCP. Fantastic canvas for workshopping the output of MCP flows.

Easiest interface for configuring MCP servers and toggling on/off tools of servers to which you're integrated. Easy to orchestrate agentic flows with total visibility into the code being executed.

I've been using Aqua Voice for a bunch of things. I use it a lot for quick communication in Slack. On the more personal front, I use it a lot for vibe coding. One of the things I really like is the long dictation mode and the ability to edit. It also seems to have a really good sense of my current context, which is great for vibe coding. As for what can be improved, the more I use it, the more I want it to be even faster. Although it's quite fast already. Also, I often want to dictate when there are people around. So it would be cool to add the ability to whisper very, very quietly. Wisper Flow actually does quite well in this regard.

We've used BAML to generate and iterate on structured outputs for a variety of LLM-based features - including several still under development. "We love BAML" has been overheard in our watercooler chats many a time.

Used an advanced version of Agent V2 for this. It seems a bit smarter than the previous version of Agent.

still loving Wispr Flow for vibe coding and dictation in general

I used Wispr Flow for the prompt and all instructions in Replit Agent. It's becoming a pretty ingrained habit at this point!

database via Repl.it agent was Neon. Seems stupid simple to use so far - even for a non-coder.

I used Repl.it agent to code this in about half an hour! The beta of the V2 agent was pretty good - only one rollback and a few bug fixes.

We used Hex to do quick ad-hoc research when tuning our forum ranking algorithms, as well as to set up dashboards for tracking user engagement after launch.

We still love Cursor here!

Our engineering team leans on Graphite Reviewer for pull request reviews. It doesn’t replace a human reviewer, but will catch a few things a week that our human reviewers miss. And the Graphite reviewer usually runs before a human reviewer gets to the pull request. Which is nice for saving expensive, human time. On an engineering team, for every hour of code writing, there are 10 hours of code fixing and maintenance. Graphite is pretty key for us to reducing that fixing and maintenance time. Another nifty thing about Graphite is pull request stacking. Our engineering team spans 14 timezones at Product Hunt. It’s not unusual for someone to crank out a bunch of work while the rest of the team is asleep. Pull request stacking is quite helpful for smoothing out that workflow.

We recently switched to Linear and have loved the speed, clean UI, and generally the feeling of organization that comes with it. Is it because our CTO set up the perfect triage process, or it it because Linear is awesome? We'll give a shout out to both :)

We built the bulk of this while in-person during our SF offsite. When we went back to working remotely, we leaned heavily on Tandem to keep the fast, fluid conversation going. It almost felt like we were still in the same room. The high-fives are cool too :)

A bunch of our team uses Windsurf. It's ok Cursor, don't panic, there are still some Cursor users as well. I personally find Windsurf producing better diffs than Cursor. Windsurf seems to be better at pulling in the correct context. And Windsurf cascade prompting iterates on the suggestions automatically (without me in the loop).

We drafted and edited the product landscape posts on Notion...plus used it for our internal docs, product kanban, and more!

As a former data scientist, Hex is the analytics tool I dreamed of. For this launch in particular we did a ton of research on web traffic and user engagement using Hex. In particular, the magic tool has been helpful - since my SQL is trés rusty.

In launching Category Pages, SEO was a big consideration - a main goal of this feature. Positional helped us assess progress without creating noise or confusion.