Choose what to get done
Love-vs-like product diagnostic instrument
A measurement instrument that tells love from like across five signals (repeat use, fanatical users, the would-miss test, organic referral, willingness to pay), each with a metric, a numeric threshold, and a data source.
Maintainability index per module
The Maintainability Index (raw and 0-100 normalized) per module from Halstead volume, cyclomatic complexity, and lines of code, with a maintainability band.
Map a price waterfall from list to pocket price and flag leakage
I get a price waterfall that ties my pocket price back to my list price through named, quantified leaks, so I can see exactly where realized revenue is lost.
Map product features to MECE use-case modules with per-segment value
I get a modular packaging map where features are partitioned into non-overlapping use-case modules, no feature is left unassigned, and each module carries a t-shirt value per segment plus a base/add-on flag.
Market sizing (TAM / SAM / SOM) with the adequacy check
TAM grossed up from a partial-coverage database count, SAM and SOM by your fractions, and a check that SOM clears 2x your revenue objective.
Model router that sends each query to the right LLM
A routing function that dispatches each query to the right model by its type, normalizing case and falling back to a default for any unlisted type.
Multi-stakeholder value proposition canvases
A multi-stakeholder VPC set with exactly one canvas per role you need to win, each meeting your jobs and pains minimums with at least one gain, and no two canvases sharing an identical profile, ready for a complex B2B sale.
MVP and the test that proves it
The smallest feature set that tests your riskiest assumption (built for your first few users), an explicit cut list, and a single pass/fail test card with a numeric threshold.
Net Promoter Score
A correct NPS from raw 0-10 responses, with the promoter/passive/detractor breakdown.
Net revenue retention with leaky-bucket flag
A correct NRR computation (net of expansion) with a leaky-bucket verdict and a benchmark comparison.
Normalized competitor comparison scorecard
The buyer gets a structured comparison grid with a distinct row for every competitor they name, matched on whole words against the row's name or domain, so one merged row cannot stand in for two competitors. Each row carries the competitor's name, a host-like domain, site traffic, a G2 rating, an authority rank, a positioning phrase, an ease-of-use note, and one specific weakness. The row count must reach at least the number of named competitors, domains are unique across rows, the numeric metrics are checked as in-range, and the written entries must clear minimum word floors rather than merely being present.
One-sentence description of what I'm building and why
One plain-language sentence that states what you are building, for whom, and why it matters, machine-checked against the published rules: exactly one sentence, inside the published word band, a purpose connective present, no banned buzzwords, no em or en dashes.