B
Small Business Daily Settlement Dashboard
3.30
Derivation Chain
Step 1
Lack of small business DT tools
→
Step 2
Inability to track daily revenue/expenses
→
Step 3
Organizing card settlement dates, fees, and VAT prepayments on a daily basis
Problem
Restaurant and Cafe owners in their 50s don't know exactly 'how much they made today' after each business day. Card payments settle 2–3 days later, VAN provider fees vary, and delivery app settlement cycles all differ—so they give up trying to track it manually in spreadsheets. Until they hand their books to the tax accountant each month, they operate without knowing actual profits and recognize cash flow shortfalls too late.
Solution
Automatically parses card company and delivery app sales notification texts/emails to show 'yesterday's actual profit' on a single screen every morning. Core features: (1) Integrated daily settlement sheet covering card sales, delivery apps, and cash revenue, (2) Automatic net profit calculation after deducting fees, VAT prepayment, rent, and other fixed costs, (3) Weekly/monthly trend charts with cash shortage forecast alerts.
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 (62%)
Data Availability
18.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 (56/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 [medium]