Signal Reader — External Intelligence Frameworks
While frontier-antenna reads AI developments and emergence-detector watches internal capability combinations, signal-reader provides the frameworks for interpreting external signals: markets, users, technology adoption, and competitive dynamics.
This is the knowledge skill of the Sense director — it teaches how to read signals, not what the signals currently say.
Signal Categories
Technology Readiness Signals
When is a capability ready for product exposure?
| Signal |
What It Means |
Product Implication |
| Works in demos, fails in production |
Capability is pre-ready |
Seed, don't surface. Prototype to understand failure modes. |
| Works reliably but requires expertise |
Capability is expert-ready |
Surface to power users. Design for progressive disclosure. |
| Works reliably for general users |
Capability is market-ready |
Surface broadly. Compete on experience, not capability. |
| Multiple competitors offer it |
Capability is commoditized |
Differentiate on synthesis, not the capability itself. |
Technology Readiness Levels (adapted for AI products):
- Theoretical — Research papers suggest it's possible
- Demonstrated — Works in controlled conditions (benchmarks, demos)
- Prototype — Works in your system with effort
- Reliable — Works consistently with minimal intervention
- Productized — Works as a seamless part of a product experience
- Commoditized — Everyone offers it; no competitive advantage
Market Timing Signals
| Signal |
Reading |
| High interest, few products |
Early window — opportunity to define the category |
| Growing adoption of adjacent products |
Adjacent possible — market is warming but hasn't arrived yet |
| Established competitors, stable market |
Late entry — need 10x better or radically different surface |
| Market fatigue, user complaints about existing solutions |
Disruption window — reframe the problem, not the solution |
| Regulatory uncertainty |
Wait or hedge — monitor, prototype, but don't bet big |
Demand Signals (for solo builders)
Without enterprise analytics, read demand through:
- Watering holes — Where do potential users gather? What do they complain about?
- Proxy metrics — Search volume, GitHub stars on related tools, forum activity
- Direct conversation — What do people ask you to build? What do they assume already exists?
- Behavioral reveals — What are people using awkward workarounds to accomplish?
- Adjacent adoption — When users adopt tool X, what complementary need does it create?
Competitive Signals
| Signal |
Reading |
| New entrant with funding, no product |
Validation — someone else sees the opportunity. Speed matters. |
| Established player adds the capability |
Commoditization clock started — differentiate on synthesis |
| Multiple small players, no dominant one |
Category is forming — opportunity to define it |
| A player pivots away from the space |
Possible warning — investigate why they left |
| Open-source alternative emerges |
Commoditization accelerating — move up the value chain |
Diffusion Curve Awareness
Products don't need to target the mass market. For a solo builder, the relevant question is: which part of the diffusion curve are my users on?
| Segment |
Characteristics |
Product Design Implication |
| Innovators (2.5%) |
Tolerate rough edges, value novelty |
Surface raw capability. Minimal experience layer. |
| Early adopters (13.5%) |
Want advantage, tolerate setup effort |
Surface with guidance. Clear value proposition. |
| Early majority (34%) |
Want proven solutions, low friction |
Surface with polish. Experience-first design. |
| Late majority (34%) |
Want standards, resist change |
Surface within existing workflows. Integration-first. |
Most AI-native products in 2026 are still in innovator/early-adopter territory. Design accordingly.
Integration with Other Sense Skills
- frontier-antenna provides the raw capability signal; signal-reader provides the framework for interpreting its product readiness
- capability-radar maps what's possible; signal-reader assesses whether the market is ready for it
- emergence-detector surfaces surprises; signal-reader evaluates whether the surprise has external demand
1---2name: signal-reader3description: Frameworks for reading external signals through a product lens — market timing, technology adoption curves, readiness levels, competitive shifts, and demand indicators. Use when evaluating whether a capability is ready for product exposure, whether the market timing is right, or how to interpret weak signals about user needs and technology shifts.4---56# Signal Reader — External Intelligence Frameworks78While frontier-antenna reads AI developments and emergence-detector watches internal capability combinations, signal-reader provides the frameworks for interpreting **external** signals: markets, users, technology adoption, and competitive dynamics.910This is the knowledge skill of the Sense director — it teaches how to read signals, not what the signals currently say.1112## Signal Categories1314### Technology Readiness Signals1516When is a capability ready for product exposure?1718| Signal | What It Means | Product Implication |19|---|---|---|20| Works in demos, fails in production | Capability is pre-ready | Seed, don't surface. Prototype to understand failure modes. |21| Works reliably but requires expertise | Capability is expert-ready | Surface to power users. Design for progressive disclosure. |22| Works reliably for general users | Capability is market-ready | Surface broadly. Compete on experience, not capability. |23| Multiple competitors offer it | Capability is commoditized | Differentiate on synthesis, not the capability itself. |2425**Technology Readiness Levels (adapted for AI products):**26271. **Theoretical** — Research papers suggest it's possible282. **Demonstrated** — Works in controlled conditions (benchmarks, demos)293. **Prototype** — Works in your system with effort304. **Reliable** — Works consistently with minimal intervention315. **Productized** — Works as a seamless part of a product experience326. **Commoditized** — Everyone offers it; no competitive advantage3334### Market Timing Signals3536| Signal | Reading |37|---|---|38| High interest, few products | **Early window** — opportunity to define the category |39| Growing adoption of adjacent products | **Adjacent possible** — market is warming but hasn't arrived yet |40| Established competitors, stable market | **Late entry** — need 10x better or radically different surface |41| Market fatigue, user complaints about existing solutions | **Disruption window** — reframe the problem, not the solution |42| Regulatory uncertainty | **Wait or hedge** — monitor, prototype, but don't bet big |4344### Demand Signals (for solo builders)4546Without enterprise analytics, read demand through:4748- **Watering holes** — Where do potential users gather? What do they complain about?49- **Proxy metrics** — Search volume, GitHub stars on related tools, forum activity50- **Direct conversation** — What do people ask you to build? What do they assume already exists?51- **Behavioral reveals** — What are people using awkward workarounds to accomplish?52- **Adjacent adoption** — When users adopt tool X, what complementary need does it create?5354### Competitive Signals5556| Signal | Reading |57|---|---|58| New entrant with funding, no product | **Validation** — someone else sees the opportunity. Speed matters. |59| Established player adds the capability | **Commoditization clock started** — differentiate on synthesis |60| Multiple small players, no dominant one | **Category is forming** — opportunity to define it |61| A player pivots away from the space | **Possible warning** — investigate why they left |62| Open-source alternative emerges | **Commoditization accelerating** — move up the value chain |6364## Diffusion Curve Awareness6566Products don't need to target the mass market. For a solo builder, the relevant question is: **which part of the diffusion curve are my users on?**6768| Segment | Characteristics | Product Design Implication |69|---|---|---|70| Innovators (2.5%) | Tolerate rough edges, value novelty | Surface raw capability. Minimal experience layer. |71| Early adopters (13.5%) | Want advantage, tolerate setup effort | Surface with guidance. Clear value proposition. |72| Early majority (34%) | Want proven solutions, low friction | Surface with polish. Experience-first design. |73| Late majority (34%) | Want standards, resist change | Surface within existing workflows. Integration-first. |7475Most AI-native products in 2026 are still in innovator/early-adopter territory. Design accordingly.7677## Integration with Other Sense Skills7879- **frontier-antenna** provides the raw capability signal; **signal-reader** provides the framework for interpreting its product readiness80- **capability-radar** maps what's possible; **signal-reader** assesses whether the market is ready for it81- **emergence-detector** surfaces surprises; **signal-reader** evaluates whether the surprise has external demand
npbuilds