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

Competitor references

No usable source links are available for this idea. Its signal notes and scores need independent verification.

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.

Target: Research administration staff at small national R&D institutions, university industry-academia cooperation office staff
Revenue Model: SaaS Monthly Subscription at 59,000 KRW (~$44)/project/month, 5+ project bundle at 199,000 KRW (~$149)/month, 15% discount for Annual Subscription
Ecosystem Role: Supplier
MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty
3.0/5
U Urgency
4.0/5
M Market
3.0/5
R Realizability
3.0/5
V Validation
3.0/5
NUMR-V Scoring System
N Novelty1-5How uncommon the service is in market context.
U Urgency1-5How urgently users need this problem solved now.
M Market1-5Market size and growth potential from proxy indicators.
R Realizability1-5Buildability for a small team with realistic constraints.
V Validation1-5Validation signal quality from competition and demand data.
N=.15 U=.20 M=.15 R=.30 V=.20

Feasibility (72%)

Tech Complexity
29.3/40
Data Availability
23.1/25
MVP Timeline
20.0/20
API Bonus
0.0/15
Feasibility Breakdown
Tech Complexity/ 40Difficulty of core implementation stack.
Data Availability/ 25Practical availability and cost of required data.
MVP Timeline/ 20Expected time to ship a usable MVP.
API Bonus/ 15Bonus for viable public API leverage.

Market Validation (52/100)

Competition
8.0/20
Market Demand
3.8/20
Timing
14.0/20
Revenue Signals
10.5/15
Pick-Axe Fit
10.5/15
Solo Buildability
5.0/10
Validation Breakdown
Competition/ 20Signal quality from competitor landscape.
Market Demand/ 20Demand proxies from search and mention patterns.
Timing/ 20Fit with current shifts in tech, behavior, and regulation.
Revenue Signals/ 15Reference evidence for monetization viability.
Pick-Axe Fit/ 15How well the concept serves participants in a trend.
Solo Buildability/ 10Practicality for lean-team implementation.

Technical Requirements

Frontend [medium] Backend [medium] Data Pipeline [low]
Dashboard