100m-offers

Run the interview: pass the market gate, score the four Value Equation terms, list at least ten customer problems, invert each into a solution, then trim and stack components with anchored dollar values. The skill writes the final offer doc with the stack, enhancers, and one weekly assignment.

Price to value, not cost. The skill asks what the outcome is worth to the buyer in year one, then positions the price as a fraction of that number with a value stack above it, since a price presented in isolation always reads as too high.

Use a guarantee when perceived likelihood of achievement is the Value Equation constraint, but only after checking your refund rate and whether the business survives if 10% of buyers invoke it. Conditional guarantees are the default recommendation.

It is the wrong tool when too few people see the offer at all, which is a leads problem, or when customers exist but cash flow fails, which is a money problem. The built-in scope check redirects those cases before any offer work begins.

An offer invented from a two-sentence description is one the user will not ship. The interview surfaces real numbers like margin, delivery hours, and close rate, and missing figures are recorded as open numbers that become the next week of work.