JPY Procurement Timing Optimizer

3.15

Derivation Chain

Step 1 Increased JPY exchange rate volatility

→

Step 2 Cost management demand from JPY-settling Small Business Owners

→

Step 3 Automated import procurement decision-making tools

Problem

Small Business Owners importing from Japan place 3–5 orders per month, and exchange rate timing alone can cause 5–8% cost differences for the same volume. However, checking currency charts daily to decide order timing is impractical, and manually executing split-ordering strategies (placing orders across multiple time points) creates excessive administrative burden.

Solution

Users input their order cycle, volume, and target exchange rate. The system recommends optimal order timing and split-ordering strategies based on historical exchange rate patterns and seasonality analysis. Users can set auto-order triggers (email/KakaoTalk notifications) when target rates are reached, plus receive monthly FX gain/loss reports.

Target: Small Business Owners and SME purchasing managers with high dependency on Japanese imports, with monthly order volumes of $3,750–$37,500

Revenue Model: SaaS Monthly Subscription: $44/account (5 order schedules/month), Pro $89/month (unlimited + auto triggers + reports), 20% discount on Annual Subscription

Ecosystem Role: Supplier

MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty

3.0/5

U Urgency

3.0/5

M Market

2.0/5

R Realizability

4.0/5

V Validation

3.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 (75%)

Tech Complexity

34.7/40

Data Availability

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

Competition

8.0/20

Market Demand

6.2/20

Timing

14.0/20

Revenue Signals

10.5/15

Pick-Axe Fit

10.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