The Product Hunt Launch That Didn't Trend

Maya Okafor lives in a one-bedroom in Lisbon's Graça neighborhood, three flights up, with a window that opens onto a tiled rooftop and, if she leans, a slice of the river. On the morning of her Product Hunt launch she made coffee at 7:42am local, which was 11:42pm Pacific the day before, which meant she had eighteen minutes before her launch went live at midnight PST. She'd written this down on a Post-it stuck to the lower-right corner of her monitor: 'PH GO LIVE 8:00 LISBON.' The Post-it had a small coffee stain on it from a previous morning.

She'd been preparing for three months. Not in a casual way. In a project-managed, Notion-doc, sub-page-with-sub-pages way. She had a 'Hunter Outreach' tab with 38 names in it, color-coded by how warm the relationship was. She had a folder of GIFs at exactly 800px wide, looped at 4 seconds each, exported from Screen Studio with the cursor zoom turned on. She had a Loom intro video where she'd re-recorded the opening 11 times because her voice cracked on the word 'finally.' She had a tweet thread, scheduled in Typefully, with the first tweet timed to 12:01am PST and the last one timed to 7:34pm. She had a Google Doc of friends and former coworkers she planned to DM, ranked by likelihood of actually opening the message.

At 8:00am her product went live. By 8:14am she had 9 upvotes. By 8:30am she had 22. She wrote her first comment — a paragraph she'd rewritten four times that week, ending with a question to invite replies. She refreshed the page. She replied to the first commenter within ninety seconds. She replied to the second one within two minutes. She got up, paced the room, came back. She opened a second tab to check the leaderboard. She was #6.

At 1:00pm Lisbon time, after a sandwich she didn't taste, she was #9. At 6:00pm she was #11. At 11:00pm she was #14. Final. Two hundred and thirty upvotes. Not Product of the Day. Not even close to the top three, which is the thing you can screenshot and tweet about. She closed her laptop, walked down the three flights, and bought a beer from the cafe on the corner. The owner asked how her day was. She said, 'Fine.' She drank the beer on the curb.

She thought she'd lost. She was wrong, but she didn't know it yet.

What Product Hunt is actually for in 2026

Here's the part nobody tells you in the playbooks, which mostly were written in 2017 and copy-pasted ever since: Product Hunt is not a viral lever. It hasn't been for years. The TechCrunch pickups, the explosive traffic spikes, the 'we got 50,000 signups overnight' stories — those belong to a different internet, one where PH was the front page of the new-things web and there were maybe forty good products launching a week.

In 2026 there are sometimes forty products launching by 9am. The leaderboard is a churn machine. Being #14 and being #4 differ by maybe a thousand pageviews, most of which bounce. The badge is nice. The traffic is real but small. The signups, if your product converts, are a number you can count on two hands.

What PH actually is now is a meetup. A controlled-burn ritual where a specific community — indie founders, technical PMs, designers who like new tools, the small subset of investors who still scroll for fun — gathers around your thing for one day. They poke at it. They comment. Some of them email you. The leaderboard rank is the seating chart. The people in the room are the room.

This is a different game than Hacker News. Show HN is brutal and technical and the comments will tell you, in plain language, what's broken about your architecture or your pricing or your premise. The audience there is engineers who will not be your customer but will absolutely tell their friend who might be. The stakes are different — you can win Show HN and get nothing, or get torched and still walk away with the three best pieces of product feedback you'll ever receive.

An X launch is different again. It's a rhythm thing. A thread on launch morning, the right replies in the right places, a quote-tweet from someone with reach, and you're at the top of someone's timeline for six hours. Then it's gone. There's no archive page. There's no comment thread you can return to in two weeks. X is a wave; Product Hunt is a campfire.

The mistake: treating it as a marketing campaign

Maya's three months of prep had a structural flaw, and it took her a while to see it. She'd been planning a marketing campaign. The Notion doc, the GIF spec, the hunter outreach — all of it pointed at the leaderboard. The leaderboard was the goal. The number was the win condition.

But the leaderboard is bait. It exists to get you to do the work of showing up. The work of showing up is what generates the actual return, and the actual return is not visible on the leaderboard. It's in the inbox.

On launch day, 47 people emailed Maya. Not signed up — emailed. Wrote her a real message, sometimes a paragraph, sometimes three pages. Some asked questions. Some said 'I tried to use this for X and it didn't work, here's what happened.' Some said 'I'm building something adjacent and would love to compare notes.' Two said 'I have a budget for this kind of tool, can we hop on a call.'

