# MVP Scope v2: Realistic Timeline

**Date:** November 2, 2025  
**Status:** 🔄 Planning - Based on actual dev capacity  
**Version:** 2.0 (replaces 09-mvp-scope.md)

---

## Current State (Nov 2)

**DONE:**
- ✅ API endpoints for generation
- ✅ Prompt Enhancement (working, always on)
- ✅ 6 Aspect Ratios (Gemini native)
- ✅ MinIO storage connected
- ✅ Web UI base exists

**BLOCKERS:**
- 🔴 DB schema update (2 days)
- 🔴 Endpoints align with DB (2 days)

**Total blockers:** 4 days before new features

---

## Feature Priorities

### Priority A: BLOCKING REVENUE (Must-have for first $ )

**1. Prompt URLs** (3 days after blocker)
- Universal entry point
- Works without MCP/SDK
- Validated by ImageKit success
- Simplest for users

**2. Manual Payments** (1 day)
- Stripe invoice manual
- Email API key
- Track usage manually

**3. Auth basics** (0 days)
- Manual API key generation
- Email to user
- No admin UI needed yet

**TOTAL:** 4 days work  
**TIMELINE:** Week 1 after blockers clear

---

### Priority B: AUTOMATION (Week 2-3)

**4. MCP Server** (3 days)
- Cursor/Claude Code integration
- Primary for Segment B/D
- Differentiator vs stock photos MCP

**5. SDK** (2 days)
- TypeScript/Python
- Programmatic generation
- For technical users

**6. CLI** (2 days)
- Terminal workflows
- Nice-to-have for power users

**7. Automated Payments** (2-3 days)
- Stripe Checkout integration
- Auto API key generation
- Usage tracking

**TOTAL:** 9-10 days work  
**TIMELINE:** Weeks 2-3

---

### Priority C: PRODUCTION (Week 4+)

**8. CDN** (1 day)
- Cloudflare integration
- MinIO → CDN pipeline
- Better performance

**9. Image Transformations** (1 day)
- Service already selected
- Resize, format, optimize

**10. Focal Point Detection** (2-3 days)
- AI determines focus (face, product)
- Smart cropping for aspect ratios
- Quality feature for agencies

**11. Admin UI** (3-5 days)
- API key management
- Usage dashboard
- User management

**TOTAL:** 7-10 days work  
**TIMELINE:** Week 4+

---

### Priority D: POST-MVP (After validation)

**12. @references Consistency System**
- Only if validated need
- Estimate: 1-2 weeks

**13. Team Features**
- For agencies (Segment A)
- Multi-user accounts
- Estimate: 1 week

**14. WordPress Plugin**
- If high demand
- Estimate: 1 week

---

## Non-Tech Requirements (Day 8)

### Landing Page (2 hours)
**Single page with:**
- Hero: "Generate professional images without leaving Cursor"
- What it does: 3 bullet points (enhancement, aspect ratios, CDN)
- Pricing: Free/Credits/Pro (3 lines)
- CTA: Email signup

**Tech:** Single HTML, Tailwind, Vercel deploy

### Documentation (2 hours)
**Single page with:**
- Prompt URLs format + example
- API curl example
- "Email us for API key"

**No:** Advanced usage, troubleshooting, examples library

### Signup Flow (30 min)
- Google Form: Name, Email, Use case
- Auto-reply: "API key within 24h"
- Manual review → Invoice → API key

---

## Launch Sequence

### Week 1: Ultra-Minimal Launch (Experiment)

**This is NOT:**
- ❌ Mass launch (no Product Hunt)
- ❌ Professional site (simple = OK)
- ❌ 100 users goal

**This IS:**
- ✅ Experiment with 3-5 early adopters
- ✅ Validation: will anyone pay?
- ✅ Discovery: which features matter?

**Ready:**
- Prompt URLs (tech)
- Landing page (2h)
- Docs page (2h)
- Signup form (30min)

**Launch to:**
- r/cursor (36K members)
- Discord Cursor channel

**Reddit post template:**
```
Title: Show HN: Generate images in Cursor without context switching

Problem: Stock photos generic. Midjourney = Discord workflow.
Solution: Prompt URLs with AI enhancement.

<img src="banatie.app/gen?prompt=hero+image&aspect=16:9" />

Early access: 10 free images. $20 for 200 after.
Looking for 5-10 early users for feedback.
```

**Goal:** 
- 3-5 people try it
- 1 person pays (any amount)
- Clear feedback pattern

---

### Week 2-3: Developer Tools

**Add:**
- MCP Server
- SDK
- CLI
- Automated payments

**Launch to:**
- Broader developer audience
- Product Hunt (maybe)

**Goal:** 10-20 paying users

---

### Week 4+: Production Features

**Add:**
- CDN
- Transformations
- Focal point
- Admin UI

**Launch to:**
- Agencies (Segment A)
- Broader market

**Goal:** 50+ users, validate segments

---

## Success Metrics by Phase

**Week 1 (Minimal):**
- 3-5 early adopters
- 1-2 paying (any amount)
- Positive feedback on quality

**Week 2-3 (Developer):**
- 10-20 users total
- 5+ paying
- MCP or SDK actively used

**Week 4+ (Production):**
- 50+ users
- 20+ paying
- Clear winner segment identified

---

## Decision Points

**After Week 1:**
- Quality validated? (enhancement working?)
- Willing to pay? (any conversions?)
- GO/PIVOT decision

**After Week 3:**
- Which interface used most? (MCP vs Prompt URLs vs SDK)
- Which segment converts? (B/D vs A/C)
- Double down or adjust

**After Week 4:**
- Is there PMF signal?
- Revenue trajectory clear?
- Scale or rethink

---

## What We're NOT Building (Yet)

❌ @references - no validated demand  
❌ Multiple models - Gemini only  
❌ Complex admin UI - manual OK  
❌ Team features - single user first  
❌ Integrations - API sufficient  
❌ Advanced analytics - basic tracking OK  

**Principle:** Ship fast, validate, iterate

---

## Risks & Mitigation

**Risk:** Complexity creep (want to build everything)  
**Mitigation:** Strict priority system, ship Week 1 no matter what

**Risk:** Payment complexity blocks launch  
**Mitigation:** Manual invoices, automate later

**Risk:** No one wants to pay  
**Mitigation:** Week 1 shows value, pivot if needed

---

## Current Focus (Nov 2-6)

**Days 1-2:** Clear DB blocker  
**Days 3-4:** Endpoint alignment  
**Days 5-7:** Prompt URLs  
**Day 8:** Manual payment setup  

**Target:** Launch-ready by Nov 9-10

---

**Owner:** Oleg  
**Last updated:** November 2, 2025  
**Next review:** After Week 1 launch