B
Solo Biz Monthly Statement
3.20
Derivation Chain
Step 1
Solo business digital operations
→
Step 2
Managing revenue, expenses, and Tax in one place
→
Step 3
Instant 'how much did I actually earn this month' view at month-end
Problem
Small Business Owners aged 55–65 who started a business after Retirement (cafe, academy, online shop) spend 3–5 hours each month-end trying to figure out 'how much did I actually earn this month.' They must manually retrieve and sum up delivery app settlements, card payment settlements, cash receipt records, maintenance fees, labor costs, and VAT prepayments from separate websites. Missed expenses lead to penalty surcharges during Tax filing, or—worse—they unknowingly operate at a loss for 2–3 months.
Solution
Collects card processor, delivery app, and cash receipt settlement data via manual input (CSV upload) or email statement parsing. Users register monthly fixed costs (rent, labor, maintenance), and the system produces a single monthly statement showing 'Net profit = Total revenue – Total expenses – Estimated Tax.' Immediate alerts when the business turns to a loss.
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 (69%)
Data Availability
19.4/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 (60/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 [medium]
Data Pipeline [low]