Research → briefing: the launch playbook

2 months ago

Yesterday I spent a session reading primary sources on one question. How does a solo founder launch a developer tool. What you are watching is that session's findings, turned into something you can share. The findings first. Then the one line that made this.

Ask

Ask about this presentation

Answers are generated from this presentation.

Chapters

  1. 0:00Research that talksgets watched.
  2. 0:16Launch againand again.
  3. 0:41Eight rungs,each cheap.
  4. 1:05Show HN hashouse rules.
  5. 1:30Three ways tokill it yourself.
  6. 1:56Take the backlink,not the day.
  7. 2:32Slide 7
  8. 2:56Documents getskimmed.
Show transcript

Research that talksgets watched.

Workflow guides · 03

Yesterday's research session on launching a dev tool, turned into the briefing you are watching.

01

Yesterday I spent a session reading primary sources on one question. How does a solo founder launch a developer tool. What you are watching is that session's findings, turned into something you can share. The findings first. Then the one line that made this.

Launch againand again.

The doctrine

The canonical essay is by YC partner Kat Mañalac

"How to Launch (Again and Again)" — commonly misattributed to Michael Seibel; Seibel presents the adjacent Startup School material.

Source

ycombinator.com/library/6i-how-to-launch-again-and-again

. Launching is not an event you polish toward. It is something you do continually.

"Launch and iterate, launch and iterate, until you have a core of users who really love you."

02

The central finding comes from Y Combinator's own library. The canonical essay is by partner Kat Manalac, and its title is the whole doctrine. Launch again and again. Launching is not an event you polish toward for months. It is something you do continually, to refine the pitch and find the channel where your real users live. Launch and iterate, until you have a core of users who really love you.

Eight rungs,each cheap.

The ladder

YC companies walk a ladder of launches, and every release hits the buttons again.

1

Silent — a page, a name, a way to reach you

2

Friends and family

3

Strangers — the product in unfiltered hands

4

Online communities — one channel at a time

5

Waitlist and referral loops

6

Niche press, last and optional

7

Every new feature: launch again

03

The essay lays out the ladder these companies climb. A silent launch, only a page and a name. Friends and family next. Then strangers, the product in unfiltered hands. Then online communities, one channel at a time. A waitlist if scarcity helps you. Press comes last, and stays optional. And every meaningful release climbs the ladder again. None of these rungs costs much, which is the point.

Show HN hashouse rules.

The anchor channel

For a developer tool, this is the room that matters. The rules are published, and most launches break them.

Something people can play with. No signup walls. A runnable local tool is the ideal object.

A plain title. Description, not marketing. No adjectives doing sales work.

A founder first comment. What it does, the problem, the backstory, how it works, one honest limitation.

04

For a developer tool the anchor channel is Show HN, and its rules are published. It must be something people can play with, without a signup. The title is plain description. No adjectives doing sales work. And the founder writes the first comment. What it does, in the first sentence. The problem. The backstory. How it works, with real technical detail. And one honest limitation, offered before anyone asks.

Three ways tokill it yourself.

The failure modes

All three are in the site's own guidelines, and all three are common.

Asking friends to upvote. Readers sniff out booster comments, and the anti abuse software drops suspicious votes.

Marketing speak in the title or the thread.

Stacking channels on the same day. HN's advice page says plainly: do not coordinate your launch with press.

05

The same pages spell out what kills a launch, and all three failures are self inflicted. Asking friends to upvote. Readers have a nose for booster comments, and the anti abuse software silently drops suspicious votes. Marketing speak. And stacking channels on the same day. The site's own advice page says do not coordinate your launch with press. One channel per day, so each gets its own push and you can tell where the traffic came from.

Take the backlink,not the day.

Second channel, and the clock
PRODUCT HUNT, 2026

Founders who ran both channels report a fraction of the traffic

Sept 2025 HN thread "Product Hunt is dead": ~50 visitors for a #7 finish in 2024 vs 250 for #14 in 2022; Show HN cited at 3–10× the traffic.

Source

news.ycombinator.com/item?id=45362569

and widely gamed rankings. Still worth a quiet self hunted launch, on a different day.

TIMING

Tuesday morning,
then stay all day.

Weekday mornings, Eastern time, Tuesday among the most active. But the first hour of genuine engagement outweighs the clock.

06

Two smaller findings. Product Hunt still exists, and the community verdict on it is blunt. Traffic has collapsed and the rankings are widely gamed. Founders who ran both channels saw several times the visitors from Show HN. It is still worth a quiet secondary launch on a different day, for the backlink and the badge. And timing is the smallest lever. A weekday morning, Eastern time, Tuesday among the most active days. Every analysis agrees the first hour of genuine engagement matters more than the clock. Post in the morning, then stay in the thread and answer as a builder.

Slide 7

The workflow
1

Run research as an agent session, against primary sources.

2

Findings land in a markdown file in the repository, with the source links.

3

Then ask for the briefing. The sources travel with it.

THE SENTENCE THAT MADE THIS
Turn this research into a briefing I can share.

Pause on any slide and hover an underlined claim to pull its source. That is the research file, riding along.

07

The recipe. Run the research as a session. The agent reads the primary sources and writes the findings into a file in your repository, links included. Then one line. Turn this research into a briefing I can share. The sources travel with it. Pause this presentation on any slide and hover an underlined claim, and the source comes up. That is the research file, riding along with the briefing.

Documents getskimmed.

Workflow guides · 03

Research that talks gets watched. End the session with a link.

bisque.cloud

08

Research you share as a document gets skimmed. Research that talks gets watched, and the sources ride along for anyone who wants to check. End the session with a link.