docs(10_Wiki): 위키 전체 재구성 — Topic_* 폴더를 4개 카테고리로 통합 + 대규모 중복 제거

Topic_Agent/Topic_Blog/Topics/Topics_Biz/Topics_Meeting/Topics_Rag의 마크다운 지식 문서를
Topic_General/Topic_Programming/Topic_Graphic/Topic_Business 4개 카테고리로 재분류.

- 중복 제거: frontmatter의 status:duplicate/merged + duplicate_of/redirect_to 필드로
  자기 자신을 중복으로 선언한 리다이렉트 stub 1032개 제거, 완전 동일 내용 파일 472개 제거,
  동일 파일명·다른 내용 충돌 시 더 큰(완전한) 버전만 유지(162개 제거) — 총 1639개 중복 제거.
- 분류: 폴더 단위로 명확한 항목(AI_and_ML/Coding/Architecture 등 → Programming,
  Comfyui/Visual_Effects → Graphic, Topics_Biz/Topics_Meeting/사업 등 → Business,
  Poetic_Blog_Writing/창의성/Game_Design 등 → General)은 폴더 우선순위로,
  나머지 혼재 폴더(Topic_Agent/Topic_Blog/Topics 루트/Thinking & Reasoning/Other/UI_UX_Assets)는
  title/tags 키워드 스코어링으로 파일 단위 분류(불명확한 경우 General로 폴백).
  원본 폴더명은 "From_*" 서브폴더로 보존해 추적 가능성 유지.
- 최종 배치: Programming 2784 / General 1608 / Graphic 285 / Business 249 = 4926개 문서.
- 에이전트 운영 상태(.astra/.agent/.obsidian/sessions/memory/_company/docs/lessons/_shared/src)는
  지식 콘텐츠가 아니므로 재분류 대상에서 제외하고 원위치 유지.
