B
Business Closure & Restart Admin Roadmap
3.20
Derivation Chain
Step 1
Career-based small business and Freelancer transition
→
Step 2
Recovery after self-employment failure
→
Step 3
Business closure filing → delinquent tax settlement → re-startup support fund connection admin sequence
Problem
When a 52-year-old Self-employed cafe owner wants to close after 3 years of operation, there are 10+ administrative procedures including business closure filing (HomeTax) → VAT final return → social insurance deregistration → lease deposit recovery → remaining inventory disposal → delinquent tax installment application. Getting the order wrong incurs penalties. After closure, government support programs like 'Second Chance Special Funds' exist for re-startups, but applicants must first complete credit recovery procedures during the closure phase to qualify — a chain of prerequisites most people don't know about.
Solution
Users enter their business type, planned closure date, delinquency status, and debt level on the web. The tool automatically generates a timeline from closure → settlement → restart with all administrative procedures. It visualizes dependencies showing 'you must complete this step before the next one becomes available.' The connected path from credit recovery → restart funding → re-startup training is displayed in a single view.
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 (65%)
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]