B
Inheritance Asset Overview Dashboard
3.05
Derivation Chain
Step 1
Digital inheritance and asset organization
→
Step 2
Consolidated view of scattered asset holdings
Problem
When a 60-year-old head of household tries to get a full picture of assets spread across 4 banks, 2 brokerages, 5 insurance policies, and 3 properties, they must log into or visit each institution individually, taking 2-3 days to compile everything. There's no unified format to share with family, leading to 'hidden asset' problems where surviving family members can't locate assets after the owner's passing. The Financial Supervisory Service's integrated account lookup is restricted to the account holder only and excludes insurance and Real Estate.
Solution
Users manually enter their financial, insurance, and Real Estate assets by category on the web, and the tool consolidates everything into a single-page dashboard. It shows each asset's valuation, maturity, and returns at a glance, and generates a 'family summary PDF' for sharing. Users can set alerts for asset changes, and the tool provides a simplified inheritance tax simulation with applicable deductions.
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 (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]
Infrastructure [low]