Steel CBAM Document Builder

4.05

Derivation Chain

Step 1 AI data center steel demand + EU CBAM full implementation

→

Step 2 Steel exporters

→

Step 3 CBAM (Carbon Border Adjustment Mechanism) declaration document auto-generation

Problem

As steelmakers like Hyundai Steel and Dongkuk Steel produce H-beams and rebar for AI data centers, their EU exports are also increasing. With the EU CBAM transitional period fully taking effect from 2026, reporting embedded carbon per product is now mandatory. Calculating, verifying, and preparing the declaration for a single product takes 2-3 weeks, with consulting fees running 5-10 million KRW (~$3,750-$7,500) per engagement.

Solution

Input steel manufacturing process data (raw material inputs, energy consumption) to automatically calculate embedded carbon per EU CBAM requirements, then generate verification-ready reports and declaration documents with one click. Auto-updates when EU regulations change and provides comparative analysis against previous declarations.

Target: Environmental safety teams at mid-size steelmakers (Hyundai Steel/Dongkuk Steel suppliers, $7.5M-$37.5M annual revenue), customs teams at steel trading companies

Revenue Model: Per-transaction billing at 300,000 KRW (~$225) per product declaration, monthly plan at 490,000 KRW (~$370)/month (includes 3 products), 20% discount with annual contract

Ecosystem Role: Regulation

MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty

4.0/5

U Urgency

5.0/5

M Market

3.0/5

R Realizability

4.0/5

V Validation

4.0/5

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 (78%)

Tech Complexity

34.7/40

Data Availability

23.1/25

MVP Timeline

20.0/20

API Bonus

0.0/15

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 (61/100)

Competition

8.0/20

Market Demand

6.2/20

Timing

18.0/20

Revenue Signals

10.5/15

Pick-Axe Fit

13.5/15

Solo Buildability

5.0/10

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 [low] Data Pipeline [low]

Dashboard