B

CS Lab Auto-Grading Engine

3.00

Derivation Chain

Step 1 CS Education curriculum revision (Missing Semester 2026)
→
Step 2 Demand for lab environment setup among CS educators
→
Step 3 Demand for automated lab assignment grading

Problem

Instructors teaching CS practical tools (Git, shell, Docker) spend 10–15 minutes manually grading each student's lab assignment—5–7 hours per week for a 30-student course. Unlike programming assignments, there are virtually no auto-grading tools for shell scripts, Git commit histories, or Docker configurations, making instructor workload 2–3x higher than for standard programming courses.

Solution

Automatically executes student-submitted shell scripts, Git repositories, and Dockerfiles in isolated environments and grades them against expected outcomes. Instructors define grading rubrics in YAML, and the system auto-generates test cases, assigns partial credit, and provides automated feedback comments.

Target: CS practical tools course instructors (universities, bootcamps) managing courses of 20–100 students
Revenue Model: SaaS monthly: ~$59/month per course (500 gradings/month), additional gradings at ~$0.07 each, university site license ~$2,240/year
Ecosystem Role: Supplier
MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty
4.0/5
U Urgency
3.0/5
M Market
2.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.
Each dimension is scored 1-5 and weighted into grade S/A/B/C/D.
SaaS N=.15 U=.20 M=.15 R=.30 V=.20 Senior N=.25 U=.25 M=.05 R=.30 V=.15

Feasibility (74%)

Tech Complexity
29.3/40
Data Availability
24.4/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.
Total 100 points; below 50% is filtered out.

Market Validation (52/100)

Competition
8.0/20
Market Demand
6.2/20
Timing
14.0/20
Revenue Signals
10.5/15
Pick-Axe Fit
10.5/15
Solo Buildability
3.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.
Total 100 points; below 50 is filtered out.

Technical Requirements

Infrastructure [medium] Backend [medium] Frontend [low]
Dashboard