I am building a product around relationship-driven outreach, and one workflow keeps coming up: When someone has a goal like hiring, sales, fundraising, partnerships, or career exploration, the hard part is often not writing the message. It is deciding who is actually worth reaching first, why now, and what the smallest good ask should be. I am curious how other makers and operators handle this today. When you are trying to reach someone through your network: 1. Do you start with the most senior person, the closest connection, or the person closest to the context?
2. What makes a first ask feel easy to answer?
3. Where does the workflow usually break: choosing the person, explaining the reason now, finding the warm path, or writing the first message? I am building Netlio in this space, so I am asking partly from product research, but I am more interested in the workflow than in pitching the product here.

I've worked around speech technology for years, so I've probably tried voice input more than the average person.

And there's one thing that keeps bothering me:

Most voice tools remove the typing but leave all the interruptions around it.

I can dictate a sentence.

Hey Product Hunt

I m Rishil, a solo founder building Provoon.

I kept noticing something weird with testimonials.

Getting them is hard.

I'm a developer in the Salesforce ecosystem. Every job search I'd waste hours rewriting my resume for each posting so I built JobHelper.

What it does:

- Upload your resume once

- Browse aggregated jobs in a feed

I m still in school and build small things with Claude Code. My own workout log lives in a spreadsheet right now, it s fine, but logging a set mid-workout on my phone is clunky, and Strong/Hevy solve that but lock your data behind a subscription. The free trackers I ve tried don t export at all.

Considering building one thing well: fast mobile logging, full CSV/JSON export, $39 once, no subscription ever.

I m building HUMANITY.TXT, a tiny public archive where each person leaves one numbered line. A fair criticism was: why trust a database owned by one site?

I m considering making durability explicit:

every accepted line appended to a public Git repository

every change timestamped in commit history

We built MemShift around a frustrating problem we kept experiencing:

You find something incredibly useful online.

A GitHub repo.
A YouTube tutorial.
An article.
A Reddit post.
A random page that perfectly explained something you were struggling with.

You think:

We created I AM a sanctuary to be you, a space to pause, reflect, get to know yourself better, and remember that Being comes Before Doing.

If you have 2 minutes, it would mean so much to us if you could:

Try I AM:

[https://i-a-m.netlify.app/?ref=p...

We built Tidbit around a simple observation:

We already spend a huge amount of time scrolling.

We discover AI concepts, psychology ideas, finance tips, history facts, books, startups, and random things we're curious about.

I've been building PeakRoutine for the past 1.5 years and honestly, growth marketing has never been my strong suit. It's not my core skillset, and it's not something I naturally enjoy.

So I did what any engineer would do: I leaned into what I love, and built an agent to handle it.