Choose what to get done
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 feature ranking (collaborative weighted scorecard)
A product team prioritizing a roadmap gets each feature's weighted value, cost normalized to the most expensive feature, absolute value, and a deterministic rank, computed exactly per the CWS formula.
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.
Quarterly pricing-analytics metrics register
I get a quarterly pricing report object carrying all five metrics plus the eight-dimension segmentation, where ASP/median/discount-% recompute correctly from the deal rows I supplied.
Raise amount and implied valuation from inflection point
A single headline raise number, the implied post-money valuation range, the investor ownership range it implies, and a flag for whether the ask sits inside the track-record-appropriate band, so the founder can answer 'how much are you raising?' with one defensible figure.
Ranked ecosystem-qualified lead list
A big undifferentiated prospect list is run against your partner ecosystem data and returned as a tight, ranked shortlist of ecosystem-qualified leads, each tagged with which partner touches the account, the partner segment, the partner owner, and an overlap-based priority score.
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.
Runway-to-profitability monthly projection
A structured monthly financial projection (a table of months with cash, revenue, expenses, net) that is arithmetically self-consistent, covers the required horizon, and explicitly marks the profitability crossover month, so the team and investors see the trajectory rather than a single number.