Build · Create · Writing & Content

Build a Nemesis-and-Hero Story Register

I get a structured register naming my nemesis, listing the enemy's pain points, and pairing each with a hero resolution from my product, so the audience roots for my product to arrive and save the day.

You receive: A JSON object {nemesisName, nemesisCategory, productAsHero, painResolutionPairs:[{enemyPain, heroResolution}]} with a minimum number of paired rows.

Part of Pitch Investors

What's verified: STUD verifies the register names a nemesis and a hero product, lists at least N distinct enemy pains, and pairs each with a non-empty hero resolution. STUD does NOT judge whether the nemesis is the right enemy, whether the resolutions are real product capabilities, or whether the framing will make audiences root for the product.

Opens soon

Cost20 credits

AcceptanceAutomated check against your inputs

ProtectionHeld until verified delivery

This objective is verified and ready. It opens soon, once sign-in and payments are live.

Deliverable interface

The exact vocabulary the automated check enforces: keys, tokens, entry points, and worked examples. Generated from the verification source.

{
 "buyerParamKeys": [
  "nemesisName",
  "productAsHero",
  "requireDistinctPains"
 ],
 "checkNames": [
  "format_parses",
  "nemesis_set",
  "category_present",
  "pairs_count",
  "pairs_complete",
  "resolution_starts_with_token",
  "distinct_pains"
 ],
 "constants": {},
 "deliverableLabel": "nemesis_and_hero_register",
 "documentKeys": [
  "enemyPain",
  "heroResolution",
  "nemesisCategory",
  "nemesisName",
  "painResolutionPairs",
  "productAsHero"
 ],
 "enumLiterals": [
  [
   "true",
   "yes",
   "1",
   "on"
  ]
 ],
 "submission": "a JSON document (submitted as a string), validated as data; every check below must pass",
 "tier": "doc-validator"
}

Get early access to STUD the day it goes live.