B
AI Assistant Service Cost Comparison Table
3.90
Derivation Chain
Step 1
Proliferation of AI assistant shopping services
→
Step 2
Opaque billing structures for middle-aged users adopting AI assistants
→
Step 3
Actual cost comparison of AI assistant subscriptions and commissions + savings simulator
Problem
When people in their 50s and 60s start shopping with AI assistants (Clova, Kakao, etc.) instead of Naver or Coupang, they find it hard to understand the monthly subscription fees, per-transaction commissions, and the margin structure of recommended products. Many AI assistant services tout 'free', but in reality, 10-15% commissions are embedded in recommended products, leading to an extra 30,000-50,000 KRW (~$22.50-$37.50) in monthly spending without their knowledge.
Solution
The service compares the billing structures of major AI assistant services (Clova, Kakao, Coupang, etc.) in a table. Users input their monthly shopping items and amounts, and the service calculates the actual cost for each service (subscription + commission + price difference) to show which route is cheapest.
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 (77%)
Data Availability
22.5/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 (51/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 [low]
Data Pipeline [medium]