B
Couple Investment Style Mediation Board
3.35
Derivation Chain
Step 1
S&P 500 crash fears
→
Step 2
Investment opinion conflicts between couples in their 50s
→
Step 3
No tool for evidence-based consensus when spouses disagree on investment direction
Problem
When couples in their 50s manage joint assets (severance pay, savings, real estate sale proceeds), one spouse thinks 'now is a buying opportunity' while the other insists 'it will drop further, let's wait.' After emotional arguments, they either end up doing nothing, or one spouse secretly invests, escalating into marital conflict. There is no tool to quantify each partner's investment style and risk tolerance to produce a 'joint portfolio consensus plan' for couples.
Solution
Each spouse completes an investment style assessment (12 questions) on the web, which quantifies their risk tolerance. After entering joint assets, target timeline, and required amount, the system proposes 3 portfolio plans acceptable to both partners. Each plan's projected returns, maximum potential loss, and principal recovery period are visually compared to provide an evidence-based foundation for discussion.
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 (62%)
Data Availability
18.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 (50/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]