Plan a developer launch (Show HN, Reddit, Product Hunt) that earns goodwill instead of a flaming. Use when the user is sitting on a launch out of fear, wants to "go viral," or is about to post a press-release-style announcement to a developer community.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Developer communities reward the honest, technical, slightly humble builder and punish the marketer instantly. A Show HN is not an announcement. It's "I built this thing, here's how it works and what's still rough."
Use this when: you're scared to launch, you're hoping to "go viral," or you're about to drop marketing copy into a room that eats marketing copy for breakfast.
The bar is usefulness + honesty, not polish. Developers will test your claims and read your code. Show up as a real engineer sharing real work, be present to answer everything, and never, ever fake it. One genuine launch beats ten hype posts.
Framework adapted from Flo Merian's awesome-product-hunt.
A launch is one prepared moment across the channels your ICP actually uses (from first-50-users): HN, your own network, and the relevant communities, all on the same day, each tailored to the room. It is not the same copy blasted five places.
Can a stranger get to first value in < 1 hour from docs alone (the weekend test)?
├─ NO → don't launch yet. A flood of users who bounce burns the channel and the goodwill.
└─ YES → is your Show HN first-comment written (why/how/limits/try)?
├─ NO → write it first; it matters more than the product page.
└─ YES → launch on a Tue-Thu morning US time, then clear your calendar to reply.
know-if-its-working). If not, delay.Built from real dev-tool GTM experience, with frameworks from Adam Frankl (The Developer-Facing Startup) and Jakub Czakon (markepear.dev). A launch you only get one shot at is worth a human sanity-check first. Reach out to me on LinkedIn.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Position an AI product when everyone claims AI and skeptics call it "just a wrapper." Find the real wedge (data, workflow, trust, domain), make reliability the differentiator, answer "won't the big labs just build this," and stop leading with "AI-powered." Use when your AI or dev tool blends into a sea of similar demos, buyers doubt the accuracy, or you can't say why you win when the model is a commodity.
日本語の概要は準備中です。原文の説明を表示しています。
Get the first 50 real users through channels the user's ICP already uses. Use when the product shipped and nobody came, the user is "posting more" with no result, or is reaching for paid ads before product-market fit.
日本語の概要は準備中です。原文の説明を表示しています。
Build authority by teaching the problem space, not announcing features. Use when the user finds "marketing" distasteful and does none, publishes only product updates, or wants a sustainable content and GitHub-README strategy that developers actually respect.
日本語の概要は準備中です。原文の説明を表示しています。
Coach the user through actually selling: finding the champion and the buyer, running the first sales conversations, demoing their use case, handling "let me think about it," and closing the first paying customers yourself. Use when developers love it but nobody pays, you've never sold anything and freeze on the conversation, or deals keep stalling on "we'll think about it."
日本語の概要は準備中です。原文の説明を表示しています。
Turn hand-made first-50 traction into self-reinforcing acquisition loops, so the next 5,000 users come from usage, not founder hours. Use when growth stalls the moment the user stops pushing, every signup traces back to a DM or one launch spike, or they're reaching for "more channels" when the real gap is that using the product creates no new users.
日本語の概要は準備中です。原文の説明を表示しています。
Measure GTM with the metrics that matter (net developer retention, DREAM funnel) instead of vanity numbers. Use when the user has dashboards full of stars and pageviews but can't tell if go-to-market is working, or is optimizing acquisition over a leaky bucket.
日本語の概要は準備中です。原文の説明を表示しています。