I was about to put my install count on my landing page. 2,411, which felt like a real number for something nine days old.
Then I split it by version and it fell apart. 0.1.0 got 172 downloads last week. So did 0.2.0, and 1.6.1, and every other version I have ever published, all sitting between 150 and 200. Nobody deliberately installs the first release of anything. A real user base concentrates almost entirely on latest. A flat line across every version that has ever existed is mirrors and scanners walking the registry, and they do that to every package, forever, whether or not one person wants your code.
So here is the check. It takes about two minutes. Split your downloads by version. Flat across all of them means automation. Concentrated on the newest one or two means people.Cross it against a surface only humans reach. My repo had 81 unique visitors while the registry was reporting 2,411 downloads. Thirty to one.Look for a spike with no correlated movement anywhere else. Mine had 1,542 downloads in a single day and the visitor graph for that day is flat. Nothing happened. A mirror woke up.
Then work out what you cannot see at all, which was the uncomfortable one for me. Anyone using my tool the way it is meant to be used never touches a single thing I can count. It runs locally. It never loads my site and never opens my repo. Their usage is indistinguishable from a scanner in the only number I have.
Search rank is the other one I would not lean on, and I say that as someone whose rank went up this week.
I am 5th on npm for "pre-production checklist" and 8th for "security checklist". Two days ago I was 8th and 8th. The only thing that changed in between was that I published a new version. Nobody needed anything for that to happen.
And then look at where my visitors actually came from. My own site, GitHub itself, the MCP registry, Google twice, Telegram once. npm is not on that list at all. Not low. Absent. Ranked 5th and it has sent me zero people, because almost nobody discovers a package by searching npm. They arrive already knowing the name.
There is a loop in it as well. npm's search score has a popularity component fed by download counts, and I have just spent this whole post establishing that my download count is mostly mirrors. So the rank is partly computed from the bot number, and then the rank gets quoted as evidence of traction. Same number, different hat.
The one query where my actual audience would be, "mcp checklist", I do not appear in at all. That is the only ranking of the four that would have told me anything useful, and it is the one nobody would ever screenshot.
What I track now is unique cloners, 116, and CDN file requests, 95 a week. Both far smaller than 2,411 and both far more likely to be a person.I still show a number on the site, because everyone does and a visitor reads mine against everyone else's. But I stopped using it to decide anything, and that turned out to be the part that mattered.
If you have shipped a package, go split yours by version. I would genuinely like to know whether anyone's is concentrated the way it is supposed to be, because I am starting to suspect almost nobody's is.

In the AI era, it is no longer so difficult to finance things from your own resources bootstrapped (except for promotion or hardware-intensive solutions).

I have always saved money and tried to do things myself (what I didn't know, I learned to do to save on financial costs).

My instinct is always to polish. I want the first thing someone sees to be good, because I figure you only get one first impression and an embarrassing v1 sticks to you.
But almost every product I actually respect started out rough. The early versions were janky and half-broken, and the founders shipped anyway because real users teach you things a year of polishing never will.
So I go back and forth on this constantly.
The case for shipping ugly is that you stop guessing. You find out what people actually care about instead of perfecting features nobody asked for. The case for waiting is that a bad first experience can kill momentum before it ever gets a chance to stick, and you don't always get told why people left.
I think the answer depends on how reversible the launch is. A small audience that forgives you is very different from a big public moment you can't take back.
But I'm probably biased toward polishing longer than I should, and I've definitely buried good ideas thinking they were not ready yet.
Where do you land: ship the ugly version and learn, or hold it until you're proud of it?

Been browsing Product Hunt for a while without an account and finally made one.

Something I've noticed about my own reactions. When a launch page is really slick, a nice demo video, a beautiful site, testimonials already in place, I get a little suspicious. I know that's unfair, plenty of good products have good design. But my experience has been that the polish on launch day doesn't tell me anything about whether the thing works when I actually use it.

Some of the roughest-looking listings I've clicked on turned out to be the most solid tools. And some of the prettiest ones fell apart the moment I tried anything outside the demo flow.

Curious if anyone else has this bias. Has a really polished launch ever turned out to be exactly as good as it looked? Or is there a tell you've learned to spot?

Yesterday, I came across an article on TechCrunch that OpenAI is upgrading ChatGPT search with shopping features.

Slowly but surely, ChatGPT is taking over Google's role and doing it well. I ve noticed it myself, especially how it s replaced much of my browsing.

Notice this pattern a lot, technical founder pairs with another technical co-founder.
Makes sense on paper, same language, fast execution.
But distribution often becomes an afterthought when nobody on the team actually lives in that world.

Wondering if the stronger combo is one person deeply into building, and one person deeply into attention, algorithms, what makes people actually stop and care, not a marketing hire added later, but an actual co-founder who treats distribution as seriously as the other treats code.

Genuinely not sure if i'm right about this, would love to know if the two technical founder setup has worked well for people here.

If there's one thing marketers know, it's that most holidays and promotional opportunities fall between September 1st and December 31st.

Summer is generally quieter; people are on vacation, and paradoxically, more on their phones, but things are still slower.

In yesterday's post, I broke down the goals (and achievements/failures for Q1 2025).

So happy to see your contributions as well and would like to know...
What is on your plate for the next Q2 period?

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?

Nobody said running a startup was easy but some issues whether it's increasing DAU, perfecting ad copy, increasing MRR, hiring, or whatever can be pull your hair out levels of frustration.

What's one pain point you are struggling with at the moment? Drop it in the replies and then help someone else based on your experience!