B
Pre-Retirement Pay Stub Analyzer
3.55
Derivation Chain
Step 1
Career transition matching
→
Step 2
Poor understanding of pre-retirement pay components
→
Step 3
Pay stub item-by-item post-retirement change simulation
Problem
Office workers at large corporations approaching age 55 cannot accurately determine how each line item on their pay stub (base salary, position allowance, meal stipend, vehicle maintenance, performance bonus, welfare benefits) will disappear or convert after retirement. They don't know which items count toward the average wage used to calculate severance, or how tax-exempt items affect retirement income tax—leading to severance payouts frequently coming in 2–5 million KRW (~$1,500–$3,750) lower than expected. Getting clarity requires asking HR or consulting a labor attorney at 100,000–200,000 KRW (~$75–$150) per session.
Solution
Upload a pay stub PDF on the web or manually enter line items, and the tool visually breaks down each item's inclusion in severance calculation, retirement income tax impact, and post-retirement status (eliminated or converted). It generates an estimated net severance payout along with an auto-generated 'pre-retirement pay item checklist.'
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.6/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 (51/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
Frontend [medium]
Backend [medium]
Data Pipeline [low]