CrossBorder Settlement Bridge

3.70

Derivation Chain

Step 1 Global payment Infrastructure advancement

→

Step 2 Rising overseas revenue for small Korean SaaS companies

→

Step 3 Overseas payment → domestic Tax Accounting automated bridge

Problem

Korean SaaS operators with 1-5 people using overseas payment platforms like Stripe or Paddle spend 6-10 hours each month-end converting foreign revenue to KRW and preparing VAT and withholding tax filing documents. Exchange rate base-date confusion and revenue recognition timing errors trigger 1-2 additional correction requests to tax accountants per quarter, costing $75-$150 (100K-200K KRW) each time.

Solution

Connect via Stripe/Paddle API to automatically convert each transaction to KRW, classify revenue recognition timing, and generate monthly VAT/withholding Tax filing spreadsheets. Outputs in a standardized format for Tax Accounting firms, with alerts for revenue variances caused by exchange rate fluctuations.

Target: Korean SaaS/digital product sellers with 1-5 people using overseas payment platforms, Freelancer developers

Revenue Model: SaaS monthly flat rate $21.75/month (29K KRW, up to 500 transactions/month), $36.75/month (49K KRW, up to 2,000). Additional payment platform API integration $7.50/month (10K KRW) per platform.

Ecosystem Role: Infrastructure

MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty

2.0/5

U Urgency

4.0/5

M Market

4.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 (70%)

Tech Complexity

34.7/40

Data Availability

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

Competition

8.0/20

Market Demand

6.2/20

Timing

16.0/20

Revenue Signals

10.5/15

Pick-Axe Fit

12.0/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

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

Dashboard