B

MakerDoc Build Guide Builder

3.30

Derivation Chain

Step 1 From Scratch (DIY/self-build) trend expansion
→
Step 2 Increasing content production in maker communities
→
Step 3 Project documentation and sharing tool

Problem

When makers who have completed From Scratch projects try to share their process on blogs or communities, they spend an average of 4-6 hours per project on photo organization, circuit diagram insertion, BOM table creation, and step-by-step formatting. Non-developer makers in particular are unfamiliar with Markdown or HTML and often give up on creating quality documentation.

Solution

Drag and drop project photos in order and AI automatically recognizes build steps through image analysis. Attach BOM lists, circuit diagrams, and 3D model files for automatic rendering into structured build guides. Supports one-click export to Naver Blog, Instructables, GitHub, and more.

Target: Electronics, woodworking, and 3D printing makers ages 20-40; makerspace instructors; DIY YouTubers and bloggers
Revenue Model: Premium SaaS at 39,000 KRW (~$29)/month per account (unlimited projects, AI documentation), Free Plan limited to 2 projects/month.
Ecosystem Role: Infrastructure
MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty
3.0/5
U Urgency
3.0/5
M Market
3.0/5
R Realizability
4.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 (50/100)

Competition
8.0/20
Market Demand
6.2/20
Timing
14.0/20
Revenue Signals
7.5/15
Pick-Axe Fit
7.5/15
Solo Buildability
7.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

Frontend [medium] AI/ML [medium] Backend [low]
Dashboard