A
Rate-Hold Loan Refinancing Hub
3.65
Derivation Chain
Step 1
Bank of Korea base rate held at 2.50% for 6 consecutive meetings
→
Step 2
Borrower rate comparison and refinancing demand
→
Step 3
Integrated hidden-cost simulator for loan refinancing
Problem
With the prolonged base rate freeze widening interest rate gaps between commercial banks, mortgage and personal loan holders (salaried workers ages 30-50) consider refinancing but struggle to accurately calculate hidden costs like early repayment penalties, stamp duty, and mortgage registration fees. Bank branch consultations only recommend in-house products, and loan comparison platforms show only interest rates without revealing actual savings. Cases of losing $375-$1,500 (~500,000-2,000,000 KRW) from poorly-timed refinancing are frequent.
Solution
Users enter their current loan terms (remaining balance, interest rate, remaining term, early repayment penalty rate), and the system automatically compares total refinancing costs (penalties + stamp duty + registration fees) and actual savings across 10 major banks on 5-year/10-year/maturity bases. Visualizes the break-even point and optimal refinancing timing to support the 'should I refinance now?' decision within 1 minute.
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 (70%)
Data Availability
20.8/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 (55/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 [medium]
Data Pipeline [low]