B
Cashwalk Quiz Earnings Settlement Report
4.05
Derivation Chain
Step 1
Cashwalk answer search trend
→
Step 2
Difficulty for 50s reward app users in tracking actual earnings
→
Step 3
Lack of analysis on total earnings and time efficiency when using multiple reward apps
Problem
Many smartphone users in their 50s use 3-5 reward apps simultaneously (Cashwalk, Toss, Naver, etc.), but their actual earnings from each app are scattered and impossible to track. They spend 30-60 minutes daily on quizzes, step counts, and check-ins without knowing whether their monthly take-home is $2.25 or $22.50. In particular, they often fail to recognize hidden losses such as point-to-cash conversion rates, tax deductions, and expiration dates, leading to activities that pay below minimum wage per hour.
Solution
When you input the list of reward apps you use and your estimated monthly activity time, it automatically calculates estimated total monthly earnings, hourly return rate, and expected loss from point expiration based on an average earnings database per app, and provides a report. Key features: (1) earnings simulation based on average earnings DB of 20 reward apps, (2) ranking by efficiency relative to time investment, (3) alerts for hidden losses from point expiration and conversion rates. Differentiation: the first service to view 'all reward activities' as a portfolio rather than individual apps.
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 (72%)
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 (67/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 [low]
Backend [medium]
Data Pipeline [medium]