How We Got #2 on Product Hunt: Open Wearables Launch Recap

Introduction

On April 29, 2026, we launched Open Wearables on Product Hunt. By the end of the day we were sitting at #2 Product of the Day with 600+ upvotes, 308 comments, and a demo calendar that had no open slots left.

The result did not come from a single good post or a last-minute push. It came from three months of preparation: warming accounts, building lists, drafting outreach sequences, splitting the day into two activation windows across time zones, and running coordinated outreach across email, CRM, LinkedIn, PH communities, and Slack communities on the day itself.

This post is a full breakdown of what we did, what the data showed, and what we would approach differently. If you are planning a Product Hunt launch for a developer tool, open source project, or healthtech product, there is specific and transferable detail here. We are sharing it because the best launch resources we found before our own were written by teams who documented the whole picture, not just the headline number.

The Product

Open Wearables is an open-source platform for health intelligence. It handles wearable data ingestion across devices and providers, computes health scores using open algorithms, and exposes an MCP server that gives LLMs direct access to health signals. The platform is self-hosted, MIT-licensed, and charges zero per-user fees at any scale.

For context on why this matters: the alternative for most healthtech startups is a proprietary wearable API that costs $499/month at the low end and scales to $5,000-20,000/month at 10,000 users. Open Wearables replaces that layer entirely. We have covered the real cost of wearables integration in 2025 in detail elsewhere, but the short version is: the economics do not work for most of the people trying to build in this space.

This was our first Product Hunt launch. We had been building in public for several months before it, shipping releases and documenting progress, but this was the first time we put the product in front of the full PH audience.

How We Prepared: 3 Months Before Launch Day

Product Hunt weights votes by account quality. An upvote from a fresh account with no history contributes significantly less than one from an account that has been active for months. This is one of the least-discussed but most important mechanics of the platform.

We started warming accounts three months before the launch date. That meant the hunter account, maker accounts for the core team, and Momentum team members who would be supporting the launch all had weeks of consistent activity: visiting the platform daily, upvoting products, leaving comments. By launch day those accounts had real weight behind them.

One thing worth doing before launch day: compile a list of people in your network who have active PH accounts and are willing to support you. Not people who will create an account on launch day, those votes carry almost no weight. People with accounts that already have history and activity. Identify them in advance, confirm they are willing to help, and brief them on the timing. A list of 20-30 genuinely active accounts is worth more than 200 people who sign up on the day.

Alongside account warming, we built the outreach infrastructure:

• Email sequences: Two separate lists prepared in advance: the Open Wearables subscriber list and the Momentum marketing list. Each got a tailored message written for that specific audience, not a copy-paste.
• CRM outreach: Every relevant contact in the Momentum sales CRM received a personal outreach message. Past clients, active prospects, warm contacts. The goal was to activate people who already had a relationship with Momentum or had seen the product, not cold outreach.
• LinkedIn network: Personal outreach to network contacts asking them to check out the launch. Not a mass message, segmented by relationship and framed accordingly.
• PH communities: Outreach within relevant Product Hunt communities before and on launch day.
• Slack communities: Relevant developer and healthtech Slack communities were identified and prepared as outreach targets for launch day.

Get the Featured Badge Before Launch Day

Product Hunt moderators manually select products to feature. Featured products appear in the PH newsletter, which goes to hundreds of thousands of subscribers, and get significantly more organic visibility throughout the day. The difference in organic upvotes between a featured and non-featured product is substantial.

Moderators review submissions in advance. To be considered for the Featured badge, you need to submit your product before launch day, not at 12:00am when the day starts. More importantly, your submission needs to be complete when you submit it: gallery images, a demo video, a strong first comment, and a polished description. Moderators are evaluating whether the product is ready to be featured. A placeholder submission or missing assets will not get selected.

We had all assets ready before submission: gallery graphics, a working demo, and the first comment drafted. Getting the Featured badge was part of why the majority of our upvotes came organically from PH itself rather than from our own network.

Two Time Zone Strategy

Product Hunt operates on Pacific Time. The ranking resets at midnight PT, and the first few hours of the day carry disproportionate weight in establishing where a product will land. A European product launching at midnight PT means 9am CET, which is the start of the European workday.

We split the activation into two windows deliberately:

