Solo SaaS developers, content creators, and app development companies depend on platforms (YouTube, Instagram, App Store, Google Play, AWS, OpenAI, etc.) whose terms of service change an average of 3-5 times per year. Missing these changes can result in sudden service suspension or revenue-sharing structure changes. The full terms run tens of thousands of words in legal language, and extracting only the changed sections and assessing the impact on one's own service takes 2-4 hours per change.
(1) Periodically scrape monitored Platform TOS pages to detect changes (diff), (2) Use LLM to summarize changes and tag 'affected business types,' (3) Match against user-registered business profiles to send personalized alerts (email/Slack/KakaoTalk).
| N Novelty | 1-5 | How uncommon the service is in market context. |
| U Urgency | 1-5 | How urgently users need this problem solved now. |
| M Market | 1-5 | Market size and growth potential from proxy indicators. |
| R Realizability | 1-5 | Buildability for a small team with realistic constraints. |
| V Validation | 1-5 | Validation signal quality from competition and demand data. |
| Tech Complexity | / 40 | Difficulty of core implementation stack. |
| Data Availability | / 25 | Practical availability and cost of required data. |
| MVP Timeline | / 20 | Expected time to ship a usable MVP. |
| API Bonus | / 15 | Bonus for viable public API leverage. |
| Competition | / 20 | Signal quality from competitor landscape. |
| Market Demand | / 20 | Demand proxies from search and mention patterns. |
| Timing | / 20 | Fit with current shifts in tech, behavior, and regulation. |
| Revenue Signals | / 15 | Reference evidence for monetization viability. |
| Pick-Axe Fit | / 15 | How well the concept serves participants in a trend. |
| Solo Buildability | / 10 | Practicality for lean-team implementation. |