A
Objection Template Builder
4.00
Derivation Chain
Step 1
Digital administrative delegation
→
Step 2
Self-guided administrative objection filing process
→
Step 3
Custom template generation based on successful case database
Problem
When Self-employed or retirees in their 50s want to dispute health insurance premium assessments, property tax calculations, or National Pension benefit amounts, they can download the forms from the Government24 portal, but they don't know 'what grounds and what logic to use' to get their objection accepted. Hiring an administrative agent costs 200,000–500,000 won (~$150–$375) per case, and giving up means overpaying hundreds of thousands of won annually.
Solution
Users select the objection type (health insurance premiums/property tax/pension/fines, etc.) and enter their situation on a web interface. The system recommends 'logical structures with high acceptance rates' based on past successful cases and generates a fill-in-the-blank objection template. It also provides guidance on submission channels (online/mail/in-person) and estimated processing times.
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 (67%)
Data Availability
23.3/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 (59/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 [medium]