European window (morning CET): Email sequences sent, CRM outreach started, LinkedIn posts live, PH community outreach active. The goal was to build early momentum during European working hours and hit the top of the rankings before the US audience came online.

US window (afternoon CET / morning PT): Second wave of outreach targeting US-based contacts, Slack communities with US-heavy audiences, and a second round of social posts timed for US engagement. Live update posts published as the US day started.

The two-window approach meant we had continuous activation across the full launch day rather than a single spike that fades.

Product Hunt Results

Final position: #2 Product of the Day
Upvotes: 600+
Comments: 308
Award: #2 Product of the Day (official badge)

The 308 comments are the number worth pausing on. Most products on Product Hunt receive 10-30 comments. Products that finish in the top 5 might reach 50-100. 308 is the kind of volume you see when people are not just clicking to support a launch but have actual questions, use cases, and feedback to share.

On the upvote breakdown: roughly 277 came from our own outreach across LinkedIn and X combined. The rest, the majority, came organically from Product Hunt itself. That is the most important number in the whole recap. A well-prepared launch with a Featured badge gets in front of PH own audience, and that audience converts.

By the end of the day we also had 1,400 new followers on the Open Wearables Product Hunt profile and +100 GitHub stars.

Website Traffic

Traffic to openwearables.io jumped 8x on launch day compared to a typical day. Most of that traffic landed on the homepage, which is standard for a launch. The remaining traffic went to technical pages, reflecting that the people arriving already had context for what they were looking at.

The 8x spike is significant but the more important signal is what happened with the demo calendar. Organic traffic from launches tends to be shallow: people look, do not convert, and move on. A full calendar of booked demo calls tells you the traffic had intent behind it.

Channel Breakdown: Where the Votes Came From

LinkedIn: 237 Vote Conversions

LinkedIn was the dominant conversion channel by a significant margin. 237 view-to-vote conversions came from LinkedIn, compared to 40 from X. That is a 6:1 ratio.

For anyone building a developer tool, health platform, or B2B product, this number is worth internalizing. LinkedIn audience for healthtech and developer tooling is large, engaged, and has purchasing power. The Product Hunt audience that converts from LinkedIn tends to also leave comments and follow up with questions. The quality of the engagement from LinkedIn was noticeably higher than from other channels.

We covered the wearables integration audience and where they spend their time in Why Mobile Health Apps Struggle With Wearable Integrations. The LinkedIn dominance in vote conversions is consistent with what we observe there: the developers and product leads building health apps are on LinkedIn, not primarily on X.

X / Twitter: 40 Vote Conversions

X drove 40 conversions total: 27 view-to-vote and 13 link-to-vote. Our Open Wearables X account finished launch day with 1,100 impressions, up 595% from the previous week, and 36 likes. The Momentum account added 289 impressions.

The numbers were modest. Our profiles on X are small, and that ceiling was real on launch day. The format that performed best was the live update post, which got 2.5x more impressions than the standard announcement post. That pattern matches what we have seen with X content more broadly: real-time updates and in-progress content outperform polished announcements.

X has high upside when content catches. We have seen what a single post going wide does to traffic: it is a different scale entirely. The gap in this launch reflects where our profiles are, not what the channel is capable of. Building the X audience consistently is on the roadmap.

Product Hunt Organic: The Rest

LinkedIn and X combined accounted for roughly 277 conversions. The remaining upvotes, the majority of the total, came organically from Product Hunt itself. Visitors browsing the platform on launch day, the PH newsletter audience, and people discovering the product through the rankings. That organic share is what the Featured badge unlocks. Without it, a launch lives or dies by the size of your own network. With it, PH does a meaningful part of the work for you.

What Worked on Social Media

Storytelling Outperformed Announcements

The highest-performing LinkedIn post from launch day started with "one comment stopped us" and ended with a cliffhanger that linked to a longer article. It had a 7% CTR on 100 impressions, and the linked article drove 258 pageviews, well above the impression count. That means the post reached people beyond the follower base.

A standard launch announcement on the Momentum LinkedIn page got 4.28% CTR on 327 impressions. That is a solid number, but the storytelling post outperformed it on CTR while also generating organic distribution the announcement did not.

The mechanism is straightforward: people share content that has narrative tension. A post that says "we launched" gives a reader nothing to do with it. A post that says "here is what we found" or "here is what stopped us" gives a reader something to engage with and pass on.

