B
Solar Power Revenue Dashboard
3.20
Derivation Chain
Step 1
Rapid growth of solar power generation (surpassing hydropower in the US)
→
Step 2
Surge in small-scale solar operators in South Korea
→
Step 3
Real-time generation-to-revenue tracking and automated settlement
Problem
Over 120,000 small-scale solar power operators (under 100kW) exist in South Korea — farms and rooftop installations — but real-time revenue tracking is difficult because KEPCO's System Marginal Price (SMP), Renewable Energy Certificate (REC) prices, and grid marginal prices fluctuate hourly. Operators can only determine actual revenue when they receive KEPCO's month-end settlement statement, and since inverter monitoring and settlement data are siloed, detecting generation anomalies takes an average of 3-5 days. This results in 5-10% annual revenue loss from undetected equipment failures.
Solution
(1) Integrate inverter APIs (SolarEdge, Growatt, etc.) with KEPCO SMP/REC public data to provide a real-time estimated revenue dashboard, (2) send instant KakaoTalk/SMS alerts when abnormal generation patterns are detected, and (3) auto-generate monthly tax filing settlement reports.
NUMR-V Scores
NUMR-V Scoring System
| 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. |
SaaS N=.15 U=.20 M=.15 R=.30 V=.20
Senior N=.25 U=.25 M=.05 R=.30 V=.15
Feasibility (64%)
Data Availability
15.0/25
Feasibility Breakdown
| 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. |
Market Validation (58/100)
Validation Breakdown
| 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. |
Technical Requirements
Backend [medium]
Frontend [medium]
Data Pipeline [low]