<!-- Source: Kon Master Brief — §8 Key Risks -->

## 8. Key Risks

| Risk | Mitigation |
|---|---|
| Local AI hardware requirements exclude users on low-spec machines | Minimum spec defined: 8GB RAM, 2020+ CPU. Phi-4-mini (2.3GB) runs at 15–25 tok/s on minimum hardware. Publish specs prominently. |
| Tiimo expands to Android/desktop and closes the gap | Move fast. Tiimo's Android codebase is reportedly causing severe issues. Their B2B pivot may distract from consumer product. |
| Zero distribution infrastructure | 90-day calendar above. LaunchList + Reddit + TikTok seeding + Product Hunt. Total budget: £81. |
| Lifetime pricing limits long-term revenue | Cloud tier provides recurring revenue. Monitor conversion rate. Launch pricing for first 500 creates urgency. |
| Scope creep from secondary audiences (TTRPG, B2B) | Neurodivergent beachhead ONLY until validated. No feature work for secondary audiences until £2K MRR. |
| Nobody has seen Kon yet — zero external validation | Beta this week fixes this. Share embarrassingly early. |
| ADHD app market high abandonment rate | Design around the shame spiral. Welcome users back without judgement. Never punish inconsistency. Grace day recovery rate is the key metric. |
| Lifetime pricing economics break if cloud costs grow | Keep cloud tier strictly optional. Base product must remain sustainable on one-time revenue alone. |
| EAA compliance required as Kon grows beyond microenterprise threshold | Build to WCAG 2.2 AA from day one. Publish VPAT before competitors do. |
| cr-sqlite development pace has slowed since late 2024 | Core CRDT logic is sound and self-contained. Fallback: Automerge + SQLite BLOB storage, reusing entire iroh/mDNS networking stack unchanged. |
| Code signing costs are unavoidable | macOS £79/year + Windows £240–£480/year = ~£320–£560/year minimum. Budget from first revenue. |