Live Updates Drove More Engagement Than Static Posts

The best-performing Open Wearables LinkedIn post was a live update published six hours into the launch day: 1,732 impressions, 121 clicks, 6.99% CTR. That is more than twice the LinkedIn average click-through rate for organic posts.

On X, the live update post got 2.5x more impressions than the launch announcement. The pattern held across both platforms: people engage with what is unfolding, not what already happened.

For a future launch, we would schedule at least two live update posts for different points during the day, in addition to the opening announcement.

LinkedIn Is the Right Primary Channel for This Audience

For a product targeting developers and healthtech founders, LinkedIn is where the conversion happens. Not because X does not matter, but because the people who vote, comment, and book demos are primarily on LinkedIn for professional content. The 6:1 ratio in vote conversions was not a surprise in hindsight, but we underweighted LinkedIn in our pre-launch prep relative to what the results justified.

The Comments

308 comments over a 24-hour period is operationally demanding. We had someone actively monitoring and responding throughout the day. The questions fell into a few categories:

• Provider support: which wearables are integrated, what is on the roadmap
• Self-hosting specifics: infrastructure requirements, Railway vs bare metal, Docker Compose setup
• API design: data models, normalization approach, rate limits
• Use cases: how teams were already thinking about using it

The use case questions were the most valuable. Developers described their exact stack and what they were trying to build. Several of those conversations turned into demo bookings.

For anyone planning a launch: assign a dedicated person to comments for the full day. Responding within 5-10 minutes to early comments matters. PH ranking algorithm takes engagement into account, and a comment thread that gets responses tends to attract more comments. We replied to every comment we could.

What We Would Do Differently

Start X account building at least six months out. The channel has high potential but requires an existing audience to activate. We saw the ceiling clearly on launch day. Consistent posting for six months before a launch would change those numbers in a meaningful way.

Prepare more live update content, especially for the US window. The formats that performed best were live and in-progress. We had them, but we could have had more touchpoints during the afternoon, when PH traffic peaks and the US audience is most active.

Segment the CRM outreach more aggressively. Outreach to past clients and warm contacts worked well. With more time, we would create finer segmentation within the CRM: by industry, by how recently they engaged, by whether they had already seen the product. The more personal the message, the higher the conversion.

Run a dry-run of the two-zone coordination the week before. On launch day, coordinating outreach across email, CRM, LinkedIn, PH communities, and Slack across two time zones simultaneously is operationally demanding. A dry-run of the sequence, timing, and team roles a week before would remove friction on the day itself.

Build the active-accounts list earlier. We identified people in our network with active PH accounts, but doing this earlier would have given us more time to brief them properly and confirm timing. Aim to have 20-30 confirmed active accounts lined up at least two weeks before launch.

Key Takeaways for Your Launch

If you are planning a Product Hunt launch for a developer or healthtech product, here is what the data and the preparation support:

• Start warming PH accounts 3 months before launch, not 1 week. Account quality determines vote weight.
• Compile a list of people in your network with active PH accounts willing to support you. 20-30 real accounts beat 200 day-of signups.
• Submit early and submit complete. Moderators pick Featured products manually. Have gallery images, demo, and first comment ready before you hit submit.
• Build all outreach copy before launch day. Email sequences, CRM messages, LinkedIn posts, community outreach. When the day starts, you execute, you do not write.
• Split the day into two time zones. European morning activation builds early ranking momentum. US afternoon activation sustains it through the PH peak hours.
• Cover all channels: email lists, full CRM, personal LinkedIn network, PH communities, Slack communities. Each channel reaches a different slice of your network.
• The majority of upvotes on a well-prepared launch come organically from PH itself. The Featured badge is what unlocks that.
• LinkedIn is your conversion channel if your audience is in B2B or healthtech. 237 conversions vs 40 from X. Optimize for LinkedIn first.
• Storytelling posts outperform announcements. The CTR gap between a cliffhanger post and a launch announcement was 7% vs 4%.
• Live updates outperform static posts on both platforms. Plan at least two during the day.
• A full demo calendar is a harder signal than upvotes. Design your post-launch flow to capture high-intent visitors before they leave.
• X requires an existing audience. If you do not have one, start building it now.

Open Wearables is open source and available on GitHub. If you are building a health product that needs to handle wearable data, the wearables integration service page covers how Momentum can help you move faster.