B
AI Education Project Portfolio Builder
3.30
Derivation Chain
Step 1
Expansion of AI/XR convergence Education (Metaverse Academy, etc.)
→
Step 2
Post-completion job seeking and Freelancer activities by graduates
→
Step 3
Converting AI Education project deliverables into job-ready portfolios
Problem
Non-CS graduates completing programs like Metaverse Academy or AI bootcamps spend 1–2 weeks trying to organize team project deliverables into job-ready portfolios—struggling with tech stack descriptions, isolating individual contributions, editing demo videos, and writing GitHub READMEs. Their unfamiliarity with technical terminology makes it difficult for recruiters to properly assess their capabilities, and post-completion employment rates remain below 40% within 3 months.
Solution
By connecting team project repositories (GitHub) and presentation materials, the service automatically isolates individual commit contributions and generates a portfolio page that reframes tech stack, architecture, and personal role from a recruiter's perspective. It also provides auto-edited demo video highlights, GitHub README template generation, and a resume-linked one-pager.
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 (70%)
Data Availability
20.8/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 (51/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]
AI/ML [low]