SIGNAL
Not every idea deserves to become a product. Prove the economic and behavioral signal first.
Before code, tests demand, competition, complaints, pricing and whitespace, then returns a BUILD / MODIFY / STOP decision with evidence confidence.
What remains when the system finishes?
The output is not a pile of slides; it is a usable work package that directly feeds the next decision or implementation step.
Market, competitor and substitute map
Complaint, need and payment signals
Value / likelihood / investment matrix
BUILD / MODIFY / STOP + confidence + next test
What is in, and what is not?
One product idea and one primary target market
Public-source research; paid user research is excluded
Focused scan of up to 8 direct competitors / substitutes
Produces a decision report; no product architecture or code
We tested the Product Systems idea on itself.
We evaluated the Product Systems idea through value, likelihood, investment and evidence confidence. The model survived, but overlapping boundaries and the missing BUILD bridge became required changes.
DECISION / MODIFY AND BUILD — canonicalize boundaries, add BUILD bridge, measure conversion.
When should you use this system?
You have a new SaaS or tool idea
You do not know whether a niche will actually pay
You want to reduce risk before writing code
Close this bottleneck, then move only to the stage you actually need.
Possible next system: REVERSE / Product reverse analysis. Skip it if that bottleneck is already solved.