Choose what to get done
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 transparency decision on the market 2x2
I give market size and homogeneity (with thresholds) and get the quadrant plus the publish-on-website recommendation, matching the book's transparency 2x2.
Price waterfall from list to pocket price with leakage flags
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.
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 candidates scored on the Ikigai four-lens fit
A founder receives a structured four-lens score for each candidate problem and a shortlist of those that clear every lens, so they pick a problem to focus on rather than a buzzword.
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.
Problem-statement abstraction ladder
I get a structured abstraction ladder of how-might-we problem statements ordered from most abstract to most concrete, with exactly one marked as the chosen right-sized statement, so I avoid framing my MVP problem too broadly or too narrowly.
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.
Project risk scoring and ranking
A risk register scored by exposure (likelihood x impact), banded, and ranked, flagging which need an owner.
Project scoring and MVP pick
A scored, ranked project pipeline with a recommended MVP that clears your hard gate.