B
K-Moonshot Project Management Hub
3.20
Derivation Chain
Step 1
8-sector K-Moonshot national R&D programs launched
→
Step 2
Administrative burden on K-Moonshot project teams
→
Step 3
Integrated project progress, deliverables, and settlement management SaaS
Problem
Small research institutions and university labs (5-20 researchers) conducting national R&D projects like K-Moonshot must handle progress reports, research fund settlements, and deliverable tracking (papers, Patents, software registrations) across separate systems (IRIS, RCMS, e-R&D). Each quarter, one researcher spends 3-5 days writing reports — and format changes frequently force complete rewrites.
Solution
Auto-maps IRIS and RCMS reporting formats so researchers can enter progress data, labor costs, material expenses, and travel costs in a single dashboard, which auto-converts to each system's submission format. Monitors deliverables (papers, Patents) and budget execution rates in real time, with automated checklist alerts before settlement deadlines.
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 (72%)
Data Availability
23.1/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 (52/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
Frontend [medium]
Backend [medium]
Data Pipeline [low]