banatie-strategy/ROADMAP.md

14 KiB

Banatie Project Roadmap

📅 Date Management Approach

Philosophy: Dates for completed work (track velocity), estimates for future work (reduce stress).

  • Completed tasks: Record actual completion date
  • 🔄 In progress: Show start date + estimated duration
  • 📅 Future tasks: Show estimated duration only (e.g., "2-4 weeks", "3 months")
  • 🎯 Milestones: Relative timeframes from key decision points (e.g., "Month 3 after validation")

Why: With 15-20 hrs/week availability, fixed deadlines create false pressure. Relative estimates allow flexibility while tracking actual velocity for better future planning.


🎯 Current Status

Phase: Pre-launch / ICP Validation Version: 1.1 Next Milestone: Complete ICP External Validation


Completed Sprint: Foundation (Oct 20 - Oct 30)

COMPLETED

  • Market positioning clarified (Completed: Oct 25, 2025)
  • ICP hypothesis validated internally - founder IS the ICP (Completed: Oct 28, 2025)
  • Pricing strategy drafted - hybrid credits + subscription model (Completed: Oct 29, 2025)
  • MVP scope defined - MCP + core features (Completed: Oct 30, 2025)
  • Documentation framework established - filesystem MCP approach (Completed: Oct 30, 2025)

🔄 Active Sprint: ICP External Validation

Started: Oct 31, 2025 Est. duration: 2 weeks Owner: Oleg

Status

  • Interviews completed: 0 / 10
  • Decision: GO/PIVOT/STOP pending

Tasks

  • Create throwaway Reddit account (stealth mode)
  • Post in r/ClaudeAI: "How do you handle images in Claude Code?"
  • Post in r/ChatGPTCoding: "AI-assisted devs: image generation workflow?"
  • Conduct 10-15 text-based interviews via DM
  • Fill validation scorecard after each interview
  • Make GO/PIVOT/STOP decision based on results

⏸️ BLOCKED / WAITING

  • MVP development (blocked by: need confirmed feature priorities from validation)
  • Beta user outreach (blocked by: need validated messaging)
  • Pricing finalization (blocked by: need ICP confirmation of willingness to pay)

📅 Upcoming Milestones

Post-Validation Phase (1-2 weeks after validation decision)

IF GO decision (60%+ willing to use, 40%+ willing to pay $20+):

  • Finalize MVP scope based on validated top 3 needs from interviews
  • Begin MCP server development
  • Prepare beta access list from interviews (early adopters identified)
  • Plan soft launch strategy (Reddit post schedule, messaging)

IF PIVOT decision (<60% interest OR weak willingness to pay):

  • Select alternative ICP (agencies? e-commerce? different dev segment?)
  • Prepare new interview script tailored to alternative ICP
  • Run 5-10 more interviews (est. 1-2 weeks)
  • Final GO/STOP decision