She replied to all 47 within four days, sitting in the same kitchen chair, with the same coffee, refusing to skip even the short ones. That correspondence — not the upvote count — turned out to be the launch.

What moved the needle, and what didn't

After the launch, after the 47 emails, after the slow realization that something good had happened that she couldn't measure on the leaderboard, Maya did the thing every founder should do but almost no one does: she wrote down what worked and what didn't. Not in a tweet thread. In a private doc, with timestamps, for herself.

What worked

1. 1.A real first comment from the founder. Not 'hi, excited to share this!' but a story. Two paragraphs about why she built it, what she got wrong twice before getting it right, and one specific question she wanted hunters to answer. The question was the part that mattered. People reply to questions. They don't reply to enthusiasm.
2. 2.Replying to every comment within an hour. This was the single highest-leverage thing she did all day. PH's ranking favors engagement, but more importantly, the people who comment are the people who are paying attention. A reply within an hour says: I am here, I am present, this is a conversation, not a billboard. Three of her paying customers cited the comment thread, not the product page, as the reason they signed up.
3. 3.An 'ask me anything' subthread halfway through the day. Around 2pm Lisbon time she posted a comment that just said 'taking questions for the next two hours — pricing, stack, why I quit my job to build this, anything.' Eleven people replied. The thread was still being read a week later.
4. 4.One clean GIF in the gallery. Not seven. One. It was 6 seconds, showed the product solving one problem cleanly, ended on a frame that made the value obvious. The other GIFs she'd prepared — feature tours, onboarding flows, an animated logo — she never uploaded. Nobody missed them.
5. 5.A specific 'who is this for' line in the tagline. Not 'the best way to X' but 'X for solo founders who are tired of Y.' This filtered hard. Fewer signups, better signups.

What was a waste

• Paid services that promise upvotes. Maya didn't use these but two friends did and reported back. The upvotes are real but they're from accounts that don't comment, don't sign up, don't email. They move the leaderboard number and nothing else, which is exactly the wrong thing to optimize for.
• Twelve scheduled tweets. She wrote them, she scheduled them, she watched them go out, they got the engagement of every other tweet on a launch day, which is to say modest. The tweets that actually drove signups were the unscheduled ones — replies to people who asked about the product, a screenshot of a particularly nice comment, a thank-you to the person who hunted her.
• The imaginary 'perfect' launch day. She'd built up the day in her head as a thing she had to perform. The reality was eleven hours of refreshing tabs and writing replies. The performance never showed up. Nobody was watching the way she thought they were.
• Over-preparing the hunter. She'd written a 600-word brief for her hunter, three GIFs of demo footage, a list of suggested taglines. The hunter used about 40 words of it. The rest was for her own anxiety, not for him.
• The 12am PST tweet timed to launch. It got six likes. Nobody on her timezone was awake. Nobody on PST was on Twitter. It was a ritual, not a tactic.

If you mapped the time spent against the outcome generated, the chart would be ugly. She'd spent maybe 70% of her three months on things that contributed less than 10% of the launch's return. The 10% — the first comment, the replies, the AMA, the one GIF — could've been prepped in a weekend.

Two weeks later

Fourteen days after launch, on a Saturday morning, Maya sat with her coffee and went back through her inbox. She'd been doing this every Saturday since she started the company, a habit she'd picked up from a founder she admired. Look at the last two weeks of email. Look for patterns.

Three of the 47 launch-day emailers had become paying customers. One of them on the annual plan, which she hadn't expected to sell to anyone for at least another quarter. Another two were in trial and looked like they'd convert. One had introduced her to a friend at a company in Berlin who wanted to talk procurement.

One of the emailers — a developer in Toronto named Sam — had started replying to her engineering blog posts within a few weeks. By month three he was on a 30-minute weekly call. By month six she'd hired him as her first employee. He's still there.

Two others, a designer in Berlin and an indie founder in Tokyo, became something she didn't have a category for at first. Not customers, not coworkers. Just people who texted her about their projects, who she texted about hers. A year later, when she launched her second product, both of them showed up unprompted. The designer made her a launch graphic. The Tokyo founder wrote the first comment on the PH page, before she'd even posted hers.

The 230 upvotes weren't the asset. They were the cover charge. The actual asset was a small group of people who'd looked at the thing she made, decided to say something about it, and meant it.

