4.5 KiB
ICP Segmentation: Unified Approach
Date: November 2, 2025
Status: ✅ Validated - One product, multiple segments
Version: 1.0
Key Insight: ONE Product, Multiple Entry Points
Technical implementation: IDENTICAL for all segments
Difference: Entry point preference + use case emphasis
Segment Profiles
A: Studios/Agencies (3-10 people)
Profile:
- Tech lead + 1-2 juniors
- Build sites for clients
- CEO/Manager makes buying decisions
Pain Points:
- Client approval blocked without realistic images
- Placeholder hell (projects stall 1-2 months)
- Generic stock photos = unprofessional
Preferred Entry Points:
- REST API (integration)
- Web UI (client presentations)
- Prompt URLs (easy for team)
Use Case: Client mockup approval
Pricing Preference: Subscription ($49-99/mo)
Sales Cycle: Medium (B2B, need demos)
B: Power Users (Tech Leads) ⭐ PRIMARY
Profile:
- Uses Cursor/Claude Code daily
- Builds web projects with AI agents
- Can influence team adoption
Pain Points:
- Stock photos generic, overused
- Manual Midjourney workflow tedious
- Context switching between tools
Preferred Entry Points:
- MCP (Cursor integration) - PRIMARY
- SDK (programmatic)
- CLI (terminal)
Use Case: Coding workflow automation
Pricing Preference: Subscription ($49/mo)
Sales Cycle: Fast (self-serve, product-led)
Budget: Already pays $20-200/mo for AI tools
C: Freelancers (Solo)
Profile:
- Builds sites for clients
- Price-sensitive
- Fast decision maker (no approval needed)
Pain Points:
- Stock photos unprofessional
- Client approval slow
- Budget constraints
Preferred Entry Points:
- REST API
- Web UI
- Prompt URLs
Use Case: Per-project images
Pricing Preference: Credits (pay-as-you-go)
Sales Cycle: Fast (self-serve)
D: AI-Savvy Freelancers ⭐ SECONDARY
Profile:
- Active AI tool user (Cursor, ChatGPT)
- High project volume
- Time = money mindset
Pain Points:
- Manual workflows slow
- Generic images hurt quality
- Need fast turnaround
Preferred Entry Points:
- MCP (automation)
- SDK (if codes)
- Prompt URLs (if not)
Use Case: Fast project delivery
Pricing Preference: Credits or Subscription (high volume)
Sales Cycle: Fast (self-serve)
Budget: Already pays for AI tools
Technical Product = SAME
Backend:
- Prompt enhancement (always on)
- Gemini 2.5 Flash generation
- 6 aspect ratios
- CDN delivery
- Transformations (with focal point)
Interfaces:
- MCP Server (for B/D)
- SDK (for B/D)
- CLI (for B/D)
- REST API (for all)
- Prompt URLs (for all)
- Web UI (for all)
Features:
- @references consistency (post-MVP)
- Team management (post-MVP, for A)
- Usage analytics (all)
GTM Strategy: Sequential Launch
Phase 1: Developer Focus (Weeks 1-4)
Target: B + D (AI developers)
Why first:
- Founder IS this ICP
- Fast validation
- Product-led growth
- MCP = differentiator
Channels:
- r/cursor, Discord
- Dev.to, Twitter
- Direct outreach
Message: "MCP for image generation in Cursor"
Goal: 5-10 paying users
Phase 2: Agency Expansion (Weeks 5-8)
Target: A + C (agencies, freelancers)
Why second:
- Product validated
- Add use case messaging
- Same tech, different frame
Channels:
- r/webdev, r/freelance
- LinkedIn (careful)
- Agency communities
Message: "Speed up client approval with AI mockups"
Goal: 10-20 additional users
Phase 3: Optimize (Weeks 9-12)
Analyze:
- Which segment converts better?
- Which has higher LTV?
- Which churns less?
Action: Double down on winner
Messaging by Segment
For B/D (Developers):
"Generate unique images without leaving Cursor. MCP integration for AI coding workflows."
Emphasis: Automation, speed, quality
For A (Agencies):
"Speed up client approval with realistic AI mockups. Stop waiting for client content."
Emphasis: Client approval, professional quality, faster payment
For C (Freelancers):
"Stop using generic stock photos. Generate unique images for client sites."
Emphasis: Affordability, uniqueness, professionalism
Overlap: Many people are BOTH
Example: Tech lead at small agency
- Morning: Codes in Cursor (uses MCP)
- Afternoon: Client presentation (uses Web UI)
- Same person, two use cases
This validates unified product approach.
Last updated: November 2, 2025
Next review: After customer interviews validate segments