IF STOP decision (<40% interest, no one willing to pay):

  • Document learnings (what didn't work, what insights gained)
  • Thank all interviewees professionally
  • Decide: tackle different problem OR shut down project
  • Focus energy back on day job (reduce stress, reassess in 3-6 months)

MVP Development Phase (4-6 weeks)

(Assuming GO decision)

Est. duration: 4-6 weeks total

  • Weeks 1-2: Core generation pipeline + MCP integration

    • REST API endpoints finalized
    • Prompt Enhancement Agent working
    • Image generation with @name references
    • Basic storage + CDN integration
    • Deliverable: Working API (generate + upload + references)
  • Week 3: MCP implementation

    • MCP server setup (follow spec)
    • Implement 3 tools: banatie_generate, banatie_upload, banatie_list_images
    • Test with Claude Desktop
    • Documentation for MCP usage
    • Deliverable: Working MCP integration
  • Week 4: Transformations + UI refinement

    • Image transformation service (Imageflow or Cloudflare)
    • Refine demo UI (code snippets, transformation previews)
    • Dashboard (history, usage stats)
    • API key management
    • Deliverable: Functional UI for testing
  • Week 5: Payments + polish

    • Stripe integration (credit packs: $20, $50, $100)
    • Free tier limits enforcement (10/month with watermark)
    • Landing page copy + design
    • API documentation (REST + MCP)
    • Deliverable: Monetization-ready product
  • Week 6: Beta testing + iteration

    • Invite 5-10 validated users from research
    • High-touch onboarding (help with MCP setup)
    • Gather feedback, fix critical bugs
    • Iterate on UX pain points
    • Deliverable: Product-market fit signals or pivot triggers

Soft Launch & Growth Phase (Months 3-6 after validation)

Month 3: First paying customers

  • Goal: 5-10 beta users onboarded
  • 50+ generations completed
  • 2+ users purchase credits (willingness to pay validated)
  • Target MRR: $200-500

Month 4: Soft launch to communities

  • Post in r/ClaudeAI: "Show HN: Generate images from Claude Code via MCP"
  • Indie Hackers build-in-public post
  • Dev.to technical content (tutorial: "Automate image gen in Next.js with Claude Code")
  • Target MRR: $500-1,000

Month 5: Growth optimization

  • SEO content (start ranking for "AI image generation API", "Claude Code images")
  • Community building (Discord, Reddit presence)
  • Case studies from early users
  • Target MRR: $1-2K (Side Project Validation milestone)

🎯 Long-term Goals (Relative Milestones)

Month 6 Checkpoint: Side Project Validation

Timeframe: ~6 months after validation Success criteria:

  • MRR: $1-2K
  • Customers: 10-20 paying
  • Churn: <5% monthly
  • Signal: Product-market fit OR clear pivot needed

Decision: Continue scaling OR reassess viability


Month 9 Checkpoint: Hybrid Mode Decision

Timeframe: ~9 months after validation Success criteria:

  • MRR: $3-5K
  • Customers: 30-50 paying
  • Usage: Predictable growth pattern

Options:

  • Negotiate 4-day work week with employer (80% salary = $4.8K)
  • OR: Stay full-time job, continue nights/weekends
  • Combined income: $7-10K/month (meets family needs + buffer)

Month 12 Checkpoint: Full-time Leap Evaluation

Timeframe: ~12 months after validation Success criteria:

  • MRR: $6K+ (current salary replacement)
  • OR: 12-month runway saved + high confidence in growth
  • OR: MRR = $4-5K + spouse (Ekaterina) involved in admin with income

Decision: Go full-time on Banatie OR continue hybrid

Long-term vision (24-36 months from validation):

  • $15-30K MRR: Sustainable solo/small team business
  • Hire 1-2 people (support, marketing, or tech)
  • Consider Ekaterina full-time on admin/ops

🚦 Decision Gates

GATE 1: ICP Validation (ACTIVE - Est. 2 weeks)

Started: Oct 31, 2025

Success criteria (ALL must be met):

  • 60%+ interviews say "I would use this" (6 out of 10)
  • 40%+ willing to pay $20+ (4 out of 10)
  • 30%+ want early access (3 out of 10)
  • KILLER USE CASE identified: ONE specific, frequent, expensive pain mentioned by 60%+ respondents (not scattered generic needs)
  • Budget confirmed (they pay for other tools)

Possible outcomes:

  • GO → Build MVP for AI developers (strong signals)
  • 🔄 PIVOT → Test different ICP (weak signals, add 1-2 weeks)
  • 🛑 STOP → Shut down or fundamental rethink (no market fit)

Review: Upon completion with @men


GATE 2: MVP Launch Readiness (Week 6 of MVP development)

Timeframe: ~6-8 weeks after Gate 1 GO decision

Success criteria:

  • MCP integration works reliably (95%+ success rate)
  • 5-10 beta users onboarded and generating images
  • 50+ generations completed (usage validated)
  • 2+ users purchase credits (monetization validated)
  • No critical bugs blocking core workflow

Possible outcomes:

  • LAUNCH → Soft launch to r/ClaudeAI, Indie Hackers
  • 🔄 ITERATE → Add 1-2 weeks for bug fixes, UX improvements
  • 🛑 PIVOT → Different approach needed (MCP too complex? Different features?)

Review: Upon completion


GATE 3: PMF Validation (Month 6 checkpoint)

Timeframe: ~6 months after Gate 1 GO decision

Success criteria:

  • $1-2K MRR achieved
  • <5% monthly churn (customers staying)
  • "Can't live without" feedback from 3+ users
  • Organic word-of-mouth starting (referrals, shares)
  • Usage growing without marketing spend

Possible outcomes:

  • SCALE → Invest in growth (content, partnerships, paid ads eventually)
  • 🔄 OPTIMIZE → Refine product, improve conversion
  • 🛑 PIVOT/STOP → No PMF achieved after 6 months, reassess fundamentally

Review: Upon reaching timeframe


⚠️ Risk Mitigation Watch

HIGH PRIORITY RISKS

1. Burnout Risk (Severity: HIGH)

  • Factors: Full-time job + side project + newborn (Kirill, 2 weeks old) + family of 5
  • Current exposure: Working 60+ hrs/week total (40 job + 20 Banatie)
  • Monitor: Weekly health check-ins (Sundays)
  • Mitigation:
    • Strict time boundaries (no work after 10 PM)
    • One full day off per week (family only)
    • Use Agent Coding (Claude Code) to maximize efficiency
    • Cut scope ruthlessly (MVP, not full vision)
  • Red flags: Physical health decline, family tension, day job performance suffering
  • Abort criteria: If health/family at risk, pause Banatie (not worth it)

2. Financial Pressure Risk (Severity: HIGH)

  • Factors: Zero savings buffer, school tuition coming, single income ($6K/month)
  • Current exposure: No emergency fund, Daniel's private school pending
  • Monitor: Monthly expense tracking, runway calculation
  • Mitigation:
    • Keep day job until Banatie ≥ $6K MRR (non-negotiable)
    • Negotiate hybrid work arrangement early (6-month mark if traction)
    • Bootstrap (no fundraising until PMF clear)
    • Minimize Banatie expenses (use family VPS, free tools)
  • Red flags: Credit card debt accumulating, school tuition unpaid, family stress over money
  • Abort criteria: If Banatie costs exceed $500/month without revenue

3. No PMF Risk (Severity: HIGHEST)

  • Factors: Unvalidated ICP, new category (convergence play), complex product
  • Current exposure: Hypothesis not yet tested with external users
  • Monitor: Interview feedback, churn rate, usage metrics, qualitative signals
  • Mitigation:
    • Brutal ICP validation BEFORE building more (current sprint)
    • Launch ultra-MVP (not full platform)
    • 10-15 customer interviews BEFORE launch
    • Set clear pivot triggers (see Phase 1 decision point)
  • Red flags: No one willing to pay, high churn (>10%), "cool idea, but..." feedback
  • Abort criteria: After 6 months, if <$500 MRR and no PMF signals → shut down

4. Employer Discovery Risk (Severity: MEDIUM)

  • Factors: Building side project while employed, same industry (web dev, AI)
  • Current exposure: Public presence needed for marketing (Twitter, LinkedIn, dev.to)
  • Monitor: LinkedIn/social mentions, colleague conversations
  • Mitigation strategies: (see backlog/06-future-topics-backlog.md - "свечение фейса")
    • Use separate brand identity (Banatie, not personal)
    • Delay LinkedIn posting until closer to launch
    • Focus on dev.to, Indie Hackers (less employer monitoring)
    • Check employment contract for IP clauses
  • Red flags: Employer asks about side projects, colleagues mention seeing Banatie
  • Abort criteria: If employer explicitly forbids, negotiate exit OR pause publicly

📊 Key Metrics Dashboard

Updated: Weekly (every Sunday evening)

Validation Metrics (Active Sprint)

Sprint started: Oct 31, 2025

  • Interviews completed: 0 / 10
  • Positive responses ("I would use"): - / -
  • Willing to pay $20+: - / -
  • Early access requests: - / -

Development Metrics (After GO decision)

  • MVP features completed: - / 8
  • Beta users onboarded: - / 10
  • Generations completed: - / 50
  • Credit purchases: - / 2

Business Metrics (Post-launch)

  • MRR: $0
  • Paying customers: 0
  • Churn rate: N/A
  • Conversion rate (Free → Paid): N/A
  • Usage per user (avg gens/month): N/A

🔮 Future Considerations (Not Currently Scheduled)

Features (Post-PMF, after 50+ users)

  • Flow-based chained generation (complex workflows)
  • On-demand URL generation (programmatic HTML generation)
  • Namespaces / project organization
  • Team collaboration features (multi-user, agencies)
  • Advanced style presets / fine-tuning

Market Expansion (After PMF with AI developers)

  • Agency tier ($149/mo for teams)
  • E-commerce vertical (product image generation, Shopify integration)
  • Enterprise tier (custom pricing, SLA, support)

Operations (After $10K MRR)

  • Hire VA for customer support
  • Involve Ekaterina (wife) in admin/ops
  • Consider part-time dev help for non-core features
  • Explore partnership opportunities (integrations, resellers)

📋 Action Items Summary

Active Sprint (ICP Validation - Started Oct 31):

  1. Create throwaway Reddit account
  2. Post validation questions in r/ClaudeAI and r/ChatGPTCoding
  3. Conduct 10 text-based interviews
  4. Document results in validation scorecard
  5. Make GO/PIVOT/STOP decision

After Validation - IF GO:

  1. Finalize MVP scope based on interview insights
  2. Set up development environment (if not already done)
  3. Begin MCP server implementation
  4. Prepare beta access list

After Validation - IF PIVOT:

  1. Select alternative ICP
  2. Prepare new interview script
  3. Begin second validation round (est. 1-2 weeks)

🎯 Success Definitions by Stage

Pre-launch Success (Current)

  • ICP validated externally (60%+ interest, 40%+ willing to pay)
  • MVP scope locked (based on validated needs)
  • First 5 beta users identified from research

Launch Success (Month 3-4)

  • 5-10 beta users actively using product
  • 50+ generations completed
  • 2+ credit purchases (willingness to pay confirmed)
  • No critical bugs blocking workflow

Early Traction Success (Month 6)

  • $1-2K MRR
  • <5% monthly churn
  • Product-market fit signals ("can't live without")
  • Organic growth starting (word-of-mouth, referrals)

Sustainability Success (Month 12)

  • $6K+ MRR (salary replacement level)
  • Predictable growth trajectory
  • Hybrid or full-time transition viable
  • Clear path to $10-15K MRR

Roadmap Owner: @men + Oleg (joint ownership) Last Updated: October 31, 2025 Next Review: Upon completion of ICP validation Version Control: Track major changes via Git commits


Quick Reference Commands:

  • Update metrics: Every Sunday evening
  • Review roadmap: After each decision gate
  • Update action items: As completed or priorities change
  • Archive completed sprints: When moving to next phase
  • Mark tasks complete: Record actual completion dates for velocity tracking