I launched Invoice Badger here last week. Single digit upvotes, zero signups. Nobody was rude about it, nobody was anything about it, which is worse.

Writing this up because the post mortems I've found useful were always the honest ones, and there are plenty of the other kind.

I'm trying to solve online friendships. Am I solving a real problem?

Hi everyone,

I've been thinking about something that's been bothering me for a while.

Making genuine online friends feels much harder than it used to.

Genuine question for makers who've launched here.

I browse PH almost daily. I upvote stuff, sign up on launch day, leave comments. Then 3 days later I want to use a tool and can't remember the name.

A month ago, a friend of mine approached me about creating a calorie-tracking app.

Considering that people (especially Generation Z) are more health-conscious, I really like this idea.

Port22 and AgentMicro yesterday. Termexo and TreeWork today. Four launches inside 48 hours whose core job is telling you what your coding agents are doing and which one is stuck.

When four teams independently build the same wrapper in two days, that isn't a market forming. It's a primitive the agent runtimes should have shipped and didn't. Every one of them is solving the same thing. An agent can be working, blocked, done or failed, and there is no standard way to ask it which of those it is right now. So everybody tails a PTY, or scrapes session metadata off disk, or watches the screen, and ships that as a product.

Hey Product Hunt community!

When preparing for a launch or handling sudden user traffic, scaling servers can quickly become expensive if every single user request hits your main database.

While stress-testing our API endpoints for our upcoming SaaS, we noticed that 70% of database queries were fetching the exact same static configuration and user preference data over and over.

Here is the exact setup we used to optimize response times and cut server overhead:

The answer is yes.

Team size community engagement is the strongest predictor
B2B categories (API, Payments, Fintech) convert at 3 the baseline
Rank #1 on launch day 2.2 more likely to raise Series A

The old model was mostly built around humans picking up tickets, moving them across a board, and writing updates after the fact. That still matters, but the workflow is changing.

Now a single feature might involve a human writing the intent, one agent creating a branch, another reviewing logs, another opening a PR, and someone else deciding whether the result is safe to merge. In that world, the project management tool cannot just be a static task tracker.

It needs to become the coordination layer between people, agents, code, reviews, and decisions.

For me, the interesting questions are:

Built a five beat welcome film this week. Each beat swaps an on-screen label at a fixed timestamp, 0s, 2.6s, 6.0s, 9.2s, 12.4s, across a 13.9s clip. No timeline or animation library involved, just an array of at and label pairs, plus the video element's onTimeUpdate event computing progress and a reduce picking the active beat.

It works, but onTimeUpdate fires at whatever cadence the browser feels like, so the swap is never frame accurate. Close enough that nobody notices on a phone screen, but it still feels like the wrong tool for the job.

Dictation tools and meeting notetakers technically solve two different jobs. One types for you everywhere, the other listens to your calls and hands you a summary. But they both sit in the same "capture" corner of the stack, and I've noticed a lot of people running one of each without ever really deciding to.

My own take is that the split is mostly historical. Dictation came from accessibility, notetakers came from sales tooling, and they met in the middle by accident. If either side added the other's core job tomorrow, I'm not sure most people would keep paying for two.

Curious whether that matches reality or whether I'm wrong about it.

Where are you right now?