A
Weak Yen Cost Alert SaaS
3.80
Derivation Chain
Step 1
Continued weak yen and Korea-Japan trade expansion
→
Step 2
Growth in Small Business Owners importing from Japan
→
Step 3
Real-time import cost monitoring service
→
Step 4
Cost fluctuation → automated selling price adjustment tool
Problem
Online sellers (Smartstore/Coupang) who directly import Japanese products manually track cost changes due to yen exchange rate fluctuations, missing optimal pricing adjustment windows and losing 3-8% of their margins. For sellers with 50+ products, recalculating costs combining exchange rates, tariffs, and shipping takes 3-5 hours per week.
Solution
Register product URLs from Japanese shopping sites (Rakuten, Amazon JP) to automatically scrape yen-denominated prices, then calculate KRW landed costs by applying real-time exchange rates, tariff rates, and shipping fees. When margins drop below a set threshold (e.g., 15%), the system sends alerts and offers automated price adjustment via Smartstore/Coupang API integration.
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 (66%)
Data Availability
17.1/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 (57/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 [low]
Data Pipeline [medium]