Choose what to get done
Press release with every element a reporter needs
A complete, structurally-checked release: a headline that names your company, a distinct subhead, a dateline matching your city and date, a lead of at least 25 words, your requested number of attributed quotes, a number or statistic in the body, a boilerplate that names your company, your media contact email, and your media-kit link, all within the word cap.
Price fences that separate willingness-to-pay segments
I get a set of price fences that keep my higher and lower willingness-to-pay segments in their own tiers, so a low-value buyer cannot cheaply access the high-value price.
Price-increase message with a fairness rationale
I get a price-increase message that carries a genuine rationale, fair notice, and a disclosed magnitude, so customers read it as fair rather than opportunistic.
Privacy-by-design seven-principles AI register
A JSON register with one entry per PbD principle passes validation: all seven canonical principles are present with correct slugs, each has an implementation note of minimum length, a status from the allowed enum, an assigned owner, and no principle is duplicated.
Prize-frame flip script
A prize-frame closing script containing every required prize element, at least your minimum number of target-directed qualifying questions, and a closing line, screened against a fixed neediness-phrase list plus any phrases you add.
Problem definition document
A problem definition document with the market, buyer roles, and per-problem definition, metrics, prior solutions, buying authority, and a 1-10 severity.
Product requirements document (PRD)
A complete PRD: the named sections, a quantified business context, a measurable success metric, and acceptance criteria with a clear out-of-scope fence.
Protective-provisions and board-approval consent register
A structured JSON register enumerating each protected corporate action, the approving class, and the consent threshold, covering the required protective-provision items with valid thresholds.
Release readiness gate checklist
Categorized, criterion-bearing release gates with a consistent blocking verdict, marrying governance with automation instead of a change-board bottleneck.
Requirements traceability matrix
A matrix linking every requirement to its tests (and back), with computed orphans and a coverage percentage that clears your bar.
Revenue Zone understandings, beliefs, and readiness gates
I get a structured definition of my Revenue Zone for one product: exactly three understandings and three beliefs (each mapped to demand or trust) plus the budget and impending-event readiness questions, so my team and partners share one bar for 'ready to buy'.
Romance-the-problem stakes anchor
I get a structured stakes anchor with exactly one magnitude statistic (value, unit, claim, and a cited source unless I turn sourcing off), a hook of a type I allow, and a consequence-if-unsolved line that meets my minimum word count, so I can romance the problem without drowning the audience in numbers.