S
QuizVault: Reward App Answer Archive
4.25
Derivation Chain
Step 1
CashWalk quiz answer search trend
→
Step 2
Reward app users aged 40–60 waste time daily searching for quiz answers
→
Step 3
Service that aggregates scattered quiz answers in one place to eliminate search time
Problem
Reward app users aged 50–60 who use CashWalk, Toss, OK Cashbag, and similar apps must solve 3–5 quizzes daily across multiple apps to earn points, spending 15–20 minutes per day searching for answers on Naver and Google. Answers are buried among blog ads, making them hard to find, and if the search timing doesn't match the quiz posting time, users miss out entirely.
Solution
A web service that aggregates today's quiz answers from major reward apps (CashWalk, Toss, OK Cashbag, Shinhan SOL, etc.), organized by app and time slot. Subscribers receive answers via KakaoTalk or web push notification immediately after quizzes are posted. A past answer archive also reveals recurring question patterns.
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 (78%)
Data Availability
23.1/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 (72/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
Backend [medium]
Frontend [low]
Infrastructure [low]