Introduction
Product Hunt taught me something this week, but it was not what I expected to learn.
24 hours after launch: 3 upvotes (one was mine), 0 comments. By every metric the launch failed.
Here is why I am not pivoting, not quitting, and not building an AI wrapper.
Who I am, briefly
I am Ykiki. AI Lead at a startup by day, indie hacker on the side. I run two small products called Respo and PaperTracker. The third one I just launched is MakerPulse — a metrics dashboard for indie makers that pulls Stripe, App Store Connect, and Google Analytics 4 data into one screen.
I built it because every Monday morning I was opening five tabs and spending 30 minutes copy-pasting numbers into a Google Sheet whose formulas I had already broken twice. The closest existing tool, Baremetrics, starts at $129/month, which is fine if you are doing $50k MRR but absurd if you are doing $50.
So I built the version I wanted. Free plan, Pro at $19/month, four weeks of evenings and weekends. Shipped on time. Launched. Flopped.
The launch numbers
Let me put the result on the table first, because too many launch posts dance around it.
Day 1 on Product Hunt
- Upvotes: 3 (one self)
- Comments: 0
- Signups: single digits
- Revenue: $0
I had been quietly optimistic. I imagined I would be replying to a healthy thread of comments, watching the upvote counter tick up while I pretended to do my day job. Instead I refreshed the page every 20 minutes and watched nothing happen.
It stings. Not going to pretend otherwise.
Why it did not land
I keep coming back to one observation. Scroll Product Hunt today and the front page is almost entirely AI tools. Dev tooling and indie SaaS, unless they have a striking hook, just do not get the algorithmic lift they used to.
The tempting conclusion is "I should have built an AI tool." I do not buy it. Here is why.
The AI wrapper space is saturated. Every day brings another GPT-flavored variant of an existing workflow. Differentiation gets harder, not easier.
The model labs eat their own wrappers. Anthropic and OpenAI ship at a pace that no solo dev can outrun. If your moat is "convenient interface to someone else's model," your moat is on a timer. The labs will use their own AI agents to ship the thing you wrapped, and they will ship it better.
The boring problem I am solving does not go away. Indie makers will still spend 30 minutes a week reconciling numbers across five tabs in 2027. AI does not solve that for them. A unified dashboard does.
So MakerPulse staying as MakerPulse is not stubbornness. It is a bet that non-AI problems still pay rent, and that the AI gold rush will, for a lot of indie devs, turn into the AI consolidation aftermath.
What I would actually change
Honest list, not a humble brag list.
The launch had no audience pre-built. I shipped quietly for 4 weeks and then waved at the launch day crowd. Of course nobody waved back. The makers who win Product Hunt today have spent months building an audience before launch day. I had not.
The hook was too rational. "Stop checking 5 tabs, see your metrics in one place" is true and useful and completely forgettable. There was no surprise, no contrarian take, no number that made you stop scrolling. Compare it to "I shipped a SaaS in 4 weeks and got 3 upvotes" — which, I notice, is the headline of this post. That hook works. The product page hook did not.
I aimed at the wrong day. I picked launch timing for myself, not for my audience. Tuesdays in Pacific time are crowded. A weekend launch into a smaller field probably would have given me more visibility, even if absolute traffic is lower.
I did not ship the screenshot. Until the night before launch I kept polishing the dashboard screenshot for the listing, and that polish was zero-value. The screenshot is not the product. The product is the product. Hours I spent on the screenshot were hours I did not spend telling anyone the launch was happening.
I am not sure all four would have changed the result. But I am sure they each cost me upvotes.
What I am keeping
The interesting part: there is also a list of things I would not change.
The 4-week scope. Constraint produced clarity. Every "wouldn't it be cool if…" got cut. The product that shipped is the product I would have built in 12 weeks too, except 8 weeks earlier.
The technical decisions. Supabase Auth + RLS over NextAuth, Stripe Connect OAuth over API key entry, ASC API over an iOS SDK integration. These were all chosen by one rule: what reduces friction for the user? That rule will outlast Product Hunt rankings.
The price. $19/month is correct for indie makers doing under $5k MRR. I am not raising it for revenue and I am not lowering it to chase signups. Wrong customers at a low price is worse than no customers.
Dogfooding. I am the first user of MakerPulse and the harshest reviewer of it. If I lose interest in checking my own dashboard, the product is broken. That feedback loop is faster than any user interview.
The plan from here
Product Hunt is a one-day event. SaaS is a 365-day marathon. I keep repeating that to myself.
Here is what I am committing to publicly, on this post, so I cannot quietly walk away from it:
Every Friday for a year: a build-in-public post on X, in both Japanese and English.
Twice a month: a technical or strategic write-up here on Dev.to and on Zenn (Japanese).
Within 3 months: 3-5 SEO long-form articles on the topics indie makers actually search for — "how to calculate Stripe MRR correctly," "App Store Connect API gotchas," that sort of thing.
Within 6 months: public MRR pages — let MakerPulse users opt in to publishing their own MRR badge, which doubles as distribution.
None of this is glamorous. None of it bets on a single launch day. That is the point.
If you are reading this and you are about to launch, or you just launched and it underperformed: the launch is the start of the work, not the end of it. The makers I respect most have all had the underwhelming launch. The difference is what they did on day 31, day 90, day 365.
Talk to me
Honest reactions are the most useful thing you can give me right now.
"This won't work because…"
"I would actually pay for this if it did X"
"Have you seen [competitor]? You are reinventing it"
All welcome. X DM, Dev.to comment, email — whatever is least friction for you.
Onward.
🔗 MakerPulse (free plan available): makerpulse.app
🐦 Personal X: @ykiki_dev
🐦 MakerPulse X: @MakerpulseApp
Top comments (3)
This is the most useful Product Hunt postmortem I've read this quarter. The "boring problem still pays rent" thesis is right — and the discipline to NOT pivot to an AI wrapper after a flop is rarer than people admit.
The diagnosis "the launch had no audience pre-built" is the part that should be on every founder's wall. Most postmortems blame timing, copy, or PH's algorithm. You named the actual lever — months of compounding presence before launch day.
Three specific things I'd build on:
The MRR badge → distribution play (6-month plan) is the strongest moat in your list. Public MRR pages from real users beat any landing-page testimonial because they're opt-in proof, not curated. Baremetrics' Open page used to drive 30%+ of their inbound. Ship the badge plus an Open Companies index and you're orthogonal to PH entirely.
JP-side Zenn deep-dives are the underrated channel in your bilingual cadence. "ASC API gotchas" in Japanese is an SEO gap with very little competition and a sticky audience that will compound for years. The English audience is crowded; JP technical audience is not.
One missing axis in "what I would change": outbound to your ICP during build, not post-launch. Indie makers under $5k MRR aren't all on PH — they're complaining about Baremetrics pricing in r/SaaS threads, asking "anyone use a dashboard for this?" on IH, opening issues on competitor repos. The wedge in solo SaaS is talking to those people 4 weeks before you ship.
I'm 30 days into building DevSignal at devsignal.dev — exactly that "find your people during build" tool. Surfaces warm leads for solo SaaS founders by mining GitHub stars, HN comments, and Reddit threads. Honest reaction from someone who lived your post: would something like that have changed your launch curve, or is the issue more upstream (audience itself wasn't there)?
Either way — would love a 30-min call to compare notes on the 12-month commitment. Early access + lifetime 50% off DevSignal in trade for the chat. Your postmortem has more concrete signal than 3 Founder Twitter threads combined.
Following MakerPulse and your build journal. The "day 31, day 90, day 365" framing is the right one.
Thanks for the thoughtful read.
The Baremetrics Open page reference is exactly the kind of historical context I was missing — the opt-in proof vs curated testimonial framing is going on the wall. JP Zenn as the underrated SEO channel: I think you're right, and I had been undervaluing it because the audience size looks smaller in raw numbers. The compounding sticky audience point reframes it.
The outbound-during-build axis is the one I'd push back on slightly, but only on framing. Outbound assumes a thesis about who the user is. I shipped MakerPulse partly to find that out — the people who actually signed up post-launch don't fully match the ICP I would have outbounded to during build. So for me, build-then-listen worked better than build-while-outbounding. But for someone with a clearer ICP than I had, your version is probably right.
On the call — going to pass for now. I'm trying to be ruthless about protecting build time in the first 90 days post-launch, and 1:1s are the easiest thing to say yes to and regret later. If DevSignal ships something I can self-serve into, I'll take a look.
Appreciate the substantive comment either way.
Fair pass — and "1:1s are the easiest thing to say yes to and regret later" is going on my own wall. The first 90 days are exactly the time to be ruthless about that.
The pushback on outbound-during-build is the most useful framing I've gotten on DevSignal's positioning. You're right that outbound assumes ICP clarity that most pre-launch founders don't have. The honest version of the product is probably: outbound works when you have a clear thesis; build-then-listen works when you don't; and DevSignal is wrong for the second crowd. I've been collapsing those two cases. Going to think about how to state that more sharply on the landing.
When DevSignal ships something self-serve (closed beta late June), I'll send a note. No commitment in either direction.
Building well on MakerPulse.