B
My Neighborhood Senior Culture Program Calendar
2.75
Derivation Chain
Step 1
Miss Trot Season 4 craze — surge in cultural consumption among people in their 50s
→
Step 2
Fragmented information about local cultural programs for people in their 50s
Problem
People in their 50s want to participate in free or affordable cultural programs (calligraphy, photography, instruments, dance, etc.) at local community centers, libraries, and district offices beyond just trot concerts, but information is scattered across each institution's website. They must check district office blogs, community center cafes, and library homepages separately, and miss enrollment deadlines, losing out on classes. On average, they miss 2-3 program opportunities per month.
Solution
On the web, users set their residential area (district/neighborhood level) and all cultural and sports programs within a 5km radius are displayed on a unified calendar. Features include enrollment-start alerts 3 days in advance, comparison of similar programs (schedule, cost, reviews), and interest-based tag filtering.
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 (52/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]
Data Pipeline [medium]