banatie-content/shared/target-audience.md

3.7 KiB

Target Audience (ICP)

Primary ICP: AI-First Developers

Who They Are

Developers who use AI coding tools (Claude Code, Cursor, Copilot, Windsurf) as core part of their workflow. They build web applications and need images but hate context-switching.

Demographics

  • Role: Frontend developers, full-stack developers, indie hackers
  • Experience: 2-10 years
  • Company: Solo/freelance, small startups, indie projects
  • Location: Global (English-speaking or English-proficient)
  • Tools: VS Code/Cursor, Claude Code, GitHub Copilot, React/Next.js

Psychographics

  • Value efficiency and automation over manual processes
  • Early adopters of AI tooling
  • Prefer API-first solutions over GUI tools
  • Willing to pay for time savings
  • Active in developer communities (Reddit, HN, Discord, Twitter)

Pain Points

  1. Context switching kills flow — leaving IDE to generate images breaks concentration
  2. Manual file management is tedious — download, rename, organize, import
  3. Consistency is hard — keeping visual style consistent across project
  4. AI image tools aren't developer-friendly — designed for artists, not devs

Jobs to Be Done

  • "Generate a hero image for my landing page without leaving my editor"
  • "Get consistent placeholder images for my components"
  • "Automate image generation in my build pipeline"
  • "Create project-specific image assets programmatically"

Where They Hang Out

  • r/ClaudeAI, r/ChatGPTCoding, r/cursor
  • Hacker News
  • Dev Twitter/X
  • Discord servers for AI coding tools
  • Dev.to, Hashnode

Buying Behavior

  • Try free tier first
  • Pay when they hit limits or need production features
  • Monthly subscription preferred over usage-based (predictable costs)
  • Will pay $10-50/month for tools that save significant time

Secondary ICP: Web Dev Agencies (Small)

Who They Are

Small web development agencies (3-10 people) building client websites and applications. Need images for multiple projects.

Pain Points

  • Managing images across many client projects
  • Keeping brand consistency per client
  • Time spent on asset preparation
  • Client requests for quick visual iterations

Value Proposition

  • Project-based organization
  • Consistent image generation per brand
  • API integration into existing workflows
  • Time savings across multiple projects

Tertiary ICP: E-commerce Builders

Who They Are

Developers building e-commerce solutions (Shopify apps, custom stores). Need product-related images.

Pain Points

  • Product image generation/enhancement
  • Lifestyle/marketing images
  • Consistent product photography style
  • Bulk image processing

Value Proposition

  • Product image generation
  • Style consistency across catalog
  • Integration with e-commerce platforms
  • Bulk operations

Anti-Personas (NOT Our Target)

1. Artists/Designers

  • Want fine creative control
  • Prefer Midjourney/Leonardo UI
  • Don't need developer integrations
  • Why not us: We're optimized for developer workflow, not creative exploration

2. Enterprise IT

  • Need extensive compliance/security
  • Require on-premise deployment
  • Long procurement cycles
  • Why not us: We're not enterprise-ready yet

3. Non-Technical Users

  • Need GUI-based tools
  • Don't understand APIs
  • Want drag-and-drop interfaces
  • Why not us: We're API-first, developer-focused

Validation Status

  • AI-first developers: Strong founder-market fit (Oleg's own experience)
  • 🔄 Web agencies: Needs external validation
  • 🔄 E-commerce: Needs external validation

Content Implications

When writing content:

  • Use technical terminology freely
  • Reference AI coding tools specifically
  • Focus on workflow integration, not image quality
  • Assume reader knows React/Next.js basics
  • Include code examples early and often