정비소 CRM·정비이력 통합 SaaS
비즈니스 메시징 SaaS (채널톡, NHN 알림톡 API 존재하나 정비소 워크플로 특화 템플릿 부재)
정비소 사장님이 고객에게 진행 상황 전화 통보, 견적 승인을 구두로 받는 프로세스
Even if a repair shop adopts a CRM, they still have to call customers to update them on the status: 'check-in confirmed → diagnosis complete → in repair → done.' 20-30 calls a day take up 30% of the owner's time. Customers also feel anxious about 'where is my car now?'
When the repair stage changes, automatically send a Kakao AlimTalk (notification) including a quote approval and payment link. Upon completion, automatically send a report with photos. Input: repair status change trigger. Output: AlimTalk sending + payment collection.
| 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. |