A taxonomy of indie launch platforms

PH is one room. There are others. Each does a different job, and the mistake is treating them as interchangeable. They're not. A launch is not a press release blasted across every channel. It's a sequence of arrivals, each in a different room, each requiring you to dress differently for the occasion.

• Product Hunt. The indie meetup. Best for: feedback from designers and adjacent founders, building an audience of people who care about new tools, a one-day burst of momentum. Worst for: B2B sales, enterprise traffic, anything where your buyer doesn't live on Twitter.
• Show HN. The technical proving ground. Best for: developer tools, infrastructure, anything where the underlying engineering is the story. The audience is engineers; the feedback is direct, sometimes brutal, almost always useful. You will get torn apart for hand-wavy claims. You will get a free architecture review if you're willing to listen.
• Indie Hackers. The campfire. Smaller crowd, longer attention spans. The launches that do well there are the ones with a story — revenue, struggle, a real human behind the post. Polish matters less; honesty matters more.
• Reddit, the right subreddit. Hit or miss, but when it hits, the hit is from someone who has a specific problem you solve. /r/SaaS, /r/sideproject, /r/selfhosted, /r/webdev, niche-by-niche. Lurk for a month first. Mods will sniff out a launch post written by someone who's never commented.
• BetaList. Pre-launch sign-up gathering. Quieter than it used to be, but still pulls in 100-300 emails from people who actually want to try beta software. Good for filling a waitlist.
• dev.to / Hashnode. Long-form launch posts disguised as tutorials. The launch is implicit: you wrote a piece about how you built X, and X is the product. The audience is developers reading on lunch breaks.
• X launch posts. Fast, reach-dependent, no archive. The play is a clean thread, a demo video that autoplays well, and a network of friends willing to quote-tweet the first hour. Without the network it's a shout into the void.
• The niche Slack or Discord. Smallest audience, highest conversion. If you ship a tool for, say, freelance video editors and you're already a member of three communities of freelance video editors, posting there will outperform PH by an order of magnitude. The catch: you have to actually be a member. Drive-by promotion gets you banned and remembered.

The right launch isn't picking one of these. It's picking three or four, in sequence, over a couple of months, each tuned to its room. Maya's first launch was PH and a soft X thread. Her second was a full rotation.

The second launch is the real launch

Fifteen months after the PH launch, Maya shipped product number two. By then she had Sam in Toronto, the designer in Berlin who'd become a friend, the Tokyo founder, and about 1,400 people on a newsletter she'd started six weeks after the first launch — built almost entirely from the 47 emailers and the people they introduced her to.

She approached the second launch like someone who knew what the first one had been for. No three-month prep. No Notion sub-pages. She wrote one good landing page. She wrote one good email to her list, sent the night before. She picked three platforms — PH again, Show HN, and one specific subreddit — and she staggered them over eight days, not eight hours. She didn't schedule any tweets. She did reply to every comment, every email, every DM.

The second launch finished #6 on PH. Better than the first, but not the point. The point was that on day one of the launch, 180 people emailed her. By the end of the week, the number was over 400. Three weeks in, she'd added forty paying customers. Six weeks in, she'd raised a small round from one of the people who'd commented on her launch page.

The principle: your first launch builds the audience for your second launch. Your second launch builds the audience for your third. Anyone telling you that the first launch is the launch is selling you something. The first launch is the introduction. The second one is when you stand up and say what you actually came to say.

A small detail

Two months after the first launch, Maya took down the coffee-stained Post-it. She'd noticed it one morning, peeling at the corner, and realized she'd been ignoring it for weeks. She balled it up and dropped it in the kitchen bin. Then she sat down at her laptop and wrote a thank-you email to the hunter who'd posted her — the third one she'd written him. He replied the same day. They've been friends since.

If you're prepping a launch — Product Hunt, Show HN, Indie Hackers, anywhere — the work that matters is the work that produces conversations you'll still be having in a year. The leaderboard is the cover charge. The badge is a souvenir. The people who comment are the room.

A short list of where to show up, organized by what each room actually does, is at /dir/launch-platforms. Pick three. Sequence them over a month. Reply to every comment within an hour. Count the emails, not the upvotes. Be the kind of founder someone would want to text a year from now.

Maya's window still opens onto the same tiled rooftop. The slice of the river is still there if she leans. She has a second Post-it now, in the same corner. It says: 'reply within an hour.'