Build · Create · Writing & Content

Build a Why-Now three-forces trendcasting register

A three-forces 'Why now?' register with one economic, one social, and one technology force, each impact-tagged, plus a window statement.

You receive: A JSON object { ideaName, forces: [ { forceType, change, impactOnCostOrDemand } x3 ], marketWindowStatement }.

Part of Pitch Investors

What's verified: STUD verifies the register has exactly one economic, one social, and one technology force, each with a sufficiently long distinct change and a cost/demand-tagged impact, plus a market-window statement. STUD does NOT verify the forces are real, correctly classified about the world, or that the window is genuinely open.

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": [],
 "checkNames": [
  "format_parses",
  "forces_is_list",
  "three_forces",
  "force_type_enum",
  "change_min",
  "impact_present",
  "window_marker",
  "distinct_changes"
 ],
 "constants": {},
 "deliverableLabel": "why_now_three_forces_register",
 "documentKeys": [
  "change",
  "forceType",
  "forces",
  "impactOnCostOrDemand",
  "marketWindowStatement"
 ],
 "enumLiterals": [
  [
   "cost",
   "price",
   "demand",
   "customers",
   "margin",
   "revenue",
   "%",
   "percent",
   "$"
  ],
  [
   "economic",
   "social",
   "technology"
  ],
  [
   "now",
   "window",
   "recently",
   "just",
   "emerging",
   "opened",
   "this year"
  ]
 ],
 "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.