2 builders who never spoke to each other
Launch on the day the need turns sharp
Two makers timed a launch to an outside event rather than to their own roadmap. One submitted his tool the day the platform it plugged into changed its signup flow and broke everyone's workflow; the other saw a customer use his product in an unexpected way and was on the platform within a month rather than rebuilding first. At that moment the listing reads as the answer to a question people are already asking.
The method
- 01
Time a launch to the day the platform you depend on changes behaviour, since the need is at its sharpest right then.
- 02
When one unexpected use of your product clicks, get it in front of Product Hunt within weeks instead of rebuilding first.
What it returned
On the day MailChimp switched to a two-stage confirmation flow, Zue submitted Chimp List Helper to Product Hunt; it got featured and started gaining traction
A client used Loom's user-testing tool to record himself summarising test results. Loom launched on Product Hunt a month later and several thousand people had installed the extension before that day ended.
Sources
- Week 33 RetrospectiveCory Zue · coryzue.com · Comments · 2017-11-06
- How the most successful B2B startups came up with their original ideaShahed Khan · lennysnewsletter.com · Path 3: Present pull · 2023-08-08
the second source
Three plays a week, for the phase you are in
No roundup of links, no news. Three tactics more than one builder arrived at separately, with the numbers each one returned and the disagreements left in.
More in product hunt
- Count the second wave, not the referral clicks3 unconnected · contested
- Run it even when you will not chart3 unconnected
- Launch the small or unpolished thing anyway2 unconnected
- Launch it again once something real has changed2 unconnected
- Put the same release on every board that day2 unconnected
- Convert the day into email subscribers2 unconnected