| name | strat-product-offer |
| description | Creates a product offer using the value equation from $100M Offers: dream outcome, perceived likelihood, time delay, effort/sacrifice, offer stack, risk reversal, pricing logic, naming, and one-liner. Use after problem/outcome. |
Product Offer
Create the offer that makes the selected audience think: this solves exactly what I need now.
Workflow
- Load
../_shared/references/strategy.md, ../_shared/references/artifact-conventions.md, and ../_shared/references/quality-gates.md.
- Read:
.ai/strategy/signal/market-signal.md
.ai/strategy/signal/user-context.md
.ai/strategy/signal/problem-outcome.md
.ai/steering/offer-principles.md if present
- Apply the value equation:
Perceived Value = (Dream Outcome × Perceived Likelihood of Achievement) / (Time Delay × Effort & Sacrifice).
- Be direct and critical. Flag vague promises, weak offers, broad audience, unsupported guarantees, fake scarcity, pricing/value mismatch, and missing proof.
- Define one testable claim with a concrete validation window (for example, within X days).
- Classify evidence strength for the core promise (Strong/Medium/Weak).
- Save
.ai/strategy/offer/product-offer.md.
Output template
# Product Offer
## Offer Type
Options: SaaS, Micro-SaaS, Devtool, Course, Community, Cohort, Service, Hybrid
## Audience
## Core Promise
## Dream Outcome
## Perceived Likelihood of Achievement
## Time Delay
## Effort & Sacrifice
## Offer Stack
### Core Offer
### Support
### Templates / Assets
### Bonuses
### Community / Access
### Implementation Help
## Risk Reversal
## Guarantee
## Scarcity / Urgency
Only if real.
## Pricing Logic
## Value Anchor
## Offer Name Options
## Final Offer Name
## Offer One-Liner
Format: I help [specific audience] get [desired outcome] without [main pain/sacrifice] by using [mechanism].
## Assumptions
## Risks
## Open Questions
Output quality checklist
- Audience is specific.
- Promise is testable.
- Value equation is complete.
- Pricing logic + risk reversal are coherent.
- Claim validation window is explicit.
Critical rules
- Do not invent proof, guarantees, scarcity, or urgency.
- Do not define MVP scope in detail yet; that belongs to strat-mvp-scope.
- Do not create final messaging assets or implementation code.