37 lines
1.2 KiB
Markdown
37 lines
1.2 KiB
Markdown
# Market Signal
|
|
|
|
## Purpose
|
|
|
|
This document defines how `whynot` records and interprets early signals from potential users, collaborators, customers, or investors.
|
|
|
|
## Signal Principles
|
|
|
|
- Signals are evidence, not vibes.
|
|
- Weak signals are useful if clearly labeled.
|
|
- Contradictory signals should be preserved.
|
|
- A signal should be connected to a prototype, audience, or hypothesis.
|
|
- Lack of signal is also information.
|
|
|
|
## Signal Strength
|
|
|
|
| Level | Name | Meaning |
|
|
|---|---|---|
|
|
| S0 | No Signal | No observable interest or usefulness |
|
|
| S1 | Weak Signal | Some curiosity, comments, or informal interest |
|
|
| S2 | Medium Signal | Repeated interest, specific feedback, or trial use |
|
|
| S3 | Strong Signal | Users take action, return, refer, contribute, or ask for pricing |
|
|
| S4 | Commercial Signal | Users pay, pre-order, commit budget, or request procurement path |
|
|
|
|
## Signal Record Format
|
|
|
|
Use `templates/signal-record.md`.
|
|
|
|
## Signal Review Questions
|
|
|
|
- Who produced the signal?
|
|
- What did they actually do?
|
|
- What did they merely say?
|
|
- Was there cost, effort, risk, or commitment involved?
|
|
- Does the signal point toward a specific product, offer, or community need?
|
|
- Does the signal justify another experiment?
|