B
My Local Trot Performance Schedule
3.60
Derivation Chain
Step 1
Trot craze fueled by shows like 'Unknown Legends'
→
Step 2
Difficulty for 50s Trot fans to see nationwide performance schedules at a glance
Problem
Trot fans in their 50s have to search through each artist's fan cafe, social media, and ticket sites to find performance schedules. Free Trot performances included in local festivals and events are only posted on local government websites, making them easy to miss. With no single place aggregating nationwide tour schedules, it takes 30 minutes to 1 hour to figure out 'what Trot performances I can see in my area this month.'
Solution
Aggregates nationwide Trot performances (paid concerts + free performances at local government festivals + open broadcast recordings) into a single calendar view. Users can favorite artists to receive notifications when performances are confirmed. Filter by region, date, or artist name, and see ticket purchase links, free/paid status, and seating information at a glance.
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. |
N=.15 U=.20 M=.15 R=.30 V=.20
Feasibility (74%)
Data Availability
19.6/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 (56/100)
Solo Buildability
10.0/10
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 [low]
Data Pipeline [medium]
Backend [low]