Compare commits
No commits in common. "master" and "research" have entirely different histories.
90
INDEX.md
90
INDEX.md
|
|
@ -1,8 +1,8 @@
|
||||||
# Banatie Strategy Documentation Index
|
# Banatie Strategy Documentation Index
|
||||||
|
|
||||||
**Last Updated:** January 9, 2026
|
**Last Updated:** January 2, 2026
|
||||||
**Total Documents:** 22 (numbered in strategy/execution) + research (prefixed) + content
|
**Total Documents:** 20 (numbered in strategy/execution) + research (prefixed)
|
||||||
**Next Available Number:** 22
|
**Next Available Number:** 20
|
||||||
**Project Stage:** Pre-launch / MVP Development
|
**Project Stage:** Pre-launch / MVP Development
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
@ -15,7 +15,6 @@
|
||||||
- Deleted documents don't free up numbers
|
- Deleted documents don't free up numbers
|
||||||
- **Exception:** `discussions/` uses date-based format (YYYY-MM-DD-topic.md)
|
- **Exception:** `discussions/` uses date-based format (YYYY-MM-DD-topic.md)
|
||||||
- **Exception:** `research/` uses flat structure with prefixes (direction-, signals-, analysis-, seo-)
|
- **Exception:** `research/` uses flat structure with prefixes (direction-, signals-, analysis-, seo-)
|
||||||
- **Exception:** `content/` uses descriptive names (CONTENT-TRACKS.md)
|
|
||||||
|
|
||||||
**Currently Used:**
|
**Currently Used:**
|
||||||
- 01 - Market Positioning
|
- 01 - Market Positioning
|
||||||
|
|
@ -36,10 +35,8 @@
|
||||||
- 18 - Production Infrastructure
|
- 18 - Production Infrastructure
|
||||||
|
|
||||||
- 19 - Placeholder SEO Sprint
|
- 19 - Placeholder SEO Sprint
|
||||||
- 20 - Template System
|
|
||||||
- 21 - Validation Approaches
|
|
||||||
|
|
||||||
**Next to assign:** 22
|
**Next to assign:** 20
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
|
|
@ -62,8 +59,7 @@
|
||||||
- [Validation Plan](execution/08-validation-plan.md)
|
- [Validation Plan](execution/08-validation-plan.md)
|
||||||
|
|
||||||
**For SEO & Content:** ⭐ ACTIVE
|
**For SEO & Content:** ⭐ ACTIVE
|
||||||
- [Content Tracks](content/CONTENT-TRACKS.md) - SEO-First + Product-First strategy ⭐ NEW
|
- [Placeholder SEO Sprint](execution/19-placeholder-seo-sprint.md) - Current sprint plan ⭐
|
||||||
- [Placeholder SEO Sprint](execution/19-placeholder-seo-sprint.md) - Current sprint plan
|
|
||||||
- [SEO Keyword Research: Placeholder Images](research/seo-keyword-research-placeholder-images.md) - Entry point cluster
|
- [SEO Keyword Research: Placeholder Images](research/seo-keyword-research-placeholder-images.md) - Entry point cluster
|
||||||
- [Research Index](research/INDEX.md) - All research documentation
|
- [Research Index](research/INDEX.md) - All research documentation
|
||||||
|
|
||||||
|
|
@ -148,39 +144,6 @@ Status: ✅ Validated - One product, multiple entry points
|
||||||
Key insight: Direction 1 (Agencies) + Direction 2 (AI Developers) = SAME product
|
Key insight: Direction 1 (Agencies) + Direction 2 (AI Developers) = SAME product
|
||||||
Segments: A (Studios/Agencies), B (Power Users - PRIMARY), C (Freelancers), D (AI-Savvy Freelancers - SECONDARY)
|
Segments: A (Studios/Agencies), B (Power Users - PRIMARY), C (Freelancers), D (AI-Savvy Freelancers - SECONDARY)
|
||||||
|
|
||||||
**[Positioning Updates Jan 2026](strategy/positioning-updates-jan-2026.md)** (Jan 9, 2026) ⭐ NEW
|
|
||||||
*Critical positioning changes summary*
|
|
||||||
Status: ✅ Reference document
|
|
||||||
Covers: MCP/SDK/CLI = table stakes, Template System reframe, 70/30 allocation, Validation approaches
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## 📝 Content Strategy ⭐ NEW
|
|
||||||
|
|
||||||
**[CONTENT-TRACKS.md](content/CONTENT-TRACKS.md)** (Jan 9, 2026)
|
|
||||||
*Two parallel content strategies: SEO-First + Product-First*
|
|
||||||
Status: 🔄 Active
|
|
||||||
Source: Keyword research ($3.60 DataForSEO) + strategic discussion
|
|
||||||
|
|
||||||
**SEO-First Track:**
|
|
||||||
- Placeholder Images API (14,800 vol, KD 32) — 🔥 HIGH
|
|
||||||
- Midjourney Alternatives (1,300 vol, KD 3) — 🔥 URGENT
|
|
||||||
- Dark Mode Placeholders (4,400 vol, KD 2) — MEDIUM
|
|
||||||
- Advertising Images (1,600 vol, KD 4) — needs SERP validation
|
|
||||||
|
|
||||||
**Product-First Track:**
|
|
||||||
- Live URLs Guide — 🔥 HIGH (core feature)
|
|
||||||
- Claude Code + Banatie Workflow — 🔥 HIGH (ICP content)
|
|
||||||
- Cursor Image Generation — HIGH (blocked by MCP)
|
|
||||||
- MCP APIs Compared — MEDIUM
|
|
||||||
- Vibecoding Tutorial — MEDIUM (future SEO bet)
|
|
||||||
|
|
||||||
**Related files in banatie-content:**
|
|
||||||
- `0-inbox/placeholder-images-api.md`
|
|
||||||
- `0-inbox/midjourney-alternatives-developers.md`
|
|
||||||
- `0-inbox/claude-code-image-generation-mcp.md`
|
|
||||||
- `research/keywords/research-report-2026-01-09.md`
|
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
## 🎯 Execution Documents
|
## 🎯 Execution Documents
|
||||||
|
|
@ -241,16 +204,6 @@ Status: 🔄 Active Sprint
|
||||||
Tracks: Landing page `/placeholder-images`, Docs `/docs/placeholders/`, Homepage quick wins
|
Tracks: Landing page `/placeholder-images`, Docs `/docs/placeholders/`, Homepage quick wins
|
||||||
Target: Zero-KD keywords + 14,800 vol main keyword
|
Target: Zero-KD keywords + 14,800 vol main keyword
|
||||||
|
|
||||||
**[20 - Template System](execution/20-template-system.md)** (Jan 9, 2026)
|
|
||||||
*Reframed "Prompt Enhancement" as Template System*
|
|
||||||
Status: ✅ Strategic decision documented
|
|
||||||
Key: Granular enhancement, default = Photorealistic, Custom Templates = Pro paid feature
|
|
||||||
|
|
||||||
**[21 - Validation Approaches](execution/21-validation-approaches.md)** (Jan 9, 2026)
|
|
||||||
*Catalog of 8 validation approaches with pros/cons*
|
|
||||||
Status: ✅ Reference document
|
|
||||||
Best balance: Discord AI Tools (⭐⭐⭐, 1-2 weeks)
|
|
||||||
|
|
||||||
### Technical Documentation
|
### Technical Documentation
|
||||||
|
|
||||||
**[12 - Current Tech State](execution/12-the-current-tech-state.md)** (v1.0, Nov 1)
|
**[12 - Current Tech State](execution/12-the-current-tech-state.md)** (v1.0, Nov 1)
|
||||||
|
|
@ -276,12 +229,11 @@ Key: Platform mostly production-ready, gaps identified
|
||||||
- ✅ Reusable methodology documented
|
- ✅ Reusable methodology documented
|
||||||
- ✅ ICP refined to A/B/C/D segments
|
- ✅ ICP refined to A/B/C/D segments
|
||||||
|
|
||||||
**SEO Research Phase (Dec 26, 2025 - Jan 9, 2026):** ⭐ UPDATED
|
**SEO Research Phase (Dec 26, 2025):** ⭐ NEW
|
||||||
- ✅ DataForSEO MCP Server integrated
|
- ✅ DataForSEO MCP Server integrated
|
||||||
- ✅ Placeholder images cluster validated (14.8K vol, KD 32)
|
- ✅ First keyword cluster researched ("placeholder images")
|
||||||
- ✅ AI coding keywords = 0 volume (problem-aware ≠ search behavior)
|
- ✅ Content plan with 5 articles defined
|
||||||
- ✅ Two-track content strategy defined (SEO + Product)
|
- ⏳ Additional clusters pending
|
||||||
- ✅ SERP analysis completed for top keywords
|
|
||||||
|
|
||||||
**Primary Finding:** Direction 2 (AI Coding Agents) = ⭐ 70-80% confidence
|
**Primary Finding:** Direction 2 (AI Coding Agents) = ⭐ 70-80% confidence
|
||||||
- [direction-2-strong-signals-part2.md](research/direction-2-strong-signals-part2.md) - Complete research
|
- [direction-2-strong-signals-part2.md](research/direction-2-strong-signals-part2.md) - Complete research
|
||||||
|
|
@ -362,9 +314,9 @@ ROADMAP.md → 02-reality-check.md → 14-icp-segmentation-unified.md → 17-wee
|
||||||
15-mvp-scope-v2-realistic.md → 16-product-features.md → 17-week-1-launch-checklist.md
|
15-mvp-scope-v2-realistic.md → 16-product-features.md → 17-week-1-launch-checklist.md
|
||||||
```
|
```
|
||||||
|
|
||||||
### For SEO & Content (UPDATED):
|
### For SEO & Content (NEW):
|
||||||
```
|
```
|
||||||
content/CONTENT-TRACKS.md → research/seo-keyword-research-*.md → banatie-content/0-inbox/
|
research/seo-keyword-research-*.md → ROADMAP.md (Content Sprint) → blog articles
|
||||||
```
|
```
|
||||||
|
|
||||||
### Legacy path (archived):
|
### Legacy path (archived):
|
||||||
|
|
@ -402,13 +354,8 @@ content/CONTENT-TRACKS.md → research/seo-keyword-research-*.md → banatie-con
|
||||||
- Direction 1 + 2 = same product, different entry points
|
- Direction 1 + 2 = same product, different entry points
|
||||||
- Prompt Enhancement as PRIMARY MOAT (3-6 months to replicate)
|
- Prompt Enhancement as PRIMARY MOAT (3-6 months to replicate)
|
||||||
|
|
||||||
**Content Tracks (content/) drives:** ⭐ NEW
|
**SEO Research (research/seo-*) drives:** ⭐ NEW
|
||||||
- SEO-First: Landing pages, docs, blog posts for traffic
|
- Content Marketing Sprint (ROADMAP.md)
|
||||||
- Product-First: Core docs, tutorials for conversion
|
|
||||||
- Links to briefs in banatie-content/0-inbox/
|
|
||||||
|
|
||||||
**SEO Research (research/seo-*) informs:**
|
|
||||||
- Content Tracks (content/CONTENT-TRACKS.md)
|
|
||||||
- Landing page creation (website)
|
- Landing page creation (website)
|
||||||
- Blog content strategy (dev.to, Hashnode)
|
- Blog content strategy (dev.to, Hashnode)
|
||||||
|
|
||||||
|
|
@ -449,16 +396,11 @@ content/CONTENT-TRACKS.md → research/seo-keyword-research-*.md → banatie-con
|
||||||
- Marketing campaigns
|
- Marketing campaigns
|
||||||
- Sales processes
|
- Sales processes
|
||||||
|
|
||||||
**Content strategy** → `content/` ⭐ NEW
|
|
||||||
- Content tracks and priorities
|
|
||||||
- SEO vs Product content plans
|
|
||||||
- Editorial calendars
|
|
||||||
|
|
||||||
**Research findings** → `research/` (use prefixes)
|
**Research findings** → `research/` (use prefixes)
|
||||||
- `direction-N-*.md` - Research directions
|
- `direction-N-*.md` - Research directions
|
||||||
- `signals-*.md` - Strong signals found
|
- `signals-*.md` - Strong signals found
|
||||||
- `analysis-*.md` - Strategic analysis
|
- `analysis-*.md` - Strategic analysis
|
||||||
- `seo-keyword-research-*.md` - SEO keyword research
|
- `seo-keyword-research-*.md` - SEO keyword research ⭐ NEW
|
||||||
- `methodology-*.md` - Research methods (if needed)
|
- `methodology-*.md` - Research methods (if needed)
|
||||||
|
|
||||||
**Session summaries** → `discussions/` (date-based: YYYY-MM-DD-topic.md)
|
**Session summaries** → `discussions/` (date-based: YYYY-MM-DD-topic.md)
|
||||||
|
|
@ -484,5 +426,5 @@ content/CONTENT-TRACKS.md → research/seo-keyword-research-*.md → banatie-con
|
||||||
---
|
---
|
||||||
|
|
||||||
**Last maintained by:** @men
|
**Last maintained by:** @men
|
||||||
**Version:** 4.5 (Content Tracks added Jan 9, 2026)
|
**Version:** 4.3 (Placeholder SEO Sprint added Jan 2, 2026)
|
||||||
**Next review:** After content execution begins
|
**Next review:** End of Placeholder SEO Sprint (mid-January 2026)
|
||||||
|
|
|
||||||
|
|
@ -1,380 +0,0 @@
|
||||||
# Content Tracks: SEO-First & Product-First
|
|
||||||
|
|
||||||
**Date Created:** January 9, 2026
|
|
||||||
**Purpose:** Two parallel content strategies for Banatie
|
|
||||||
**Status:** Active
|
|
||||||
**Source:** Keyword research ($3.60 DataForSEO) + strategic discussion
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Overview
|
|
||||||
|
|
||||||
Два параллельных трека контента:
|
|
||||||
|
|
||||||
| Track | Цель | Измерение успеха |
|
|
||||||
|-------|------|------------------|
|
|
||||||
| **SEO-First** | Трафик, domain authority, ранжирование | Позиции в Google, organic traffic |
|
|
||||||
| **Product-First** | Conversion, validation, brand positioning | User engagement, signups, feedback |
|
|
||||||
|
|
||||||
**Принцип:** SEO-first даёт трафик. Product-first конвертит и валидирует. Оба нужны параллельно.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## TRACK 1: SEO-FIRST
|
|
||||||
|
|
||||||
**Цель:** Low-hanging SEO fruits. Начать ранжироваться сейчас → результаты через 3-6 месяцев.
|
|
||||||
|
|
||||||
### Validated Opportunities
|
|
||||||
|
|
||||||
| # | Контент | Volume | KD | Тип | Приоритет | Brief |
|
|
||||||
|---|---------|--------|----|----|-----------|-------|
|
|
||||||
| 1 | **Placeholder Images API** | 14,800 | 32 | Landing + Guide | 🔥 HIGH | `0-inbox/placeholder-images-api.md` |
|
|
||||||
| 2 | **Midjourney Alternatives for Developers** | 1,300 | 3 | Listicle | 🔥 URGENT | `0-inbox/midjourney-alternatives-developers.md` |
|
|
||||||
| 3 | **Dark Mode Placeholder Images** | 4,400 | 2 | Docs section | MEDIUM | Data в `research/keywords/placeholder-niche-deep-dive-2026-01-02.md` |
|
|
||||||
| 4 | **Advertising Images Guide** | 1,600 | 4 | Guide | MEDIUM | `0-inbox/advertising-images-guide.md` — нужна SERP validation |
|
|
||||||
|
|
||||||
### Needs SERP Validation
|
|
||||||
|
|
||||||
| Keyword | Volume | KD | Риск |
|
|
||||||
|---------|--------|----|------|
|
|
||||||
| marketing images | 2,900 | 19 | Может быть stock photo intent |
|
|
||||||
| social media images | 1,900 | 14 | Может быть stock photo intent |
|
|
||||||
| blog images | 720 | 7 | Низкий риск |
|
|
||||||
|
|
||||||
### Include as Sections (не standalone)
|
|
||||||
|
|
||||||
| Keyword | Volume | KD | Где включить |
|
|
||||||
|---------|--------|----|--------------|
|
|
||||||
| test images | 6,600 | 9 | H2 в Placeholder guide |
|
|
||||||
| lorem picsum | 880 | 15 | Comparison в Placeholder |
|
|
||||||
| placeholder api | 880 | 28 | Placeholder guide |
|
|
||||||
|
|
||||||
### Skip (validated as wrong intent)
|
|
||||||
|
|
||||||
| Keyword | Volume | Причина |
|
|
||||||
|---------|--------|---------|
|
|
||||||
| banner images | 27,100 | Stock photo intent, dominated by Unsplash/Adobe |
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
### SEO Content Details
|
|
||||||
|
|
||||||
#### 1. Placeholder Images API (PRIMARY)
|
|
||||||
|
|
||||||
**Target:** `/placeholder-images` landing page
|
|
||||||
|
|
||||||
**Keywords cluster:**
|
|
||||||
- placeholder images (14,800)
|
|
||||||
- placeholder api (880)
|
|
||||||
- lorem picsum (880) — comparison
|
|
||||||
- dummy images (720)
|
|
||||||
- test images (6,600) — as section
|
|
||||||
|
|
||||||
**SERP Validation:** ✅
|
|
||||||
- "AI placeholder images" в related searches
|
|
||||||
- Competitors beatable (placehold.co, Lorem Picsum)
|
|
||||||
- 100% developer intent
|
|
||||||
|
|
||||||
**Differentiation:**
|
|
||||||
| Feature | placehold.co | Lorem Picsum | Banatie |
|
|
||||||
|---------|--------------|--------------|---------|
|
|
||||||
| Real images | ❌ | ✓ (random) | ✓ (contextual) |
|
|
||||||
| AI-generated | ❌ | ❌ | ✓ |
|
|
||||||
| Prompt-based | ❌ | ❌ | ✓ |
|
|
||||||
| Live URLs | ❌ | ❌ | ✓ |
|
|
||||||
|
|
||||||
**Content structure:**
|
|
||||||
1. What are placeholder images (answer base intent)
|
|
||||||
2. Best placeholder image services (comparison)
|
|
||||||
3. AI Placeholder Images: Next Generation (our pitch)
|
|
||||||
4. Getting started with Banatie Live URLs
|
|
||||||
5. Code examples (HTML, React, Next.js)
|
|
||||||
|
|
||||||
**Outreach opportunity:** loremipsum.io ranks with "15 Best Placeholder Generators" — get listed.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
#### 2. Midjourney Alternatives for Developers (URGENT)
|
|
||||||
|
|
||||||
**Target:** Blog post (dev.to, cross-post)
|
|
||||||
|
|
||||||
**Why urgent:** Volume declining rapidly (8.1K → 1.3K). Window closing.
|
|
||||||
|
|
||||||
**Keywords:**
|
|
||||||
- midjourney alternative (1,300, KD 3)
|
|
||||||
- midjourney api (720, KD 35)
|
|
||||||
- ai image generator api (590, KD 32)
|
|
||||||
|
|
||||||
**Angle:** "5 Midjourney Alternatives with API Access for Developers"
|
|
||||||
|
|
||||||
**Include competitors:**
|
|
||||||
- Replicate
|
|
||||||
- fal.ai
|
|
||||||
- Runware
|
|
||||||
- DALL-E API
|
|
||||||
- Banatie (our positioning)
|
|
||||||
|
|
||||||
**Key message:** Midjourney = Discord-only, no API. Developers need programmatic access.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
#### 3. Dark Mode Placeholder Images
|
|
||||||
|
|
||||||
**Target:** `/docs/placeholders/dark-mode`
|
|
||||||
|
|
||||||
**Keywords:**
|
|
||||||
- image placeholder dark (4,400, KD 2)
|
|
||||||
- placeholder image dark (1,300, KD 6)
|
|
||||||
|
|
||||||
**Why separate:** Combined 5.7K volume, ultra-low KD. Easy win.
|
|
||||||
|
|
||||||
**Content:** How to generate dark-mode-friendly placeholders with Live URLs.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
#### 4. Advertising Images Guide
|
|
||||||
|
|
||||||
**Target:** Blog post or guide
|
|
||||||
|
|
||||||
**Keywords:**
|
|
||||||
- advertising images (1,600, KD 4)
|
|
||||||
- promotional images (880, KD 17)
|
|
||||||
|
|
||||||
**Status:** Needs SERP validation before writing. Could be stock photo intent like "banner images".
|
|
||||||
|
|
||||||
**Angle if validated:** "How developers can generate advertising images programmatically"
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## TRACK 2: PRODUCT-FIRST
|
|
||||||
|
|
||||||
**Цель:** Core product positioning, conversion, validation. Нужно независимо от SEO volume.
|
|
||||||
|
|
||||||
### Core Content
|
|
||||||
|
|
||||||
| # | Контент | SEO Vol | Зачем нужен | Тип | Приоритет | Brief |
|
|
||||||
|---|---------|---------|-------------|-----|-----------|-------|
|
|
||||||
| 1 | **Live URLs Guide** | ~0 | Core feature documentation | Docs + Landing | 🔥 HIGH | Нет brief, core docs |
|
|
||||||
| 2 | **Claude Code + Banatie Workflow** | 10-20 | ICP контент, позиционирование | Tutorial | 🔥 HIGH | `0-inbox/claude-code-image-generation-mcp.md` |
|
|
||||||
| 3 | **Cursor Image Generation Workflow** | ~0-50 | ICP контент, workflow demo | Tutorial | HIGH | `0-inbox/cursor-image-generation-workflow.md` |
|
|
||||||
| 4 | **MCP Image APIs Compared** | ~0 | Competitive positioning | Comparison | MEDIUM | `0-inbox/mcp-image-apis-compared.md` |
|
|
||||||
| 5 | **Vibecoding Images Tutorial** | ~0 | Future SEO, trend positioning | Tutorial | MEDIUM | Нет brief |
|
|
||||||
|
|
||||||
### Blocked Content
|
|
||||||
|
|
||||||
| Контент | Блокер |
|
|
||||||
|---------|--------|
|
|
||||||
| MCP Integration Guide | MCP feature must ship first |
|
|
||||||
| Cursor Workflow (полный) | MCP feature must ship first |
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
### Product Content Details
|
|
||||||
|
|
||||||
#### 1. Live URLs Guide (CORE)
|
|
||||||
|
|
||||||
**Target:** `/docs/live-urls/` + `/live-urls` landing
|
|
||||||
|
|
||||||
**Why critical:**
|
|
||||||
- Core differentiator от всех конкурентов
|
|
||||||
- Без гайда пользователь не поймёт главную фичу
|
|
||||||
- Validation scenario для interviews
|
|
||||||
|
|
||||||
**Content structure:**
|
|
||||||
1. What are Live URLs
|
|
||||||
2. How they work (URL → generation → CDN)
|
|
||||||
3. Use cases (placeholders, prototypes, production)
|
|
||||||
4. Code examples (HTML, React, Next.js)
|
|
||||||
5. Prompt syntax and parameters
|
|
||||||
6. Best practices
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
#### 2. Claude Code + Banatie Workflow
|
|
||||||
|
|
||||||
**Target:** Tutorial (blog + docs)
|
|
||||||
|
|
||||||
**Keywords (low but exact ICP):**
|
|
||||||
- can claude code generate images (20 vol)
|
|
||||||
- claude code image generation (10 vol)
|
|
||||||
|
|
||||||
**Why important despite low volume:**
|
|
||||||
- Direct hit на наш ICP
|
|
||||||
- Показывает что мы понимаем workflow
|
|
||||||
- Может ранжироваться по unexpected queries
|
|
||||||
- Needed для validation interviews
|
|
||||||
|
|
||||||
**Content structure:**
|
|
||||||
1. The problem: broken images in Claude Code projects
|
|
||||||
2. Current solutions (copy stock photos manually)
|
|
||||||
3. Better way: Banatie integration
|
|
||||||
4. Step-by-step setup
|
|
||||||
5. Real examples with prompts
|
|
||||||
6. Before/after comparison
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
#### 3. Cursor Image Generation Workflow
|
|
||||||
|
|
||||||
**Target:** Full tutorial (blog + cross-post)
|
|
||||||
|
|
||||||
**Why important:**
|
|
||||||
- Cursor = massive user base
|
|
||||||
- AI-first developers = our ICP
|
|
||||||
- Detailed tutorial = conversion
|
|
||||||
- Competitors have docs, we need tutorial
|
|
||||||
|
|
||||||
**Content structure:**
|
|
||||||
1. The old way (context switching pain)
|
|
||||||
2. The new way (MCP integration)
|
|
||||||
3. Setup guide (step-by-step)
|
|
||||||
4. Real use cases with code
|
|
||||||
5. Comparison: Banatie vs other MCP servers
|
|
||||||
6. Advanced features (@name, project organization)
|
|
||||||
|
|
||||||
**Note:** Partially blocked until MCP ships. Can prepare outline and screenshots.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
#### 4. MCP Image APIs Compared
|
|
||||||
|
|
||||||
**Target:** Comparison article (blog)
|
|
||||||
|
|
||||||
**Why important:**
|
|
||||||
- Shows we understand ecosystem
|
|
||||||
- Honest comparison = trust
|
|
||||||
- Competitive positioning
|
|
||||||
|
|
||||||
**Compare:**
|
|
||||||
- Replicate MCP
|
|
||||||
- Together AI MCP
|
|
||||||
- fal.ai MCP
|
|
||||||
- Banatie MCP
|
|
||||||
- Amazon Bedrock MCP
|
|
||||||
|
|
||||||
**Criteria:**
|
|
||||||
- Setup time
|
|
||||||
- Cost per image
|
|
||||||
- Project organization
|
|
||||||
- Developer experience
|
|
||||||
|
|
||||||
**Key message:** "You don't need cheapest. You need the one that fits your workflow."
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
#### 5. Vibecoding Images Tutorial
|
|
||||||
|
|
||||||
**Target:** Tutorial (blog)
|
|
||||||
|
|
||||||
**Why despite 0 volume:**
|
|
||||||
- Vibecoding = explosive trend (10 → 135K in 3 months)
|
|
||||||
- Search behavior not formed yet
|
|
||||||
- Early indexed content = advantage when demand comes
|
|
||||||
- Shows we understand the movement
|
|
||||||
|
|
||||||
**Content structure:**
|
|
||||||
1. What is vibecoding
|
|
||||||
2. The image problem in vibecoding
|
|
||||||
3. How Banatie solves it
|
|
||||||
4. Workflow examples
|
|
||||||
5. Live URLs for rapid prototyping
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Site Structure Plan
|
|
||||||
|
|
||||||
### Landing Pages (banatie.app)
|
|
||||||
|
|
||||||
```
|
|
||||||
/placeholder-images ← SEO landing (14.8K vol)
|
|
||||||
/live-urls ← Product feature landing
|
|
||||||
/integrations/cursor ← Workflow landing (when MCP ready)
|
|
||||||
/integrations/claude-code ← Workflow landing
|
|
||||||
```
|
|
||||||
|
|
||||||
### Documentation
|
|
||||||
|
|
||||||
```
|
|
||||||
/docs/
|
|
||||||
├── getting-started/
|
|
||||||
├── live-urls/ ← Core feature docs (Product-first)
|
|
||||||
├── placeholders/ ← SEO + utility
|
|
||||||
│ ├── dark-mode/ ← 4.4K vol, KD 2
|
|
||||||
│ ├── sizes/
|
|
||||||
│ └── profiles/
|
|
||||||
├── integrations/
|
|
||||||
│ ├── mcp/
|
|
||||||
│ ├── cursor/
|
|
||||||
│ └── claude-code/
|
|
||||||
└── api-reference/
|
|
||||||
```
|
|
||||||
|
|
||||||
### Blog (dev.to, cross-post)
|
|
||||||
|
|
||||||
- Midjourney Alternatives (URGENT, SEO)
|
|
||||||
- MCP Servers Compared (Product)
|
|
||||||
- Claude Code + Banatie Workflow (Product)
|
|
||||||
- Cursor Image Generation (Product, when MCP ready)
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Priority Summary
|
|
||||||
|
|
||||||
### TOP 5 (делать первыми)
|
|
||||||
|
|
||||||
1. **Placeholder Images Landing** — SEO foundation (14.8K vol) ✅ Brief ready
|
|
||||||
2. **Live URLs Documentation** — core product story
|
|
||||||
3. **Midjourney Alternatives** — URGENT, easy win (KD 3) ✅ Brief ready
|
|
||||||
4. **Claude Code Workflow Tutorial** — ICP content ✅ Brief ready
|
|
||||||
5. **Cursor Workflow Tutorial** — ICP content (blocked by MCP) ✅ Brief ready
|
|
||||||
|
|
||||||
### SECONDARY
|
|
||||||
|
|
||||||
6. Dark Mode Placeholders (docs section)
|
|
||||||
7. Advertising Images (needs SERP validation)
|
|
||||||
8. MCP Comparison Article
|
|
||||||
9. Vibecoding Tutorial (future SEO bet)
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Research Files Reference
|
|
||||||
|
|
||||||
**Keyword Research:**
|
|
||||||
- `banatie-content/research/keywords/research-report-2026-01-09.md` — final report
|
|
||||||
- `banatie-content/research/keywords/serp-analysis-2026-01-09.md` — SERP validation
|
|
||||||
- `banatie-content/research/keywords/placeholder-niche-deep-dive-2026-01-02.md` — placeholder deep dive
|
|
||||||
- `banatie-content/research/keywords/ai-web-dev-images-2026-01-09.md` — main research
|
|
||||||
|
|
||||||
**Content Briefs:**
|
|
||||||
- `banatie-content/0-inbox/placeholder-images-api.md`
|
|
||||||
- `banatie-content/0-inbox/midjourney-alternatives-developers.md`
|
|
||||||
- `banatie-content/0-inbox/advertising-images-guide.md`
|
|
||||||
- `banatie-content/0-inbox/claude-code-image-generation-mcp.md`
|
|
||||||
- `banatie-content/0-inbox/cursor-image-generation-workflow.md`
|
|
||||||
- `banatie-content/0-inbox/mcp-image-apis-compared.md`
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Key Insights from Research
|
|
||||||
|
|
||||||
1. **Solution keywords > Problem keywords**
|
|
||||||
- "placeholder images" (14.8K) vs "how to get images for vibe coding" (0)
|
|
||||||
- Target what people search, not what they need
|
|
||||||
|
|
||||||
2. **Generic > AI-prefixed**
|
|
||||||
- "placeholder images" (14.8K, KD 32) vs "ai image generator" (high KD)
|
|
||||||
- Position as "images for developers" not "AI image generator"
|
|
||||||
|
|
||||||
3. **Long-tail questions = ~0 volume**
|
|
||||||
- People don't google problems, they google solutions
|
|
||||||
- Don't target question keywords standalone
|
|
||||||
|
|
||||||
4. **SEO ≠ Market validation**
|
|
||||||
- SEO shows search behavior, not real pain
|
|
||||||
- Customer interviews still needed
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
**Document Owner:** @men + Oleg
|
|
||||||
**Last Updated:** January 9, 2026
|
|
||||||
**Related:** `BANATIE-CONTENT-INTEGRATION.md`
|
|
||||||
|
|
@ -1,7 +1,7 @@
|
||||||
# Pricing Strategy: Banatie for AI Developers
|
# Pricing Strategy: Banatie for AI Developers
|
||||||
|
|
||||||
**Date:** October 20, 2025 (Updated: January 9, 2026)
|
**Date:** October 20, 2025
|
||||||
**Version:** 2.2 (Fixed encoding, Template System terminology)
|
**Version:** 2.0 (Hybrid model - Credits + Subscription)
|
||||||
**Based on:** Oleg's personal feedback + Krea.ai model inspiration
|
**Based on:** Oleg's personal feedback + Krea.ai model inspiration
|
||||||
**Status:** Draft for validation testing
|
**Status:** Draft for validation testing
|
||||||
|
|
||||||
|
|
@ -10,7 +10,7 @@
|
||||||
## Pricing Philosophy
|
## Pricing Philosophy
|
||||||
|
|
||||||
**Core insight from ICP research:**
|
**Core insight from ICP research:**
|
||||||
> "Дискомфорт подписки в том, что я не регулярно пользуюсь сервисами и жалко денег когда не пользуюсь"
|
> "ДиÑкомфорт подпиÑки в том, что Ñ Ð½Ðµ регулÑрно пользуюÑÑŒ ÑервиÑами и жалко денег когда не пользуюÑÑŒ"
|
||||||
|
|
||||||
**Problem with traditional SaaS subscriptions:**
|
**Problem with traditional SaaS subscriptions:**
|
||||||
- Episodic usage patterns (site in a weekend, then 2 months idle)
|
- Episodic usage patterns (site in a weekend, then 2 months idle)
|
||||||
|
|
@ -42,19 +42,19 @@
|
||||||
- Basic transformations only
|
- Basic transformations only
|
||||||
|
|
||||||
**What's included:**
|
**What's included:**
|
||||||
- ✅ REST API access
|
- ✅ REST API access
|
||||||
- ✅ MCP integration
|
- ✅ MCP integration
|
||||||
- ✅ Template System (built-in templates)
|
- ✅ Prompt Enhancement
|
||||||
- ✅ CDN delivery
|
- ✅ CDN delivery
|
||||||
- ✅ @name references
|
- ✅ @name references
|
||||||
- ✅ Basic transformations (resize, format)
|
- ✅ Basic transformations (resize, format)
|
||||||
- ✅ Generation history (30 days)
|
- ✅ Generation history (30 days)
|
||||||
|
|
||||||
**What's NOT included:**
|
**What's NOT included:**
|
||||||
- ❌ No watermark removal
|
- ⌠No watermark removal
|
||||||
- ❌ Limited transformations (no custom presets)
|
- ⌠Limited transformations (no custom presets)
|
||||||
- ❌ Priority queue (slower generation)
|
- ⌠Priority queue (slower generation)
|
||||||
- ❌ Advanced features (when released)
|
- ⌠Advanced features (when released)
|
||||||
|
|
||||||
**Revenue impact:** $0 (cost center)
|
**Revenue impact:** $0 (cost center)
|
||||||
**Goal:** Convert 10-20% to paid within 30 days
|
**Goal:** Convert 10-20% to paid within 30 days
|
||||||
|
|
@ -80,19 +80,19 @@
|
||||||
| 1,500 generations | | | | Bulk work |
|
| 1,500 generations | | | | Bulk work |
|
||||||
|
|
||||||
**What's included:**
|
**What's included:**
|
||||||
- ✅ All Free tier features
|
- ✅ All Free tier features
|
||||||
- ✅ No watermark (production-ready)
|
- ✅ No watermark (production-ready)
|
||||||
- ✅ All transformations
|
- ✅ All transformations
|
||||||
- ✅ Extended history (1 year)
|
- ✅ Extended history (1 year)
|
||||||
- ✅ Priority support (email, 48hr response)
|
- ✅ Priority support (email, 48hr response)
|
||||||
|
|
||||||
**What's NOT included:**
|
**What's NOT included:**
|
||||||
- ❌ Priority generation queue (Pro only)
|
- ⌠Priority generation queue (Pro only)
|
||||||
- ❌ Advanced features (Pro only, when released)
|
- ⌠Advanced features (Pro only, when released)
|
||||||
- ❌ Monthly recurring generations
|
- ⌠Monthly recurring generations
|
||||||
|
|
||||||
**Why 90-day expiry:**
|
**Why 90-day expiry:**
|
||||||
- Based on Oleg's Krea.ai feedback: "90 дней достаточно чтобы потом потратить остальное"
|
- Based on Oleg's Krea.ai feedback: "90 дней доÑтаточно чтобы потом потратить оÑтальное"
|
||||||
- Long enough to not feel rushed
|
- Long enough to not feel rushed
|
||||||
- Short enough to encourage purchase when needed
|
- Short enough to encourage purchase when needed
|
||||||
- Industry standard (Krea.ai, similar services)
|
- Industry standard (Krea.ai, similar services)
|
||||||
|
|
@ -117,17 +117,16 @@
|
||||||
- OR $470/year (save $118 = 20% discount)
|
- OR $470/year (save $118 = 20% discount)
|
||||||
|
|
||||||
**What's included:**
|
**What's included:**
|
||||||
- ✅ 500 generations per month (included)
|
- ✅ 500 generations per month (included)
|
||||||
- ✅ All Credit Pack features
|
- ✅ All Credit Pack features
|
||||||
- ✅ Priority generation queue (2x faster)
|
- ✅ Priority generation queue (2x faster)
|
||||||
- ✅ Advanced features (exclusive):
|
- ✅ Advanced features (exclusive):
|
||||||
- Flow-based generation (when released)
|
- Flow-based generation (when released)
|
||||||
- **Custom Templates** (create your own enhancement templates)
|
|
||||||
- Namespaces / project organization
|
- Namespaces / project organization
|
||||||
- On-demand URL generation
|
- On-demand URL generation
|
||||||
- Custom style presets (future)
|
- Custom style presets (future)
|
||||||
- ✅ Priority support (24hr response)
|
- ✅ Priority support (24hr response)
|
||||||
- ✅ Overage pricing: $0.10/gen (same as Starter pack)
|
- ✅ Overage pricing: $0.10/gen (same as Starter pack)
|
||||||
|
|
||||||
**Why $49:**
|
**Why $49:**
|
||||||
- Below Cloudinary ($89/month)
|
- Below Cloudinary ($89/month)
|
||||||
|
|
@ -155,13 +154,13 @@
|
||||||
|---------|------|---------|-----|
|
|---------|------|---------|-----|
|
||||||
| **Generations/month** | 10 | As purchased | 500 included |
|
| **Generations/month** | 10 | As purchased | 500 included |
|
||||||
| **Watermark** | Yes | No | No |
|
| **Watermark** | Yes | No | No |
|
||||||
| **MCP Integration** | ✅ | ✅ | ✅ |
|
| **MCP Integration** | ✅ | ✅ | ✅ |
|
||||||
| **Template System** | Built-in | Built-in | Built-in + Custom |
|
| **Prompt Enhancement** | ✅ | ✅ | ✅ |
|
||||||
| **@name References** | ✅ | ✅ | ✅ |
|
| **@name References** | ✅ | ✅ | ✅ |
|
||||||
| **CDN Delivery** | ✅ | ✅ | ✅ |
|
| **CDN Delivery** | ✅ | ✅ | ✅ |
|
||||||
| **Transformations** | Basic | All | All |
|
| **Transformations** | Basic | All | All |
|
||||||
| **Priority Queue** | ❌ | ❌ | ✅ 2x faster |
|
| **Priority Queue** | ⌠| ⌠| ✅ 2x faster |
|
||||||
| **Advanced Features** | ❌ | ❌ | ✅ Exclusive |
|
| **Advanced Features** | ⌠| ⌠| ✅ Exclusive |
|
||||||
| **Support** | Community | Email (48h) | Email (24h) |
|
| **Support** | Community | Email (48h) | Email (24h) |
|
||||||
| **Price** | $0 | $20-100 | $49/mo |
|
| **Price** | $0 | $20-100 | $49/mo |
|
||||||
| **Best For** | Testing | 1-4 projects | Regular use |
|
| **Best For** | Testing | 1-4 projects | Regular use |
|
||||||
|
|
@ -178,7 +177,6 @@
|
||||||
|
|
||||||
**Prompt Enhancement (Gemini 2.0 Flash):**
|
**Prompt Enhancement (Gemini 2.0 Flash):**
|
||||||
- ~$0.001 per prompt (negligible)
|
- ~$0.001 per prompt (negligible)
|
||||||
- Note: This is the technical implementation powering Template System
|
|
||||||
|
|
||||||
**CDN Bandwidth (Cloudflare):**
|
**CDN Bandwidth (Cloudflare):**
|
||||||
- Free tier: 100GB/month
|
- Free tier: 100GB/month
|
||||||
|
|
@ -197,11 +195,11 @@
|
||||||
### Revenue Per Generation:
|
### Revenue Per Generation:
|
||||||
|
|
||||||
**Free Tier:** -$0.040 (loss per image)
|
**Free Tier:** -$0.040 (loss per image)
|
||||||
**Starter Pack ($20 / 200):** $0.10 per gen → **$0.06 profit**
|
**Starter Pack ($20 / 200):** $0.10 per gen → **$0.06 profit**
|
||||||
**Builder Pack ($50 / 600):** $0.083 per gen → **$0.043 profit**
|
**Builder Pack ($50 / 600):** $0.083 per gen → **$0.043 profit**
|
||||||
**Creator Pack ($100 / 1500):** $0.067 per gen → **$0.027 profit**
|
**Creator Pack ($100 / 1500):** $0.067 per gen → **$0.027 profit**
|
||||||
**Pro Subscription ($49 / 500):** $0.098 per gen → **$0.058 profit**
|
**Pro Subscription ($49 / 500):** $0.098 per gen → **$0.058 profit**
|
||||||
**Pro Overage:** $0.10 per gen → **$0.06 profit**
|
**Pro Overage:** $0.10 per gen → **$0.06 profit**
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
|
|
@ -259,13 +257,13 @@
|
||||||
|
|
||||||
**3. Decision Simplification:**
|
**3. Decision Simplification:**
|
||||||
- Only 3 paid options (not 6-7 like some competitors)
|
- Only 3 paid options (not 6-7 like some competitors)
|
||||||
- Clear use case per tier (testing → projects → regular use)
|
- Clear use case per tier (testing → projects → regular use)
|
||||||
- Easy to upgrade (credits → Pro seamless)
|
- Easy to upgrade (credits → Pro seamless)
|
||||||
|
|
||||||
**4. Commitment Gradient:**
|
**4. Commitment Gradient:**
|
||||||
- Free → try instantly (no credit card)
|
- Free → try instantly (no credit card)
|
||||||
- Credits → low commitment (pay once, use when needed)
|
- Credits → low commitment (pay once, use when needed)
|
||||||
- Pro → higher commitment (monthly, but cancel anytime)
|
- Pro → higher commitment (monthly, but cancel anytime)
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
|
|
@ -291,26 +289,25 @@
|
||||||
## MCP Access Strategy (Revised)
|
## MCP Access Strategy (Revised)
|
||||||
|
|
||||||
**Original plan:** MCP only for Pro tier
|
**Original plan:** MCP only for Pro tier
|
||||||
**Oleg's feedback:** "MCP должно быть бесплатно, это маркетинговая фича"
|
**Oleg's feedback:** "MCP должно быть беÑплатно, Ñто Ð¼Ð°Ñ€ÐºÐµÑ‚Ð¸Ð½Ð³Ð¾Ð²Ð°Ñ Ñ„Ð¸Ñ‡Ð°"
|
||||||
|
|
||||||
**New strategy: MCP on ALL tiers ✅**
|
**New strategy: MCP on ALL tiers ✅**
|
||||||
|
|
||||||
**Why this is correct:**
|
**Why this is correct:**
|
||||||
|
|
||||||
1. **Viral adoption:** Developers try MCP → share with others → network effect
|
1. **Viral adoption:** Developers try MCP → share with others → network effect
|
||||||
2. **Can't restrict:** If API is open, community will build MCP anyway
|
2. **Can't restrict:** If API is open, community will build MCP anyway
|
||||||
3. **Marketing asset:** "First AI image gen with native MCP support"
|
3. **Marketing asset:** "First AI image gen with native MCP support"
|
||||||
4. **Trust building:** No artificial feature paywalls (developer-friendly)
|
4. **Trust building:** No artificial feature paywalls (developer-friendly)
|
||||||
|
|
||||||
**How to monetize without MCP paywall:**
|
**How to monetize without MCP paywall:**
|
||||||
- Free tier: Limited generations (10/month) → forces upgrade
|
- Free tier: Limited generations (10/month) → forces upgrade
|
||||||
- Credits: Episodic users buy when needed → flexible revenue
|
- Credits: Episodic users buy when needed → flexible revenue
|
||||||
- Pro: Heavy users subscribe → predictable MRR
|
- Pro: Heavy users subscribe → predictable MRR
|
||||||
|
|
||||||
**Features exclusive to Pro (after launch):**
|
**Features exclusive to Pro (after launch):**
|
||||||
- Priority queue (2x faster generation)
|
- Priority queue (2x faster generation)
|
||||||
- Flow-based generation (complex workflows)
|
- Flow-based generation (complex workflows)
|
||||||
- Custom Templates (create your own)
|
|
||||||
- Namespaces (project organization)
|
- Namespaces (project organization)
|
||||||
- On-demand URL generation
|
- On-demand URL generation
|
||||||
- Custom style presets
|
- Custom style presets
|
||||||
|
|
@ -338,11 +335,11 @@ Perfect for testing and small demos
|
||||||
|
|
||||||
- 10 generations/month
|
- 10 generations/month
|
||||||
- MCP + API + UI access
|
- MCP + API + UI access
|
||||||
- Template System (built-in)
|
- Prompt Enhancement
|
||||||
- CDN delivery
|
- CDN delivery
|
||||||
- Watermark on images
|
- Watermark on images
|
||||||
|
|
||||||
[Start Free →]
|
[Start Free →]
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
|
|
@ -359,7 +356,7 @@ Buy credits when you need them
|
||||||
- Valid for 90 days
|
- Valid for 90 days
|
||||||
- No recurring charges
|
- No recurring charges
|
||||||
|
|
||||||
[View Packs →]
|
[View Packs →]
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
|
|
@ -372,11 +369,11 @@ For regular builders and agencies
|
||||||
|
|
||||||
- 500 generations/month included
|
- 500 generations/month included
|
||||||
- Priority generation queue (2x faster)
|
- Priority generation queue (2x faster)
|
||||||
- Custom Templates + Exclusive features
|
- Exclusive features (Flow, Namespaces)
|
||||||
- $0.10 per additional generation
|
- $0.10 per additional generation
|
||||||
- Cancel anytime
|
- Cancel anytime
|
||||||
|
|
||||||
[Start Pro Trial →]
|
[Start Pro Trial →]
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
|
|
@ -409,16 +406,13 @@ A: Yes, 90 days from purchase. You'll get email reminders at 30 days and 7 days
|
||||||
**Q: Is there an Enterprise plan?**
|
**Q: Is there an Enterprise plan?**
|
||||||
A: Not yet. Contact us if you need >10K generations/month or custom features.
|
A: Not yet. Contact us if you need >10K generations/month or custom features.
|
||||||
|
|
||||||
**Q: What's the difference between Template System tiers?**
|
|
||||||
A: All tiers get built-in templates (Photorealistic, Illustration, etc.). Pro tier adds Custom Templates — create and save your own enhancement templates for brand consistency.
|
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
## Pricing Experiments (Post-Launch)
|
## Pricing Experiments (Post-Launch)
|
||||||
|
|
||||||
### Month 1-2: Validation
|
### Month 1-2: Validation
|
||||||
- Test current structure
|
- Test current structure
|
||||||
- Track conversion rates (Free → Credits, Free → Pro)
|
- Track conversion rates (Free → Credits, Free → Pro)
|
||||||
- Identify most popular pack (likely Builder $50)
|
- Identify most popular pack (likely Builder $50)
|
||||||
|
|
||||||
### Month 3: A/B Test
|
### Month 3: A/B Test
|
||||||
|
|
@ -446,7 +440,7 @@ A: All tiers get built-in templates (Photorealistic, Illustration, etc.). Pro ti
|
||||||
- After strong PMF signals (low churn, high NPS)
|
- After strong PMF signals (low churn, high NPS)
|
||||||
|
|
||||||
**When to decrease prices:**
|
**When to decrease prices:**
|
||||||
- If conversion rate <5% (Free → Paid)
|
- If conversion rate <5% (Free → Paid)
|
||||||
- If competitor undercuts significantly
|
- If competitor undercuts significantly
|
||||||
- If usage patterns show lower value perception
|
- If usage patterns show lower value perception
|
||||||
|
|
||||||
|
|
@ -576,7 +570,7 @@ Metadata: { included_credits: 500, overage_rate: 0.10 }
|
||||||
|
|
||||||
## Pricing Strategy: Key Decisions
|
## Pricing Strategy: Key Decisions
|
||||||
|
|
||||||
### ✅ CONFIRMED:
|
### ✅ CONFIRMED:
|
||||||
|
|
||||||
1. **Hybrid model (Credits + Subscription)** - accommodates episodic AND regular users
|
1. **Hybrid model (Credits + Subscription)** - accommodates episodic AND regular users
|
||||||
2. **MCP on all tiers** - marketing asset, can't be restricted
|
2. **MCP on all tiers** - marketing asset, can't be restricted
|
||||||
|
|
@ -585,16 +579,15 @@ Metadata: { included_credits: 500, overage_rate: 0.10 }
|
||||||
5. **Watermark on free tier** - clear upgrade incentive
|
5. **Watermark on free tier** - clear upgrade incentive
|
||||||
6. **$49 Pro tier** - positioned between dev tools ($20) and platforms ($89+)
|
6. **$49 Pro tier** - positioned between dev tools ($20) and platforms ($89+)
|
||||||
7. **No fake scarcity** - transparent, developer-friendly pricing
|
7. **No fake scarcity** - transparent, developer-friendly pricing
|
||||||
8. **Template System on all tiers** - built-in templates free, Custom Templates = Pro
|
|
||||||
|
|
||||||
### ⏳ TO VALIDATE:
|
### â³ TO VALIDATE:
|
||||||
|
|
||||||
1. **Credit pack sizes** - are 200/600/1500 the right amounts?
|
1. **Credit pack sizes** - are 200/600/1500 the right amounts?
|
||||||
2. **Pro inclusion (500 gens)** - is this the sweet spot or too low/high?
|
2. **Pro inclusion (500 gens)** - is this the sweet spot or too low/high?
|
||||||
3. **Annual discount (20%)** - does this drive annual commitments?
|
3. **Annual discount (20%)** - does this drive annual commitments?
|
||||||
4. **Overage pricing ($0.10)** - acceptable or feels like nickel-and-diming?
|
4. **Overage pricing ($0.10)** - acceptable or feels like nickel-and-diming?
|
||||||
|
|
||||||
### 🔮 FUTURE:
|
### ðŸ"® FUTURE:
|
||||||
|
|
||||||
1. **Hobbyist tier ($10-20)** - if demand shows for lower entry point
|
1. **Hobbyist tier ($10-20)** - if demand shows for lower entry point
|
||||||
2. **Agency tier ($149+)** - when agencies start adopting
|
2. **Agency tier ($149+)** - when agencies start adopting
|
||||||
|
|
@ -603,6 +596,8 @@ Metadata: { included_credits: 500, overage_rate: 0.10 }
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
## Alternative Approach: Single Tier Launch (For Consideration)
|
## Alternative Approach: Single Tier Launch (For Consideration)
|
||||||
|
|
||||||
Before launch, it's worth considering an alternative strategy: start with **one paid tier only** instead of three (Free, Credits, Pro).
|
Before launch, it's worth considering an alternative strategy: start with **one paid tier only** instead of three (Free, Credits, Pro).
|
||||||
|
|
|
||||||
|
|
@ -1,45 +1,30 @@
|
||||||
# Product Features Overview
|
# Product Features Overview
|
||||||
|
|
||||||
**Date:** November 2, 2025 (Updated: January 9, 2026)
|
**Date:** November 2, 2025
|
||||||
**Status:** 📝 Living document - feature roadmap
|
**Status:** 📝 Living document - feature roadmap
|
||||||
**Version:** 1.1 (Template System = primary feature, Prompt Enhancement = technical implementation)
|
**Version:** 1.0
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
## Core Features (MVP)
|
## Core Features (MVP)
|
||||||
|
|
||||||
### 1. Template System ⭐ PRIMARY MOAT
|
### 1. Prompt Enhancement ⭐ PRIMARY MOAT
|
||||||
|
|
||||||
**What:** User-facing feature for professional quality output
|
**What:** AI improves user prompts for professional quality
|
||||||
|
|
||||||
**Under the hood:** Prompt Enhancement (AI improves prompts) — technical implementation that powers templates
|
|
||||||
|
|
||||||
**How:**
|
**How:**
|
||||||
- User selects template (Photorealistic default, or custom)
|
- User provides generic prompt: "hero image for SaaS"
|
||||||
- System analyzes prompt for specified parameters (subject, style, lighting, etc.)
|
- System enhances: "Professional SaaS hero image, modern gradient background, clean UI elements, high contrast, 4K quality, corporate aesthetic"
|
||||||
- Template applies **only** to missing details (granular enhancement)
|
- Gemini generates with enhanced prompt
|
||||||
- Detailed prompts pass through unchanged
|
|
||||||
- User always sees before/after comparison
|
|
||||||
|
|
||||||
**Example - Short prompt:**
|
**Status:** ✅ Working, always enabled
|
||||||
- Input: "hero image for SaaS"
|
|
||||||
- Template: Photorealistic (fills lighting, background, quality, composition)
|
|
||||||
- Output: Full professional prompt
|
|
||||||
|
|
||||||
**Example - Detailed prompt:**
|
|
||||||
- Input: "Professional SaaS dashboard mockup, purple gradient, soft shadows, 4K"
|
|
||||||
- Template: Detects most params specified
|
|
||||||
- Output: Passes through mostly unchanged (adds only missing critical details)
|
|
||||||
|
|
||||||
**Status:** ✅ Working (enhancement logic), needs template selector UI
|
|
||||||
|
|
||||||
**Why it matters:**
|
**Why it matters:**
|
||||||
- This is our main competitive advantage (3-6 months to replicate)
|
- This is our main competitive advantage
|
||||||
- Justifies $0.10 vs $0.0006 commodity
|
- Justifies $0.10 vs $0.0006 commodity
|
||||||
- Users control output via template choice, not generic "enhancement"
|
- Users get professional quality without prompt engineering skills
|
||||||
- Intelligent analysis = unique, complex feature
|
|
||||||
|
|
||||||
**Custom Templates = Pro tier paid feature**
|
**Cannot be disabled** - this is the value we sell
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
|
|
@ -297,7 +282,7 @@ const features = await banatie.generate({
|
||||||
|
|
||||||
| Feature | Segment | Priority | Status | Days |
|
| Feature | Segment | Priority | Status | Days |
|
||||||
|---------|---------|----------|--------|------|
|
|---------|---------|----------|--------|------|
|
||||||
| Template System | All | 🔴 Critical | ✅ Done | - |
|
| Prompt Enhancement | All | 🔴 Critical | ✅ Done | - |
|
||||||
| 6 Aspect Ratios | All | 🔴 Critical | ✅ Done | - |
|
| 6 Aspect Ratios | All | 🔴 Critical | ✅ Done | - |
|
||||||
| Prompt URLs | All | 🔴 Critical | ⏳ Todo | 3 |
|
| Prompt URLs | All | 🔴 Critical | ⏳ Todo | 3 |
|
||||||
| MCP Server | B/D | 🟡 High | ⏳ Todo | 3 |
|
| MCP Server | B/D | 🟡 High | ⏳ Todo | 3 |
|
||||||
|
|
|
||||||
|
|
@ -1,212 +0,0 @@
|
||||||
# Template System
|
|
||||||
|
|
||||||
**Date:** January 9, 2026
|
|
||||||
**Status:** ✅ Strategic decision documented
|
|
||||||
**Version:** 1.0
|
|
||||||
**Previous concept:** Prompt Enhancement (reframed, not replaced)
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Executive Summary
|
|
||||||
|
|
||||||
**What changed (MARKETING ONLY, not technical):**
|
|
||||||
- OLD: "Prompt Enhancement" = primary feature (Template System = detail of how it works)
|
|
||||||
- NEW: **Template System** = primary feature (Prompt Enhancement = technical implementation for those who want to understand deeper)
|
|
||||||
|
|
||||||
**Prompt Enhancement still exists** — it's the AI that analyzes and improves prompts. We just reframed the hierarchy for better user communication.
|
|
||||||
|
|
||||||
**Why reframe:**
|
|
||||||
- Better marketing: "Choose template" clearer than "we enhance your prompt"
|
|
||||||
- User control: User selects outcome style, not "trust us to improve"
|
|
||||||
- Explains mandatory nature: Template must always be selected (not "we won't let you disable")
|
|
||||||
- Solves stylization: Custom templates = paid feature (replaces need for separate styling system)
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## How Templates Work
|
|
||||||
|
|
||||||
### User Experience
|
|
||||||
|
|
||||||
1. User selects template (or uses default)
|
|
||||||
2. User writes prompt (any completeness level)
|
|
||||||
3. System applies template intelligently based on prompt completeness
|
|
||||||
4. Generation produces professional result
|
|
||||||
|
|
||||||
### Template Logic
|
|
||||||
|
|
||||||
**Default template:** Photorealistic (not "general")
|
|
||||||
|
|
||||||
**Granular enhancement based on prompt completeness:**
|
|
||||||
|
|
||||||
| User prompt | System behavior |
|
|
||||||
|-------------|-----------------|
|
|
||||||
| Short/vague | Full template enhancement applied |
|
|
||||||
| Partial (missing some details) | Fills only missing details |
|
|
||||||
| Detailed/specific | Passes through unchanged |
|
|
||||||
|
|
||||||
**Example: Photorealistic template**
|
|
||||||
|
|
||||||
Template specifies: camera type, lens, lighting, focus characteristics, etc.
|
|
||||||
|
|
||||||
- **User writes:** "cat on table"
|
|
||||||
**System applies:** Full template (camera, lens, lighting, focus, composition)
|
|
||||||
|
|
||||||
- **User writes:** "cat on table, deep focus, natural window light"
|
|
||||||
**System applies:** Camera and lens only (respects user's focus and light choices)
|
|
||||||
|
|
||||||
- **User writes:** "cat on table, Canon EOS R5, 85mm f/1.4, shallow focus, golden hour backlight, rule of thirds composition"
|
|
||||||
**System applies:** Nothing (user specified everything)
|
|
||||||
|
|
||||||
**Principle:** Respect user intent. If they specified something, don't change it.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Template Types
|
|
||||||
|
|
||||||
### Built-in Templates (Free)
|
|
||||||
|
|
||||||
| Template | Purpose | Key characteristics |
|
|
||||||
|----------|---------|---------------------|
|
|
||||||
| **Photorealistic** (default) | Real-world photos | Camera specs, lighting, focus, composition |
|
|
||||||
| **Illustration** | Digital art | Style consistency, color palette, line work |
|
|
||||||
| **3D Render** | Product visualization | Materials, lighting setup, render quality |
|
|
||||||
| **Icon/Logo** | Simple graphics | Clean lines, scalability, flat design |
|
|
||||||
| **UI Mockup** | Interface screenshots | Device frames, realistic UI elements |
|
|
||||||
| **Abstract** | Backgrounds, patterns | Color harmony, texture, visual flow |
|
|
||||||
|
|
||||||
### Custom Templates (Paid Feature)
|
|
||||||
|
|
||||||
**What:** Users create and save their own templates
|
|
||||||
|
|
||||||
**Use cases:**
|
|
||||||
- Brand-specific style (colors, mood, composition rules)
|
|
||||||
- Project consistency (same visual language across all images)
|
|
||||||
- Agency presets (client-specific templates)
|
|
||||||
|
|
||||||
**Pricing:** Pro tier feature (or separate add-on)
|
|
||||||
|
|
||||||
**Why paid:**
|
|
||||||
- Requires storage (user templates saved)
|
|
||||||
- Advanced feature for power users
|
|
||||||
- Replaces need for separate "stylization" system
|
|
||||||
- Clear value differentiation
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Technical Implementation
|
|
||||||
|
|
||||||
### Prompt Analysis
|
|
||||||
|
|
||||||
Before applying template, analyze user prompt for:
|
|
||||||
- Camera/equipment mentions
|
|
||||||
- Lighting descriptions
|
|
||||||
- Composition directions
|
|
||||||
- Style keywords
|
|
||||||
- Technical parameters (focus, exposure, etc.)
|
|
||||||
|
|
||||||
### Template Application
|
|
||||||
|
|
||||||
```
|
|
||||||
finalPrompt = userPrompt + templateAdditions(excluding what user specified)
|
|
||||||
```
|
|
||||||
|
|
||||||
**Not:**
|
|
||||||
```
|
|
||||||
finalPrompt = template.replace("{prompt}", userPrompt) // Wrong - ignores user specificity
|
|
||||||
```
|
|
||||||
|
|
||||||
### Template Storage
|
|
||||||
|
|
||||||
**Built-in:** Hardcoded in backend
|
|
||||||
**Custom:** User account storage (Pro feature)
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Migration from "Prompt Enhancement"
|
|
||||||
|
|
||||||
### What stays the same:
|
|
||||||
- AI improves prompts automatically ✅
|
|
||||||
- Professional quality output ✅
|
|
||||||
- Works in any language ✅
|
|
||||||
- Always enabled (mandatory) ✅
|
|
||||||
|
|
||||||
### What changes:
|
|
||||||
- **Naming:** "Prompt Enhancement" → "Template System"
|
|
||||||
- **Control:** System chooses enhancement → User chooses template
|
|
||||||
- **Granularity:** All-or-nothing → Intelligent partial application
|
|
||||||
- **Paid feature:** No paid enhancement option → Custom templates = paid
|
|
||||||
|
|
||||||
### Documentation updates needed:
|
|
||||||
- [ ] Landing page copy
|
|
||||||
- [ ] API documentation
|
|
||||||
- [ ] Pricing page (custom templates = Pro)
|
|
||||||
- [ ] Marketing materials
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Competitive Positioning
|
|
||||||
|
|
||||||
### Why this is still a moat:
|
|
||||||
|
|
||||||
1. **Intelligent partial application** - Complex to implement, competitors use simple template substitution
|
|
||||||
2. **Built-in quality templates** - Curated by us, tested for Gemini optimization
|
|
||||||
3. **Custom template creation** - Paid feature, requires UI and storage
|
|
||||||
4. **Prompt analysis** - Understanding what user specified vs. what to add
|
|
||||||
|
|
||||||
### Time to replicate: 3-6 months (unchanged)
|
|
||||||
|
|
||||||
Competitors would need to:
|
|
||||||
- Build prompt analysis system
|
|
||||||
- Create and test template library
|
|
||||||
- Implement granular application logic
|
|
||||||
- Build custom template UI
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## User Communication
|
|
||||||
|
|
||||||
### How to explain to users:
|
|
||||||
|
|
||||||
**Simple version:**
|
|
||||||
> "Choose a template that matches your desired style. We'll make sure your image looks professional."
|
|
||||||
|
|
||||||
**Technical version:**
|
|
||||||
> "Templates provide baseline parameters (camera, lighting, composition). If you specify these yourself, we respect your choices. If you don't, we fill in the gaps with professional defaults."
|
|
||||||
|
|
||||||
### FAQ additions:
|
|
||||||
|
|
||||||
**Q: Can I disable templates?**
|
|
||||||
A: Templates ensure professional quality. You can override any aspect by specifying it in your prompt.
|
|
||||||
|
|
||||||
**Q: Why is there a default template?**
|
|
||||||
A: Photorealistic is the most common use case. You can change it per request.
|
|
||||||
|
|
||||||
**Q: Can I create my own templates?**
|
|
||||||
A: Custom templates are available on Pro tier.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Action Items
|
|
||||||
|
|
||||||
### Immediate:
|
|
||||||
- [ ] Update landing page messaging (template language)
|
|
||||||
- [ ] Update API docs with template parameter
|
|
||||||
- [ ] Add template selection to UI
|
|
||||||
|
|
||||||
### Technical:
|
|
||||||
- [ ] Implement prompt analysis (detect user-specified params)
|
|
||||||
- [ ] Implement granular template application
|
|
||||||
- [ ] Add template parameter to API
|
|
||||||
|
|
||||||
### Future (Pro):
|
|
||||||
- [ ] Custom template creation UI
|
|
||||||
- [ ] Template storage per user
|
|
||||||
- [ ] Template sharing (optional)
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
**Document owner:** @men + Oleg
|
|
||||||
**Last updated:** January 9, 2026
|
|
||||||
**Related docs:**
|
|
||||||
- [16-product-features.md](16-product-features.md) - Feature overview
|
|
||||||
- [10-pricing-strategy.md](10-pricing-strategy.md) - Custom templates pricing
|
|
||||||
|
|
@ -1,271 +0,0 @@
|
||||||
# Validation Approaches Catalog
|
|
||||||
|
|
||||||
**Date:** January 9, 2026
|
|
||||||
**Status:** ✅ Reference document
|
|
||||||
**Version:** 1.0
|
|
||||||
**Purpose:** Catalog of validation approaches with pros/cons for Oleg to choose
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Current State
|
|
||||||
|
|
||||||
- **Paying customers:** 0
|
|
||||||
- **Interviews conducted:** 0
|
|
||||||
- **API feedback received:** 0
|
|
||||||
- **Product status:** MVP ready, validation flows partially ready
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Validation Flows (What User Tests)
|
|
||||||
|
|
||||||
| Flow | Status | Description |
|
|
||||||
|------|--------|-------------|
|
|
||||||
| **Flow 1: Live URLs** | ✅ Ready | Generate via URL params, no API key needed |
|
|
||||||
| **Flow 2: Lab UI** | TBD | Web interface for testing generations |
|
|
||||||
| **Flow 3: API Integration** | ✅ Ready | Full API with key, SDK, documentation |
|
|
||||||
| **Flow 4: MCP** | ❌ Not built | Claude/Cursor integration |
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Validation Approaches
|
|
||||||
|
|
||||||
### 1. Known Developer (Personal Network)
|
|
||||||
|
|
||||||
**What:** Ask developers you already know to try Banatie
|
|
||||||
|
|
||||||
**Reliability:** ⭐ (Low)
|
|
||||||
**Cost:** $0
|
|
||||||
**Time:** 1 day
|
|
||||||
|
|
||||||
**Pros:**
|
|
||||||
- Fastest possible feedback
|
|
||||||
- Will actually try it (personal relationship)
|
|
||||||
- Can ask deep follow-up questions
|
|
||||||
|
|
||||||
**Cons:**
|
|
||||||
- Biased feedback (won't say "this is useless")
|
|
||||||
- May not be target ICP
|
|
||||||
- Small sample size
|
|
||||||
- "Friend favor" dynamic distorts honesty
|
|
||||||
|
|
||||||
**Best for:** Technical sanity check, UX bugs, basic flow testing
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
### 2. Telegram RU Communities
|
|
||||||
|
|
||||||
**What:** Post in Russian-speaking dev communities
|
|
||||||
|
|
||||||
**Reliability:** ⭐⭐ (Low-Medium)
|
|
||||||
**Cost:** $0
|
|
||||||
**Time:** 2-3 days
|
|
||||||
|
|
||||||
**Pros:**
|
|
||||||
- Native language = deeper conversations
|
|
||||||
- Some communities are active and engaged
|
|
||||||
- Can find specific niches (React, AI, etc.)
|
|
||||||
|
|
||||||
**Cons:**
|
|
||||||
- Russian market ≠ global market (different pain points)
|
|
||||||
- Many communities are dead or low-quality
|
|
||||||
- May attract tire-kickers, not potential customers
|
|
||||||
- Language barrier limits global applicability
|
|
||||||
|
|
||||||
**Best for:** Initial concept validation, Russian market exploration
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
### 3. Daily.dev Personal Post
|
|
||||||
|
|
||||||
**What:** Post on daily.dev as Oleg (personal brand, 5.2K rep)
|
|
||||||
|
|
||||||
**Reliability:** ⭐⭐ (Medium-Low)
|
|
||||||
**Cost:** $0
|
|
||||||
**Time:** 3-5 days
|
|
||||||
|
|
||||||
**Pros:**
|
|
||||||
- Existing audience (5.2K reputation)
|
|
||||||
- Developer-focused platform
|
|
||||||
- Can test messaging
|
|
||||||
- Admin of 1.5K member squad
|
|
||||||
|
|
||||||
**Cons:**
|
|
||||||
- Personal brand risk if product is bad
|
|
||||||
- One-shot (can't spam product posts)
|
|
||||||
- Engagement may be passive (likes, not signups)
|
|
||||||
- Platform algorithm may limit reach
|
|
||||||
|
|
||||||
**Best for:** Awareness, traffic spike, testing headlines/positioning
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
### 4. Discord AI Tools Communities
|
|
||||||
|
|
||||||
**What:** Join Discord servers focused on AI coding tools (Claude, Cursor, etc.)
|
|
||||||
|
|
||||||
**Reliability:** ⭐⭐⭐ (Medium-High)
|
|
||||||
**Cost:** $0
|
|
||||||
**Time:** 1-2 weeks
|
|
||||||
|
|
||||||
**Pros:**
|
|
||||||
- Exact ICP: developers using AI tools
|
|
||||||
- Real conversations, not just reactions
|
|
||||||
- Can observe pain points before pitching
|
|
||||||
- Multiple communities to test
|
|
||||||
- Global audience
|
|
||||||
|
|
||||||
**Cons:**
|
|
||||||
- Need to build credibility first (can't just pitch)
|
|
||||||
- Time investment in community participation
|
|
||||||
- May get banned if too promotional
|
|
||||||
- Quality varies by community
|
|
||||||
|
|
||||||
**Best for:** ICP validation, pain point discovery, warm outreach
|
|
||||||
|
|
||||||
**Recommended approach:**
|
|
||||||
1. Week 1: Join, observe, help others
|
|
||||||
2. Week 2: Start mentioning Banatie when relevant
|
|
||||||
3. Week 3+: Direct conversations with interested devs
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
### 5. jsjobs.ru Paid Interviews
|
|
||||||
|
|
||||||
**What:** Pay for interviews with Russian developers
|
|
||||||
|
|
||||||
**Reliability:** ⭐⭐⭐⭐ (High)
|
|
||||||
**Cost:** $50-100 (5-10 interviews × $10 each)
|
|
||||||
**Time:** 1 week
|
|
||||||
|
|
||||||
**Pros:**
|
|
||||||
- Structured interviews with real developers
|
|
||||||
- Payment ensures commitment
|
|
||||||
- Can screen for specific profile
|
|
||||||
- Get deep feedback (30-60 min each)
|
|
||||||
|
|
||||||
**Cons:**
|
|
||||||
- Cost (budget constraint)
|
|
||||||
- Russian market focus
|
|
||||||
- May attract interview-seekers, not product users
|
|
||||||
- Requires interview script preparation
|
|
||||||
|
|
||||||
**Best for:** Deep ICP validation, detailed feedback on specific features
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
### 6. Henry Warmup (Content Marketing)
|
|
||||||
|
|
||||||
**What:** Build Henry persona presence, then soft-pitch Banatie
|
|
||||||
|
|
||||||
**Reliability:** ⭐⭐⭐ (Medium-High)
|
|
||||||
**Cost:** $0
|
|
||||||
**Time:** 2-3 weeks minimum
|
|
||||||
|
|
||||||
**Pros:**
|
|
||||||
- Builds sustainable channel
|
|
||||||
- Attracts target audience organically
|
|
||||||
- No "spam" perception
|
|
||||||
- Can repurpose content across platforms
|
|
||||||
|
|
||||||
**Cons:**
|
|
||||||
- Slow (need multiple posts before credibility)
|
|
||||||
- Requires consistent content production
|
|
||||||
- Indirect feedback (traffic, not conversations)
|
|
||||||
- Henry persona needs maintenance
|
|
||||||
|
|
||||||
**Best for:** Long-term channel building, organic discovery
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
### 7. SEO Organic Traffic
|
|
||||||
|
|
||||||
**What:** Wait for organic search traffic to convert
|
|
||||||
|
|
||||||
**Reliability:** ⭐⭐⭐⭐⭐ (Very High)
|
|
||||||
**Cost:** $0
|
|
||||||
**Time:** 1-3 months
|
|
||||||
|
|
||||||
**Pros:**
|
|
||||||
- Highest quality signal (people searching for solution)
|
|
||||||
- Sustainable and scalable
|
|
||||||
- No manual outreach needed
|
|
||||||
- Validates market demand definitively
|
|
||||||
|
|
||||||
**Cons:**
|
|
||||||
- Slowest approach
|
|
||||||
- Requires content + SEO investment upfront
|
|
||||||
- May not get enough volume for statistical significance
|
|
||||||
- Depends on keyword rankings
|
|
||||||
|
|
||||||
**Best for:** End-goal validation, sustainable acquisition
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
### 8. Product Hunt Launch
|
|
||||||
|
|
||||||
**What:** Launch on Product Hunt
|
|
||||||
|
|
||||||
**Reliability:** ⭐⭐⭐ (High for awareness)
|
|
||||||
**Cost:** $0
|
|
||||||
**Time:** 1 month+ preparation
|
|
||||||
|
|
||||||
**Pros:**
|
|
||||||
- High visibility spike
|
|
||||||
- Developer/tech audience
|
|
||||||
- Social proof from upvotes
|
|
||||||
- Press/blogger attention possible
|
|
||||||
|
|
||||||
**Cons:**
|
|
||||||
- One-shot (can't re-launch easily)
|
|
||||||
- Requires preparation (assets, hunters, timing)
|
|
||||||
- Vanity metrics (upvotes ≠ customers)
|
|
||||||
- Post-launch depression (traffic drops)
|
|
||||||
|
|
||||||
**Best for:** Awareness milestone, social proof, traffic spike
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Decision Framework
|
|
||||||
|
|
||||||
**Choose based on:**
|
|
||||||
|
|
||||||
| Priority | Best approach |
|
|
||||||
|----------|---------------|
|
|
||||||
| Speed | #1 Known Developer |
|
|
||||||
| Quality feedback | #5 jsjobs Paid |
|
|
||||||
| ICP accuracy | #4 Discord AI Tools |
|
|
||||||
| Sustainability | #7 SEO Organic |
|
|
||||||
| One-time boost | #8 Product Hunt |
|
|
||||||
| Balance | #4 Discord AI Tools |
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Not Included (Considered but Rejected)
|
|
||||||
|
|
||||||
- **Reddit cold posts** — High ban risk, low reliability without reputation
|
|
||||||
- **Twitter/X outreach** — Requires follower base first
|
|
||||||
- **LinkedIn cold messages** — Low response rate, wrong audience vibe
|
|
||||||
- **Email cold outreach** — Spam perception, low conversion
|
|
||||||
- **Paid ads** — Premature for validation stage
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Recommended Sequence
|
|
||||||
|
|
||||||
**If Oleg wants structured approach:**
|
|
||||||
|
|
||||||
1. **Week 1:** #1 Known Developer (sanity check)
|
|
||||||
2. **Week 2-3:** #4 Discord AI Tools (ICP discovery)
|
|
||||||
3. **Week 3-4:** #6 Henry Warmup (start content)
|
|
||||||
4. **Month 2:** #7 SEO Organic (wait for traffic)
|
|
||||||
5. **Month 3:** #8 Product Hunt (if signals are positive)
|
|
||||||
|
|
||||||
**But:** Oleg decides. This is catalog, not prescription.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
**Document owner:** @men
|
|
||||||
**Last updated:** January 9, 2026
|
|
||||||
**Related docs:**
|
|
||||||
- [ROADMAP.md](../ROADMAP.md) - Current phase and priorities
|
|
||||||
- [03-icp-research-questions.md](../research/03-icp-research-questions.md) - ICP definition
|
|
||||||
|
|
@ -1,7 +1,7 @@
|
||||||
# Market Positioning & Strategy
|
# Market Positioning & Strategy
|
||||||
|
|
||||||
**Date:** October 20, 2025 (Updated: January 9, 2026)
|
**Date:** October 20, 2025
|
||||||
**Version:** 3.1 (MCP/CLI repositioned as table stakes, Template System = primary feature)
|
**Version:** 3.0 (Major update - expanded ICP, realistic TAM/SAM, competitive analysis)
|
||||||
**Status:** Working hypothesis - requires validation through founder's use case + 10-15 external interviews
|
**Status:** Working hypothesis - requires validation through founder's use case + 10-15 external interviews
|
||||||
**Previous versions:**
|
**Previous versions:**
|
||||||
- v1.0: Agencies-focused (archived)
|
- v1.0: Agencies-focused (archived)
|
||||||
|
|
@ -275,7 +275,7 @@ We ARE competing in "Production Image Infrastructure for Agentic Development" ($
|
||||||
| **MCP Integration** | ✅ | ⌠| ⌠| ⌠| 🔨 DIY |
|
| **MCP Integration** | ✅ | ⌠| ⌠| ⌠| 🔨 DIY |
|
||||||
| **CLI Tool** | ✅ | ⌠| ⌠| ⌠| 🔨 DIY |
|
| **CLI Tool** | ✅ | ⌠| ⌠| ⌠| 🔨 DIY |
|
||||||
| **REST API** | ✅ | ✅ | ✅ | ✅ | 🔨 DIY |
|
| **REST API** | ✅ | ✅ | ✅ | ✅ | 🔨 DIY |
|
||||||
| **Template System** | ✅ Unique | ⌠| ⌠| ⌠| ⌠|
|
| **Prompt Enhancement** | ✅ Unique | ⌠| ⌠| ⌠| ⌠|
|
||||||
| **@name References** | ✅ Unique | ⌠| ⌠| ⌠| 🔨 DIY |
|
| **@name References** | ✅ Unique | ⌠| ⌠| ⌠| 🔨 DIY |
|
||||||
| **Prompt URLs** | ✅ Unique | ⌠| ⌠| ⌠| ⌠|
|
| **Prompt URLs** | ✅ Unique | ⌠| ⌠| ⌠| ⌠|
|
||||||
| **Permanent CDN** | ✅ | ✅ | ⌠Temp URLs | ⌠| 🔨 DIY |
|
| **Permanent CDN** | ✅ | ✅ | ⌠Temp URLs | ⌠| 🔨 DIY |
|
||||||
|
|
@ -285,9 +285,7 @@ We ARE competing in "Production Image Infrastructure for Agentic Development" ($
|
||||||
| **Total Cost (TCO)** | $0.10 | $0.08-0.15 | $0.15-0.25 | $0.10-0.20 | $1-3 (time) |
|
| **Total Cost (TCO)** | $0.10 | $0.08-0.15 | $0.15-0.25 | $0.10-0.20 | $1-3 (time) |
|
||||||
| **Setup Time** | 5 min | 10 min | 10 min | 15 min | 20-40 hours |
|
| **Setup Time** | 5 min | 10 min | 10 min | 15 min | 20-40 hours |
|
||||||
|
|
||||||
**Our unique value:** Complete developer workflow (MCP + CLI + API + Prompt URLs) + intelligent Template System + production pipeline (CDN + transformations + optimization)
|
**Our unique value:** ONLY solution with complete developer workflow integration (MCP + CLI + API + Prompt URLs) + production pipeline (CDN + transformations + optimization)
|
||||||
|
|
||||||
**Note (Jan 2026):** MCP/CLI are now table stakes for developer tools. All serious competitors will have them by mid-2026. Our defensible moats are: Template System (intelligent prompt analysis), @references (consistency), Prompt URLs (unique), and complete production pipeline.
|
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
|
|
@ -300,7 +298,7 @@ We ARE competing in "Production Image Infrastructure for Agentic Development" ($
|
||||||
|
|
||||||
**What we BUILD:**
|
**What we BUILD:**
|
||||||
|
|
||||||
### 1. **Complete Developer Experience (DX Suite)**
|
### 1. **Best Developer Experience (DX)**
|
||||||
- MCP integration (for Claude Code, Cursor, future tools)
|
- MCP integration (for Claude Code, Cursor, future tools)
|
||||||
- CLI tool (for CI/CD, scripts, terminal workflows)
|
- CLI tool (for CI/CD, scripts, terminal workflows)
|
||||||
- REST API (fully documented, with SDKs)
|
- REST API (fully documented, with SDKs)
|
||||||
|
|
@ -309,24 +307,17 @@ We ARE competing in "Production Image Infrastructure for Agentic Development" ($
|
||||||
- Interactive docs with live examples
|
- Interactive docs with live examples
|
||||||
- Fast, helpful support (Discord, email)
|
- Fast, helpful support (Discord, email)
|
||||||
|
|
||||||
**Note (Jan 2026):** MCP/CLI/SDK collectively express "DX-first approach" but are NOT competitive advantages on their own. All serious competitors will have similar tools by mid-2026. The moat is in the *quality and completeness* of our DX suite, not individual tools.
|
|
||||||
|
|
||||||
**Moat:** Switching cost increases with integration depth. Once they've integrated Banatie into their workflow, moving to competitor requires re-coding, re-testing, re-deploying.
|
**Moat:** Switching cost increases with integration depth. Once they've integrated Banatie into their workflow, moving to competitor requires re-coding, re-testing, re-deploying.
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
### 2. **Workflow Intelligence**
|
### 2. **Workflow Intelligence**
|
||||||
|
|
||||||
**Template System (PRIMARY MOAT):**
|
**Prompt Enhancement:**
|
||||||
- User selects template (Photorealistic default, or custom)
|
- AI agent optimizes prompts automatically
|
||||||
- System analyzes prompt for specified parameters
|
|
||||||
- Applies template only for missing details (granular enhancement)
|
|
||||||
- Detailed prompts pass through unchanged
|
|
||||||
- Works in any language (Russian → English, etc.)
|
- Works in any language (Russian → English, etc.)
|
||||||
|
- Applies Gemini best practices
|
||||||
- Shows before/after (educational)
|
- Shows before/after (educational)
|
||||||
- Custom templates = Pro tier paid feature
|
|
||||||
|
|
||||||
**Technical implementation:** Prompt Enhancement (AI-powered prompt analysis and improvement). This is the "how it works" for technical users who want to understand the system.
|
|
||||||
|
|
||||||
**Competitors don't have this** — they just pass raw prompts to model.
|
**Competitors don't have this** — they just pass raw prompts to model.
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,8 +1,8 @@
|
||||||
# Competitive Analysis
|
# Competitive Analysis
|
||||||
|
|
||||||
**Date:** November 2, 2025 (Updated: January 9, 2026)
|
**Date:** November 2, 2025
|
||||||
**Status:** ✅ Updated - Template System = primary feature (Prompt Enhancement = technical implementation), MCP/CLI = table stakes
|
**Status:** ✅ Updated with Runware + ImageKit research
|
||||||
**Version:** 1.1
|
**Version:** 1.0
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
|
|
@ -34,14 +34,11 @@
|
||||||
|
|
||||||
## Our Competitive Advantages
|
## Our Competitive Advantages
|
||||||
|
|
||||||
### 1. Template System (PRIMARY MOAT)
|
### 1. Prompt Enhancement (PRIMARY MOAT)
|
||||||
- Generic to Professional quality via intelligent templates
|
- Generic → Professional quality
|
||||||
- Granular enhancement: only fills missing prompt details
|
|
||||||
- Custom templates = Pro tier paid feature
|
|
||||||
- 3-6 months to replicate
|
- 3-6 months to replicate
|
||||||
- Always enabled, not optional
|
- Always enabled, not optional
|
||||||
- This is what justifies $0.10 vs $0.0006
|
- This is what justifies $0.10 vs $0.0006
|
||||||
- **Technical implementation:** Prompt Enhancement (AI analyzes and improves prompts) — the "how it works" for devs who want details
|
|
||||||
|
|
||||||
### 2. Consistency System (@references)
|
### 2. Consistency System (@references)
|
||||||
- Style/object persistence across generations
|
- Style/object persistence across generations
|
||||||
|
|
@ -54,14 +51,12 @@
|
||||||
- Transformations (with focal point detection)
|
- Transformations (with focal point detection)
|
||||||
- Zero manual work
|
- Zero manual work
|
||||||
|
|
||||||
### 4. Developer Experience (DX Suite)
|
### 4. Developer Experience
|
||||||
- MCP (Cursor/Claude Code)
|
- MCP (Cursor/Claude Code)
|
||||||
- SDK (programmatic)
|
- SDK (programmatic)
|
||||||
- CLI (terminal)
|
- CLI (terminal)
|
||||||
- Prompt URLs (universal)
|
- Prompt URLs (universal)
|
||||||
|
|
||||||
**Note (Jan 2026):** MCP/CLI/SDK are table stakes for 2026. All competitors will have them. Our moat is the *completeness and quality* of DX, not individual tools.
|
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
## Positioning vs Competitors
|
## Positioning vs Competitors
|
||||||
|
|
|
||||||
|
|
@ -1,160 +0,0 @@
|
||||||
# Positioning Updates - January 2026
|
|
||||||
|
|
||||||
**Date:** January 9, 2026
|
|
||||||
**Status:** ✅ Strategic decisions documented
|
|
||||||
**Purpose:** Summary of critical positioning changes to apply across documentation
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Critical Update #1: MCP/SDK/CLI Repositioning
|
|
||||||
|
|
||||||
### Change
|
|
||||||
|
|
||||||
**OLD positioning:**
|
|
||||||
> "First to MCP" as competitive moat
|
|
||||||
> MCP/SDK/CLI as unique differentiators
|
|
||||||
|
|
||||||
**NEW positioning:**
|
|
||||||
> MCP/SDK/CLI/Lab = **table stakes** for 2026
|
|
||||||
> Collectively they express "DX-first approach", not competitive advantage
|
|
||||||
|
|
||||||
### Rationale
|
|
||||||
|
|
||||||
- All serious competitors will have MCP in 2026
|
|
||||||
- Can be replicated in 2-4 weeks by any team
|
|
||||||
- Like having documentation — expected, not special
|
|
||||||
- "First to market" advantage is temporary (months, not years)
|
|
||||||
|
|
||||||
### What IS still defensible
|
|
||||||
|
|
||||||
1. **Template System** — Intelligent prompt analysis + granular application (3-6 months to replicate)
|
|
||||||
2. **@references consistency** — Unique, complex (post-MVP)
|
|
||||||
3. **Production pipeline** — CDN + transformations included
|
|
||||||
4. **DX quality** — Sum of all tools + docs + support
|
|
||||||
|
|
||||||
### Documentation updates required
|
|
||||||
|
|
||||||
| Document | Section | Change |
|
|
||||||
|----------|---------|--------|
|
|
||||||
| 01-market-positioning-v3.md | Competitive table | Remove MCP/CLI from "unique advantages" |
|
|
||||||
| 01-market-positioning-v3.md | Moat strategy | Reframe: "Complete DX suite" vs competitors' partial |
|
|
||||||
| 13-competitive-analysis.md | Competitor features | Update comparison to show MCP as expected |
|
|
||||||
| 16-product-features.md | MCP section | Reframe as "must-have" not "differentiator" |
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Critical Update #2: Template System (Marketing Reframe)
|
|
||||||
|
|
||||||
### Change
|
|
||||||
|
|
||||||
**OLD messaging:**
|
|
||||||
> "We enhance your prompts"
|
|
||||||
> (Sounds restrictive — "we change what you wrote")
|
|
||||||
|
|
||||||
**NEW messaging:**
|
|
||||||
> "Choose a template that matches your style"
|
|
||||||
> (User control — "you choose, we help")
|
|
||||||
|
|
||||||
### Key points
|
|
||||||
|
|
||||||
- Template is always applied (mandatory) — but framed as "ensures quality"
|
|
||||||
- Default template: **Photorealistic** (not "general")
|
|
||||||
- Granular enhancement:
|
|
||||||
- Short prompt → full template applied
|
|
||||||
- Partial prompt → fills missing details only
|
|
||||||
- Detailed prompt → passes through unchanged
|
|
||||||
- Custom templates = **Pro tier paid feature** (replaces separate stylization system)
|
|
||||||
|
|
||||||
### Full documentation
|
|
||||||
|
|
||||||
See: [execution/20-template-system.md](execution/20-template-system.md)
|
|
||||||
|
|
||||||
### Documentation updates required
|
|
||||||
|
|
||||||
| Document | Section | Change |
|
|
||||||
|----------|---------|--------|
|
|
||||||
| 16-product-features.md | Prompt Enhancement | Rename to "Template System" |
|
|
||||||
| 10-pricing-strategy.md | Pro features | Add "Custom Templates" as paid feature |
|
|
||||||
| Landing page copy | Feature descriptions | Update messaging |
|
|
||||||
| API documentation | Enhancement parameter | Add template selection |
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Critical Update #3: Resource Allocation (70/30)
|
|
||||||
|
|
||||||
### Decision
|
|
||||||
|
|
||||||
**70% effort:** SEO + Content (primary acquisition channel)
|
|
||||||
**30% effort:** API refinement + validation outreach
|
|
||||||
|
|
||||||
### Rationale
|
|
||||||
|
|
||||||
- Organic search = highest quality signal
|
|
||||||
- Content builds sustainable moat (competitors can't copy overnight)
|
|
||||||
- First Henry article published, pipeline validated
|
|
||||||
- API is "good enough" for validation flows
|
|
||||||
|
|
||||||
### Implications
|
|
||||||
|
|
||||||
- Don't over-engineer API features before validation
|
|
||||||
- Prioritize content production velocity
|
|
||||||
- SEO optimization is strategic, not tactical
|
|
||||||
- Direct outreach is secondary to organic discovery
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Critical Update #4: Validation Approach
|
|
||||||
|
|
||||||
### Current state
|
|
||||||
|
|
||||||
- 0 paying customers
|
|
||||||
- 0 interviews conducted
|
|
||||||
- 0 API feedback received
|
|
||||||
|
|
||||||
### Available validation flows
|
|
||||||
|
|
||||||
| Flow | Status |
|
|
||||||
|------|--------|
|
|
||||||
| Live URLs | ✅ Ready |
|
|
||||||
| Lab UI | TBD |
|
|
||||||
| API Integration | ✅ Ready |
|
|
||||||
| MCP | ❌ Not built |
|
|
||||||
|
|
||||||
### Approach catalog
|
|
||||||
|
|
||||||
8 approaches documented with reliability/cost/time analysis.
|
|
||||||
|
|
||||||
See: [execution/21-validation-approaches.md](execution/21-validation-approaches.md)
|
|
||||||
|
|
||||||
### Next step
|
|
||||||
|
|
||||||
Oleg decides which approach(es) to pursue. Recommendation: Discord AI Tools for best balance of reliability and speed.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Master Update Checklist
|
|
||||||
|
|
||||||
### High Priority (affects positioning)
|
|
||||||
|
|
||||||
- [ ] 01-market-positioning-v3.md — Remove MCP from unique advantages
|
|
||||||
- [ ] 01-market-positioning-v3.md — Update moat strategy section
|
|
||||||
- [ ] 13-competitive-analysis.md — Reframe competitor comparison
|
|
||||||
- [ ] 16-product-features.md — Rename "Prompt Enhancement" → "Template System"
|
|
||||||
|
|
||||||
### Medium Priority (affects pricing/features)
|
|
||||||
|
|
||||||
- [ ] 10-pricing-strategy.md — Add Custom Templates to Pro tier
|
|
||||||
- [ ] INDEX.md — Add documents #20, #21
|
|
||||||
- [ ] ROADMAP.md — Update current phase description
|
|
||||||
|
|
||||||
### Low Priority (can wait)
|
|
||||||
|
|
||||||
- [ ] Landing page messaging updates
|
|
||||||
- [ ] API documentation updates
|
|
||||||
- [ ] Marketing materials refresh
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
**Document owner:** @men
|
|
||||||
**Last updated:** January 9, 2026
|
|
||||||
**Status:** Reference for documentation updates
|
|
||||||
Loading…
Reference in New Issue