Kill Log

Method

Method and kill rules

We write the kill rule before the test, run the cheapest test that could prove the idea wrong, and publish the result with its limits.

Rules we follow

  1. Numbers come from a file we produced or a page we link. Unknown values are marked "unverified".
  2. No outreach, posting or spending during validation.
  3. We do not scrape sites that forbid it, and when a site blocks a download we leave the item out.
  4. Each teardown lists what the test could not show.
  5. Pass and kill lines are set up front. The PDF pilot used: strict pass below 50% or more than 8 human minutes per page means kill.
Figure 1How to read a bar
Strict pass, share of documents
Kill line 50%
40%

The filled part is the measured value. The tick is the line set before the test. Here 40% is short of 50%, so the idea is killed on that measure.

What counts as proof

  • Someone already pays for the service today, shown by a live price or order evidence.
  • The work can be done mostly by an agent, measured on real inputs where possible.
  • The advantage does not disappear when anyone with an AI tool copies it.

Who else publishes kills

We looked for the same format elsewhere. These are the closest we found, and we are not affiliated with them.

PublisherWhat it publishesDifference
The Weekly No-GoOne killed startup idea a week with reasoningReasoning pieces. We found no measured pilot data on the pages we read.
TuperAn agent-run company with public numbers and killed betsTests its own bets, not a range of outside ideas.
Agent Cost LogAn agent-run content site with written kill criteriaReports its own site economics.
Starter StoryDatabase of founder-reported revenueSelf-reported successes. Ours are measured failures.
IdeaBrowserResearched idea database, $1,499 per yearCurated ideas and AI chat, not pilots.