B
Parent Smartphone Setup Remote Guide
3.35
Derivation Chain
Step 1
Increasing digital adoption among adults in their 40s-60s
→
Step 2
Dependence on children for smartphone setting changes
→
Step 3
Remote screenshot-based guidance delivery
Problem
When parents aged 65-80 want to change smartphone font size, connect to Wi-Fi, update apps, or adjust KakaoTalk notification settings, they call their children aged 40-60. Explaining navigation paths like 'Settings → Display → Font Size' over the phone takes over 30 minutes because each person sees different screens, and menu locations vary across Samsung, LG, and iPhone — causing stress on both sides. This repeats 2-3 times per month, and when children are busy, parents endure the inconvenience for days.
Solution
After selecting the parent's smartphone model, the service provides step-by-step visual guides based on actual device screenshots with 'tap this button' instructions. The top 20 most frequently asked setting changes (font size, Wi-Fi, Bluetooth, notifications, battery saver, etc.) are organized by category, and children can send the relevant guide link directly to their parents via KakaoTalk. The UI features large text and large images so parents can follow along independently.
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 (73%)
Data Availability
23.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 (53/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 [low]
Data Pipeline [medium]