Choose what to get done
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 an independent, non-duplicated canvas for each role you need to win, 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 where every named competitor has the same set of fields populated (domain, site traffic, G2 rating, authority rank, positioning phrase, ease-of-use note, specific weakness), with the metrics validated as in-range.
One-sentence description of what I'm building and why
One clear sentence (8 to 40 words, no buzzwords) that states what you are building, for whom, and why it matters.
Online-presence audit for demand, trust, and journey impact
I get a structured audit of my online presence: each page or surface across the four categories rated on create-demand, build-trust, and potential-impact using fixed enums, with negatives flagged so I know what is hurting the journey.
OpenAPI endpoint reference
A complete, well-formed reference for one endpoint: method, path, parameters (with every path placeholder covered), the required status codes, and a consistent request body.
You are not what you make. You are the one who can make it.
Opens soon. Get early access the day it goes live.