B
Inheritance Tax Payment Source Simulator
2.65
Derivation Chain
Step 1
Inheritance & gift tax simulation
→
Step 2
Payment source problem after inheritance tax calculation
→
Step 3
Cash shortfall with high Real Estate concentration → in-kind vs. installment payment decision
Problem
Even when a person in their 60s calculates inheritance tax at ~$75,000–375,000, if 70–80% of assets are in Real Estate, the heirs (children) lack the cash to pay the tax. Deciding whether property-in-kind payment, installment payment over 5–10 years, or property sale is the best strategy requires a tax consultant (costing ~$375–750), and there's no tool to compare scenarios beforehand.
Solution
Enter the decedent's asset list (Real Estate assessed values, financial assets, insurance proceeds) on the web, and the system calculates the estimated inheritance tax, then displays a comparison table of three payment methods (lump sum, property-in-kind payment, installment payment) with real costs for each scenario (interest, appraisal fees, distressed sale discounts, etc.). It identifies the cash shortfall and provides specific solutions (insurance proceeds utilization, optimal property selection for in-kind payment, etc.).
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 (60%)
Data Availability
23.1/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 (54/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 [high]
Data Pipeline [low]