파운드리
Day One — Journal Collections for organizing separate records
inferred: 반도체 공급사 품질담당자 — 고객사별 인증 증빙을 반복 수집하고 제출 형식에 맞게 재편집
Quality teams at semiconductor equipment and materials suppliers repeatedly repackage certificates, inspection reports, change approvals, and corrective-action records to meet each customer's format. Because document versions and expiration dates are tracked in spreadsheets, missing records may not be discovered until shortly before an audit.
The service organizes evidence stored in Drive or SharePoint into collections by customer, process, part number, and validity period, then automatically creates submission packages and renewal tasks. It records customer-specific requirements and actual rejection reasons to improve missing-document checks for future submissions.
| 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. |