A
C2C Seller Revenue Dashboard
4.25
Derivation Chain
Step 1
Karrot Pay and trust system expansion
→
Step 2
Growth of professional C2C Platform sellers
→
Step 3
Revenue/inventory management tool for professional sellers
→
Step 4
Multi-Platform unified settlement Infrastructure
Problem
Professional secondhand sellers (50+ transactions/month) operating across 2-3 platforms like Karrot, Bunjang, and Jungonara spend 3-4 hours per week manually organizing transaction records in Excel. Different fee structures across platforms make it difficult to track actual net profit, and gathering transaction evidence for Tax filing wastes an additional 10-15 hours annually.
Solution
The tool auto-collects sales records from each C2C Platform (via notification message parsing + app integration) and displays them in a unified dashboard, automatically calculating net profit after deducting platform-specific fees and shipping costs. It generates monthly and category-based profit Reports and provides one-click export of Tax filing documentation for simplified/standard taxation.
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 (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 (69/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
Backend [medium]
Frontend [medium]
Data Pipeline [low]