B

Used Phone Data Erasure Certificate

2.65

Derivation Chain

Step 1 Increasing smartphone setup complexity
Step 2 Expansion of the used phone market
Step 3 Data erasure trust issues between used phone sellers and buyers
Step 4 Service that provides third-party certification of data erasure completion

Problem

Used phone buyers (e.g., Mint, Secuware, etc.) process about 8 million units annually, but cannot prove that the previous owner's data has been completely erased, leading to persistent consumer trust issues. Sellers worry whether a factory reset is sufficient, and buyers face legal liability (up to 50 million KRW in fines for violating the Personal Information Protection Act) in case of data leakage. Currently, erasure verification relies on manual sample checks, making full certification impossible.

Solution

A B2B SaaS that automatically records the data erasure process for used phones and issues blockchain-based certificates. (1) Automatically logs the erasure method, scope, and timestamp during the erasure process, (2) records a third-party certified hash on the blockchain after erasure completion, then issues a QR code certificate, (3) allows buyers to verify the erasure history by scanning the QR code.

Target: Used phone buyers and refurbishers (e.g., Mint, Secuware, unlocked phone specialty stores), and corporate IT asset disposal managers.
Revenue Model: API per-transaction billing: 500 KRW (approx. $0.38) per certificate issued; monthly flat rate of 150,000 KRW (approx. $112.50) (includes 500 certificates per month, additional certificates at 300 KRW (approx. $0.23) each). Separate annual contracts for enterprises.
Ecosystem Role: Infrastructure
MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty
4.0/5
U Urgency
3.0/5
M Market
3.0/5
R Realizability
2.0/5
V Validation
2.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 (69%)

Tech Complexity
29.3/40
Data Availability
19.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.

Market Validation (56/100)

Competition
8.0/20
Market Demand
3.8/20
Timing
14.0/20
Revenue Signals
10.5/15
Pick-Axe Fit
15.0/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

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