SIGNAL
Desk research guides direction; customer behavior validates it. Do not confuse the two.
Before code, gathers public demand, competition, complaint, pricing and whitespace signals; separates them from first-party customer evidence and returns BUILD / MODIFY / STOP + confidence + the next customer test.
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
Separate record of desk-research signals and first-party customer evidence
Value / likelihood / investment matrix + evidence confidence
BUILD / MODIFY / STOP + next customer-validation test
What is in, and what is not?
One product idea and one primary target market
DESK RESEARCH / Included: public search, complaint, competitor, substitute, pricing and market signals
CUSTOMER VALIDATION / Never assumed: interviews, paid smoke tests, pre-orders, activation, retention or real payment behavior count only when actually observed
CLAIM RULE / Public signals alone never justify 'demand validated' or 'willing to pay'; first-party behavioral or economic evidence is required
Focused scan of up to 8 direct competitors / substitutes
Produces a decision report and next-test definition; no product architecture or code
We used the SIGNAL decision model on our own Product Systems model.
We evaluated the ahmetcanal.com Product Systems model through value, likelihood, investment and available evidence confidence. This is real internal decision evidence, not customer validation: it contains no interview, payment or usage-behavior evidence.
DECISION / MODIFY AND BUILD — canonicalize boundaries, add the BUILD bridge, measure conversion; collect first-party evidence before claiming customer demand validation.
When should you use this system?
You have a new SaaS or tool idea
You do not know how strong the evidence is for a niche's willingness-to-pay assumption
You want to know which assumption needs a real customer test 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.