세무사무소 기장자동화 워크플로우
전자세금계산서 API 연동 미들웨어
세무사무소→고객사 간 매월 자료요청·수집·독촉 수작업 병목
Tax office employees spend 30% of their average working hours individually requesting and chasing supporting documents from 50–200 client companies each month. With the expansion of mandatory electronic tax invoices, the number of transactions increases, but document collection still relies on manual work via KakaoTalk and email.
Send automated document request links per client → upload portal → automatic reminders for non-submission → upon completion, integrate and send to accounting software. Input: client list and request item templates. Output: collection status dashboard and automatic accounting software integration.
| 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. |
| 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. |
| 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. |