JPY Travel Group Expense Splitter

2.65

Derivation Chain

Step 1 Widening JPY exchange rate fluctuations

→

Step 2 Rising demand for Japan travel amid weak yen

→

Step 3 Exchange rate confusion in group travel expense splitting

Problem

When splitting JPY payments among group travelers (3–6 people) visiting Japan, each person pays at different times with different cards (varying exchange rate benefits), making the actual KRW settlement amounts inconsistent. Post-trip settlement takes an average of 1–2 hours per group, and disputes over inconsistent rate application arise in 3 out of 10 cases.

Solution

Users photograph each receipt (OCR) during the trip, and the app automatically applies the actual exchange rate at the time of payment, converts to KRW, and splits evenly among members. It factors in card-issuer-specific exchange rate benefits to calculate true per-person costs, shares the final settlement breakdown via KakaoTalk, and minimizes the number of transfers needed to settle up.

Target: Groups of 3–6 office workers in their 20s–30s who travel to Japan 2+ times per year

Revenue Model: Premium in-app purchase: basic splitting free (1x/month), Premium ~$1.40/month (unlimited + OCR + per-card-issuer rate adjustment), travel agency B2B partnership at ~$0.37 Per Transaction

Ecosystem Role: Consumer

MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty

2.0/5

U Urgency

2.0/5

M Market

3.0/5

R Realizability

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

Tech Complexity

29.3/40

Data Availability

17.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 (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	/ 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

Frontend [medium] Backend [medium] Data Pipeline [low]

Dashboard