- Topics/Topic_email(상위 보호 폴더 Topic_email과 파일명 100% 중복) 삭제 — 보호 폴더 자체는 미변경.
- 완전히 비게 된 Topic_Agent/Topic_Blog/Topics_Biz/Topics_Rag 폴더 제거.
This commit is contained in:
Antigravity Agent
2026-07-05 00:33:48 +09:00
parent 1cfd3bbb56
commit 9148c358d0
6455 changed files with 1 additions and 86875 deletions
@@ -0,0 +1,204 @@
---
id: wiki-2026-0508-startup
title: Startup
category: 10_Wiki/Topics
status: verified
canonical_id: self
aliases: [Lean Startup, Startup Methodology, 스타트업]
duplicate_of: none
source_trust_level: A
confidence_score: 0.9
verification_status: applied
tags: [startup, lean, mvp, customer-development, ai-startup]
raw_sources: []
last_reinforced: 2026-05-10
github_commit: pending
tech_stack:
language: english-korean
framework: lean-startup
---
# Startup
## 매 한 줄
> **"매 startup = search for repeatable + scalable business model"**. Steve Blank 의 customer development + Eric Ries 의 Lean Startup 이 base. 2026 AI wave 에선 매 1인 founder 가 Claude/Cursor 로 prototype → seed 까지 < 30 일 의 cycle.
## 매 핵심
### 매 기본 정의 (Blank/Ries)
- **Startup** ≠ 매 small business. 매 "search for repeatable, scalable, profitable business model" 하 temporary org.
- **Customer Development** (Blank): Get-out-of-the-building, Customer Discovery → Validation → Creation → Building.
- **Lean Startup** (Ries): BuildMeasureLearn loop, MVP, validated learning, pivot or persevere.
### 매 stages
- **Pre-seed** ($100K~$2M): idea + founders. 2026 AI prototype demo 기본.
- **Seed** ($1M~$5M): PMF 탐색. 매 design partner 510 개.
- **Series A** ($5M~$25M): PMF 입증 + GTM scale.
- **Series B+**: scale operations, geographic/category expansion.
### 매 PMF (Product-Market Fit)
- Sean Ellis test: "How disappointed if product disappeared?" — 40%+ "very" → PMF signal.
- Retention curve flat → PMF. Churning curve → 매 not yet.
- Andreessen: "you can always feel PMF when it's happening."
### 매 2026 AI Startup wave
- **Solo / 2-person AI startup**: Cursor/Claude Code 로 1 founder 가 full-stack ship. ARR $1M+ < 12 개월 사례 다수.
- **Vertical AI agents**: 법률 (Harvey), 회계 (Pilot+AI), 의료 scribe (Abridge), 영업 (11x.ai).
- **Foundation model wrapper risk**: GPT-5 / Claude Opus 4.7 / Gemini 3 가 직접 feature 흡수. Moat = data/distribution/workflow integration.
- **AI-native pricing**: per-task, per-outcome (success-based), per-agent-seat. 매 traditional per-seat SaaS 의 위협.
## 💻 패턴
### MVP 가설 worksheet (Lean Canvas style)
```markdown
## Problem (top 3)
1. ...
## Customer Segments
- Early adopter: ...
- Mainstream: ...
## Unique Value Prop
"<X> for <segment> who <pain>"
## Solution (top 3 features)
1. ...
## Channels
- ...
## Revenue Streams
- ...
## Cost Structure
- ...
## Key Metrics (AARRR)
- Acquisition / Activation / Retention / Referral / Revenue
## Unfair Advantage
- ...
```
### Customer interview template
```markdown
# Discovery Interview (30 min)
## Warm-up
- Tell me about your role + day-to-day.
## Problem (no pitching!)
- Walk me through last time you <did task>.
- What was hardest part? Why?
- What did you do to solve it? (existing workarounds)
- How much time/money does <pain> cost?
## Solution probe (only after problem confirmed)
- If a tool did <X>, how would you use it?
- Who else needs to be involved in buying decision?
## Close
- Who else should I talk to?
- Can I follow up in 2 weeks?
```
### MVP build (2026 AI startup stack)
```bash
# Day 03: validate pain via 10 interviews
# Day 410: prototype with Claude Code + v0 + Supabase
pnpm create next-app@latest mvp --typescript --tailwind --app
cd mvp
pnpm add @supabase/ssr ai @ai-sdk/anthropic
# Day 1114: 5 design partner deploy via Vercel
vercel deploy --prod
# Day 15+: weekly BuildMeasureLearn cycle
```
### BuildMeasureLearn loop
```typescript
// 매 weekly cycle 의 instrumentation
import { track } from "@vercel/analytics";
export async function onUserAction(action: string, props: object) {
await track(action, props); // PostHog/Mixpanel/Amplitude
}
// Measure: cohort retention, activation funnel
// Learn: 매 weekly 5-customer call → hypothesis update
// Build: 매 1 hypothesis test per sprint
```
### PMF metric dashboard (PostHog SQL)
```sql
-- Sean Ellis-style retention cohort
SELECT
date_trunc('week', signup_at) AS cohort,
COUNT(DISTINCT user_id) FILTER (WHERE active_in_week_4) * 1.0
/ COUNT(DISTINCT user_id) AS w4_retention
FROM users
GROUP BY 1
ORDER BY 1 DESC;
-- 매 30%+ flat W4 retention = PMF candidate
```
### Pivot decision matrix
```python
# 매 "pivot or persevere" — Ries
def pivot_signal(metrics):
# No traction after 3 build-measure-learn cycles?
if metrics.weekly_active_growth < 0.05 and metrics.cycles >= 3:
return "PIVOT"
if metrics.retention_w4 > 0.30 and metrics.organic_share > 0.20:
return "PERSEVERE / SCALE"
return "CONTINUE LEARNING"
```
### Fundraising data room essentials (2026)
```markdown
## Seed Data Room
- Pitch deck (10-12 slides, Sequoia/YC format)
- 매 financial model (3-year, monthly first 12mo)
- KPI dashboard (live link to Mixpanel/PostHog)
- Customer letters / testimonials (5+)
- Cap table (Carta export)
- 매 incorporation docs (Delaware C-Corp)
- IP assignment, founder agreements
- AI compliance: 매 SOC2 Type 1 progress, EU AI Act risk class
```
## 매 결정 기준
| 상황 | Approach |
|---|---|
| 매 Idea 단계 | Customer Discovery 만, 매 build 전 10+ interview |
| Prototype 후 traction X | Lean iteration, 매 pivot 고려 |
| 매 Seed 단계, design partner 확보 | Validation: contract / LOI 5+ |
| Series A 준비 | Repeatable sales motion 입증 (CAC payback < 18mo) |
| AI wrapper 우려 | Workflow integration + proprietary data moat 의 강화 |
**기본값**: 매 Lean Startup + Customer Development 결합 — 매 BuildMeasureLearn weekly cadence.
## 🔗 Graph
- 부모: [[Business-Strategy]]
- 변형: [[Lean Startup]]
- 응용: [[MVP]]
## 🤖 LLM 활용
**언제**: 매 idea validation, customer interview synthesis, pitch deck draft, KPI dashboard SQL 작성, market sizing (TAM/SAM/SOM).
**언제 X**: 매 hard customer signal 의 대체 X — 매 LLM 가 진짜 customer pain 의 hallucinate 가능. 매 actual interviews irreplaceable.
## ❌ 안티패턴
- **Build first, validate later**: 매 6개월 build → 매 nobody wants. Customer dev 가 먼저.
- **Vanity metrics**: signup count, page view 만 추적 — 매 retention/revenue 의 무시.
- **매 foundermarket mismatch**: domain 의 unfamiliar — design partner 의 trust 약화.
- **AI wrapper without moat**: GPT-5 / Claude API call only → foundation model 이 흡수 시 사라짐.
- **Premature scaling** (Marmer): PMF 전 매 sales team 의 hire — 매 burn rate 폭주.
## 🧪 검증 / 중복
- Verified (Steve Blank "Four Steps to the Epiphany", Eric Ries "Lean Startup", YC startup library 2026).
- 신뢰도 A.
## 🕓 Changelog
| 날짜 | 변경 |
|---|---|
| 2026-05-08 | Phase 1 |
| 2026-05-10 | Manual cleanup — Lean/Customer Dev + 2026 AI startup wave 정리 |