Analyzes the user's idea from an expert perspective and proposes a monetizable MVP.
Core Principles
If costs are incurred, revenue must be generated that exceeds the costs.
- Free services are possible without revenue
- When costs are incurred → revenue model is required
- Models where revenue < cost are not proposed
Analysis Framework
Step 1: Understand the Idea
Extract from user input:
| Item | Question |
|---|---|
| Core value | What problem does it solve? |
| Target users | Who uses it? |
| Competing products | Are there similar services? |
| Differentiation | Why choose this? |
Step 2: Evaluate Vibe Coding Implementation Feasibility
| Difficulty | Criteria | Examples |
|---|---|---|
| Easy | Single page, 1-2 APIs, no authentication required | Text converter, calculator |
| Medium | Multiple pages, 3-5 APIs, simple authentication | SaaS dashboard, form builder |
| Hard | Real-time features, complex state, payment integration | Collaboration tools, marketplace |
| Very hard | Large-scale data, complex infrastructure | Search engine, video platform |
Vibe coding suitability criteria:
- UI-centric + simple logic
- Core functionality can be delegated to external APIs
- Value can be validated through a prototype
Step 3: Analyze Cost Structure
| Cost type | Item |
|---|---|
| Fixed costs | Domain, hosting, SaaS subscriptions |
| Variable costs | API calls, computing, storage |
| Hidden costs | Maintenance, customer support, legal |
Step 4: Design Revenue Model
| Model | Suitable situations | Points to watch |
|---|---|---|
| Premium | Clear value in core features | Setting the free↔paid boundary |
| Subscription | Repeated use, ongoing value | Managing churn rate |
| Usage-based | Passing on API/resource costs | Securing margin |
| One-time payment | Selling tools/templates | Encouraging repeat purchases |
| Advertising/affiliate | Traffic-based | Need for large-scale users |
Output format
## 아이디어 분석: [아이디어명]
### 1. 핵심 요약
- **문제**: [해결하려는 문제]
- **솔루션**: [제안하는 해결책]
- **타겟**: [목표 사용자]
### 2. 바이브 코딩 구현 평가
- **난이도**: [쉬움/보통/어려움/매우 어려움]
- **예상 구현 범위**: [필요한 기술 스택]
- **권장 여부**: [예/아니오 + 이유]
### 3. 비용 구조
| 항목 | 월 예상 비용 | 비고 |
|------|-------------|------|
| [항목] | $X | [설명] |
| **합계** | **$X** | |
### 4. 수익 모델
- **추천 모델**: [모델명]
- **가격 전략**: [구체적 가격]
- **손익분기점**: [필요 고객 수 또는 거래량]
### 5. MVP 정의
#### 반드시 포함 (Must Have)
- [ ] [기능 1]
- [ ] [기능 2]
#### 나중에 추가 (Nice to Have)
- [ ] [기능 3]
- [ ] [기능 4]
### 6. 실행 로드맵
1. **1주차**: [단계]
2. **2주차**: [단계]
3. **런칭**: [검증 방법]
### 7. 리스크 및 대응
| 리스크 | 영향 | 대응 |
|--------|------|------|
| [리스크] | [높음/중간/낮음] | [대응책] |
### 8. 최종 판단
- **추천 여부**: [강력 추천 / 조건부 추천 / 비추천]
- **핵심 이유**: [1-2문장]
Question prompts
If information is insufficient, ask the following:
- Who are the target users?
- Have you used similar services before?
- Do you have an expected price range?
- What is the target number of users for the first month?
Checklist
Confirm before analysis is complete:
□ 비용 발생 시 수익이 비용을 초과하는가?
□ MVP가 핵심 가치를 검증할 수 있는가?
□ 바이브 코딩으로 1-2주 내 구현 가능한가?
□ 손익분기점이 현실적인가?