Gig Delivery Driver Per-Transaction Auto Settlement & Withholding Tax Calculation Micro SaaS

4.00

Signal Sources (v8 Triple Source)

Trigger

긱배송 인력풀 매칭·관리 도구

Market

긱배송 인력풀 매칭·관리 도구

Workflow

긱배송 인력풀 매칭·관리 도구 — 온보딩·스케줄링·정산 수작업

Competitor references

No usable source links are available for this idea. Its signal notes and scores need independent verification.

Problem

Small logistics companies use 20–50 gig delivery drivers daily, but settle per-transaction rates, distance weights, and incentives in Excel. Calculation errors in the 3.3% withholding tax occur 2–3 times a month, and delayed settlement dates have led to a 15% driver churn rate.

Solution

Input delivery completion data (via API or CSV) to automatically calculate per-transaction rates, distance, and time-of-day weights, and generate settlement statements per driver reflecting the 3.3% withholding tax. Automatically send settlement details via driver app/KakaoTalk, and batch-print payment statements for tax reporting.

Target: Settlement staff at small logistics companies (20+ gig drivers) / quick-service operators

Revenue Model: Monthly subscription: 50,000 KRW/month (approx. $37.50) for up to 50 drivers / 100,000 KRW/month (approx. $75) for 100+ drivers

Ecosystem Role: -

MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty

3.0/5

U Urgency

4.0/5

M Market

3.0/5

R Realizability

5.0/5

V Validation

4.0/5

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 (81%)

Tech Complexity

40.0/40

Data Availability

21.2/25

MVP Timeline

20.0/20

API Bonus

0.0/15

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)

Competition

8.0/20

Market Demand

6.2/20

Timing

16.0/20

Revenue Signals

10.5/15

Pick-Axe Fit

12.0/15

Solo Buildability

7.0/10

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.

Dashboard