S
FairShare: Sibling Eldercare Cost Splitter
4.35
Derivation Chain
Step 1
Dual burden planning: parent caregiving + personal retirement
→
Step 2
Care cost sharing is the core source of sibling conflict
→
Step 3
Auto-calculate fair share ratios based on income, distance, and caregiving hours
Problem
When 3-4 siblings in their 50s try to split caregiving costs for parents in their 80s, there's no objective standard for 'who pays how much,' causing emotional conflicts. No tool exists that comprehensively factors in income gaps, distance from parents, time invested in direct caregiving, and past financial support history. Consulting a lawyer feels excessive, and family discussions get derailed by emotions, making rational agreement nearly impossible.
Solution
On a web app, siblings enter the number of family members, each person's income bracket (range selection instead of exact amounts), distance from parents' residence, and monthly hours of direct caregiving. The tool auto-calculates a 'fair share ratio' using weighted factors and presents 3 allocation scenarios (equal split, income-proportional, and time-value-adjusted) for comparison. The agreed result is documented and exported as a PDF.
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 (63%)
Data Availability
19.4/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 [medium]