clawhub install product-hunt-playbook

• 24-hour battle plan with hour-by-hour tactics for launch day
• Ranking algorithm deep-dive — weighted factors decoded (it's not just upvotes)
• Post-launch 72h momentum plan to convert PH traffic into retained users

🌍 Language / 语言: 中文 | English | 日本語 | 한국어

30x Daily #1 | 3x Weekly #1 | 1x Monthly #1

• 📅 24-hour battle plan — hour-by-hour tactics for launch day
• 🎯 Ranking algorithm insights — how PH ranking actually works
• 👥 Community mobilization — activate your network without violating rules
• 💬 Maker comments strategy — engaging with voters effectively
• 📊 Post-launch momentum — converting PH traffic to users

• Complete hour-by-hour timeline
• Hunter selection framework
• Community mobilization templates
• Post-launch conversion playbook

1. Watch support quality and rate, not just the total. Historical launches were reviewed in roughly two-hour windows; abrupt bursts and low-context accounts were more likely to be removed. Treat ~100 upvotes/hour as an operational warning line, not an algorithm guarantee.
2. If the count drops, pause amplification and audit sources. Do not compensate with another blast.
3. Ask only real users and existing community members to visit voluntarily and leave an authentic comment. Never buy accounts or votes, coordinate vote exchanges, conceal identity/network origin, or instruct supporters to evade platform controls.

• Do not infer a universal spend-to-vote rate. Historical outcomes varied by audience fit, account quality, assets, timing and platform review.
• With a small budget, redirect effort: the field notes found that roughly ten relevant X KOC collaborations often beat a PH-only push on registrations. Historical directional benchmarks were PH exposure→upvote around 1% and Reddit OSS exposure→star around 5–8%; validate against your own cohort before budgeting.
• One anonymized field case (an AI Agent product, 2025-12): a 500K-visit launch day engineered across Twitter/Reddit/YouTube/groups produced ~800 signups at $6.25 CAC. Traffic ≠ conversion — plan the funnel, not just the spike.
• AFFiNE Apple Notes case (2024-02 launch): a three-person operations team coordinated 30 Twitter/LinkedIn KOLs and 24-hour multi-channel distribution. The project note reports 700K+ impressions and 1,000+ upvotes in 24 hours, monthly #8 within 96 hours, plus daily #2 and weekly #2. Treat these as self-reported historical figures—not a vote-per-KOL benchmark or causal guarantee.

1. T−21 to T−14: make the maker profile credible through normal participation; finalize positioning and audience fit.
2. T−14 to T−7: create Coming Soon, select a hunter only if their audience/feature access helps, and review every asset yourself. A hunter is not a source of votes.
3. T−7 to T−1: observe recent competition for 1–3 weeks; prepare the maker comment, FAQ, demo, community destination and per-channel UTMs.
4. Launch day: publish the first maker comment with the offer and community destination; answer questions; monitor source-level visits, activations and suspicious spikes every two hours.
5. T+1 to T+7: move B2C leads into Discord/forum and B2B leads into Slack/community or a qualified demo flow. Report visits → signup → activation → retained/paid, not badge alone.

references/iris-field-notes.md

• gingiris-launch — Full GTM playbook
• gingiris-opensource — OSS marketing
• gingiris-b2b-growth — B2B SaaS growth

• 🐦 Twitter: @WeiYipei — Daily growth tactics
• 💬 Consulting: @Iris_carrot on Telegram
• 🛒 Premium (templates + case studies): Get on Gumroad
• 📦 Full Bundle ($249): All 5 Playbooks
• 📚 40+ Free Playbooks: gingiris.tools/skills