shipwright-cli 1.10.0 → 2.0.0

package/docs/strategy/01-market-research.md

@@ -0,0 +1,619 @@
+# Market Research: AI Coding Agent Landscape
+
+**Date:** February 2026
+**Author:** Market Research Analysis
+**Status:** Competitive Landscape & Strategic Positioning
+
+---
+
+## Executive Summary
+
+The AI coding agent market has experienced explosive growth in 2025-2026, with autonomous software engineering capabilities maturing rapidly. Leading models now exceed 80% success rates on standardized benchmarks, developer adoption has reached 85% by end of 2025, and market valuations project $8.5 billion by 2026 (reaching $35 billion by 2030).
+
+Shipwright occupies a unique position in this landscape: it is the only open-source, team-oriented orchestration platform designed specifically for multi-agent delivery pipelines with daemon-driven autonomous processing, persistent learning systems, and fleet operations across multiple repositories. This analysis identifies key competitors, market trends, and strategic differentiation opportunities.
+
+---
+
+## Competitive Landscape
+
+### Direct Competitors
+
+#### 1. **Devin (Cognition Labs)**
+
+**Status:** Commercial, $$$
+**Positioning:** Autonomous AI software engineer
+
+**Key Achievements:**
+
+- Production-deployed at thousands of companies (Goldman Sachs, Santander, Nubank)
+- 67% PR merge rate (up from 34% in 2024)
+- Produces 25% of Cognition's internal pull requests
+- 4x faster problem-solving, 2x more resource efficient than prior year
+
+**Strengths:**
+
+- Best-in-class single-agent capability for complex refactoring and feature work
+- High PR merge quality indicating strong contextual understanding
+- Proven production deployment track record
+- Clear roadmap for 50% internal code production by end of 2026
+
+**Weaknesses:**
+
+- Only 15% success rate on complex end-to-end tasks requiring senior judgment
+- No multi-agent orchestration (single Devin instance per task)
+- Proprietary, closed-source, vendor-locked
+- Expensive (no public pricing, but enterprise-tier cost)
+- No team collaboration features
+
+**Target Audience:** Enterprise teams wanting to offload junior engineer tasks; not suitable for cross-repo fleet operations
+
+---
+
+#### 2. **OpenHands (formerly OpenDevin)**
+
+**Status:** Open source, MIT license
+**Positioning:** Open platform for AI coding agents
+
+**Key Features:**
+
+- Model-agnostic (works with Claude, GPT, local LLMs)
+- Python SDK for composable agent definitions
+- CLI and cloud scalability (supports 1000s of agents)
+- 188+ contributors, 2100+ contributions
+- Evaluation harness with 15+ benchmarks
+
+**Strengths:**
+
+- Fully open source with permissive MIT license
+- Model flexibility (not locked to specific vendor)
+- Academic credibility (university partnerships)
+- Rich evaluation infrastructure
+- Community-driven development
+
+**Weaknesses:**
+
+- Lacks orchestration for multi-agent teams (designed for single agents at scale)
+- No daemon-driven autonomous issue processing
+- No persistent memory system
+- No DORA metrics or cost intelligence
+- No pipeline composition (no workflow/delivery pipeline)
+- Limited production deployment evidence
+
+**Target Audience:** Teams wanting to self-host agents; researchers; teams favoring flexibility over workflow automation
+
+---
+
+#### 3. **SWE-agent (Princeton/Stanford)**
+
+**Status:** Open source, academic research
+**Positioning:** Agent-computer interface for repository fixing
+
+**Key Technology:**
+
+- Custom agent-computer interface (ACI) optimized for file editing and repo navigation
+- Mini-SWE-agent: achieves >74% on SWE-bench verified in just 100 lines of Python
+- Presented at NeurIPS 2024
+
+**Strengths:**
+
+- Exceptional performance on SWE-bench (gold standard for code agents)
+- Minimal, elegant approach (100-line reference implementation)
+- Strong academic credentials
+- Highly efficient agent-environment interaction
+
+**Weaknesses:**
+
+- Single-agent only, no multi-agent orchestration
+- Research-focused, not production-optimized
+- No delivery pipeline or deployment automation
+- No daemon or autonomous processing
+- Limited persistence or learning systems
+- Essentially a benchmark-specific tool, not a production delivery platform
+
+**Target Audience:** Researchers, academics, teams benchmarking agent capability; not a production delivery solution
+
+---
+
+#### 4. **GitHub Copilot Workspace + Agent Mode**
+
+**Status:** Commercial (Microsoft/GitHub)
+**Positioning:** AI agents integrated into GitHub
+
+**Recent Developments (2025):**
+
+- Agent Mode: iterative self-correction, error recognition, auto-fixing
+- Coding Agent (GA in May 2025): asynchronous autonomous developer agent
+- Model Context Protocol (MCP) support for custom tools
+- "Project Padawan": future autonomous task completion from issue to PR
+
+**Strengths:**
+
+- Native GitHub integration (issues → agent → PR → merge workflow)
+- Multi-model choice (Claude, GPT via MCP)
+- Asynchronous execution (can work in background)
+- Mission Control: parallel task orchestration for large refactors
+- Built-in at $20/month for Copilot Pro users
+
+**Weaknesses:**
+
+- Proprietary, closed-source
+- No cross-repo fleet operations
+- No daemon-driven issue watching (GitHub-native only)
+- Limited multi-agent team coordination
+- No persistent learning or memory system
+- Pricing per-user, not per-task
+
+**Target Audience:** Teams already on GitHub; enterprises with Copilot Pro; teams wanting low-friction integration
+
+---
+
+#### 5. **Cursor IDE, Windsurf, Cline**
+
+**Status:** Commercial/Open source hybrid
+**Positioning:** AI-powered development environments
+
+**Market Context:**
+
+- 85% of developers use some form of AI coding tool by end of 2025
+- Cursor: $20/month, strong on IDE polish
+- Windsurf: acquired by Cognition (Devin's parent), $15/month, deep agentic planning
+- Cline: open-source, runs in VS Code or terminal, local-first control
+
+**Strengths:**
+
+- Seamless IDE integration (chat, autocomplete, refactor in one environment)
+- Cursor/Windsurf are feature-rich and mature
+- Cline offers transparency and local control
+- Multi-file editing with diff visualization
+
+**Weaknesses:**
+
+- Interactive-only (no daemon for autonomous background processing)
+- No pipeline automation or deployment
+- No cross-repo orchestration
+- No memory or learning systems
+- Designed for individual developer workflows, not team delivery
+
+**Target Audience:** Individual developers; teams using VS Code; teams wanting polished IDE experience
+
+---
+
+#### 6. **Amazon Q Developer Agent**
+
+**Status:** Commercial, AWS service
+**Positioning:** Enterprise AI coding assistant for AWS
+
+**2025 Performance:**
+
+- 51% SWE-bench verified (state-of-the-art in April 2025)
+- 66% on full SWE-bench dataset
+- Pricing: $19/user/month
+
+**Strengths:**
+
+- Strong SWE-bench performance
+- Deep AWS service knowledge
+- Expanded language support (Dart, Go, Kotlin, Rust, Bash, Terraform, etc.)
+- Enterprise support and compliance
+- Generous capacity (1000 agentic interactions/month, 4000 LOC/month transformations)
+
+**Weaknesses:**
+
+- AWS-centric (optimization bias toward AWS patterns)
+- Proprietary, vendor-locked
+- No multi-agent orchestration
+- No daemon or autonomous processing
+- No cross-repo fleet operations
+- Limited deployment to AWS only
+
+**Target Audience:** AWS-native enterprises; teams using AWS infrastructure; large enterprises wanting compliance
+
+---
+
+#### 7. **v0 by Vercel**
+
+**Status:** Commercial SaaS
+**Positioning:** AI UI/full-stack code generation for Next.js
+
+**2026 Roadmap:**
+
+- Full-stack app generation (not just UI)
+- End-to-end agentic workflows
+- Self-driving deployment infrastructure
+- 6M+ developers, 80K+ active teams
+
+**Strengths:**
+
+- Specialized for React/Next.js (deep optimization)
+- Vercel infrastructure integration
+- UI-first feedback loop (see code working immediately)
+- Full-stack ambitions for 2026
+
+**Weaknesses:**
+
+- Narrow focus (Next.js/React only)
+- Not suitable for non-web or monolith codebases
+- No multi-agent orchestration
+- No cross-repo or fleet operations
+- Interactive-only
+
+**Target Audience:** Frontend-heavy teams; Next.js/React shops; startups building web apps
+
+---
+
+#### 8. **Aider**
+
+**Status:** Open source, GPLv3
+**Positioning:** Terminal-based AI pair programming with Git integration
+
+**Key Features:**
+
+- Multi-file editing with Git commit tracking
+- Works with any LLM (Claude, GPT-4, local models)
+- Codebase-aware (builds internal maps)
+- CLI-native workflow
+
+**Strengths:**
+
+- Highly trusted in terminal/CLI environments
+- Strong git integration (every edit is a commit)
+- Model-agnostic
+- Proven for refactors and multi-file changes
+- Small, focused scope
+
+**Weaknesses:**
+
+- CLI-only (not web/IDE-based)
+- No autonomous processing (interactive only)
+- No pipeline or deployment automation
+- No multi-agent or team features
+- No memory or learning systems
+
+**Target Audience:** Terminal-loving developers; teams wanting git-native workflows; DevOps engineers
+
+---
+
+### Adjacent Competitors: General Agent Orchestration Frameworks
+
+These are not code-specific but compete for the multi-agent orchestration and workflow automation layers:
+
+**CrewAI:** Role-playing agent framework, good for multi-agent workflows but not code-optimized
+**AutoGen (Microsoft):** Open-source multi-agent orchestration, general-purpose
+**LangGraph:** Graph-based task orchestration (DAG model), general-purpose
+
+**Gap:** None of these are specialized for software delivery pipelines, team coordination in version control workflows, or autonomous issue processing.
+
+---
+
+## Competitive Matrix
+
+| Feature                   | Devin         | OpenHands | SWE-agent | Copilot        | Cursor      | Amazon Q    | v0          | Aider    | Shipwright             |
+| ------------------------- | ------------- | --------- | --------- | -------------- | ----------- | ----------- | ----------- | -------- | ---------------------- |
+| **Model**                 | Proprietary   | Agnostic  | Agnostic  | Agnostic (MCP) | Proprietary | Proprietary | Proprietary | Agnostic | Agnostic (uses Claude) |
+| **Open Source**           | ✗             | ✓         | ✓         | ✗              | Limited     | ✗           | ✗           | ✓        | ✓                      |
+| **Single Agent**          | ✓             | ✓         | ✓         | ✓              | ✓           | ✓           | ✓           | ✓        | ✓                      |
+| **Multi-Agent Teams**     | ✗             | ✗         | ✗         | Limited        | ✗           | ✗           | ✗           | ✗        | **✓**                  |
+| **Autonomous Processing** | ✓             | ✗         | ✗         | Async          | ✗           | ✗           | ✗           | ✗        | **✓**                  |
+| **Daemon-Driven**         | ✗             | ✗         | ✗         | ✗              | ✗           | ✗           | ✗           | ✗        | **✓**                  |
+| **Issue Watching**        | ✗             | ✗         | ✗         | GitHub-native  | ✗           | ✗           | ✗           | ✗        | **✓ (multi-tracker)**  |
+| **Fleet Operations**      | ✗             | ✗         | ✗         | ✗              | ✗           | ✗           | ✗           | ✗        | **✓**                  |
+| **Delivery Pipeline**     | ✗             | ✗         | ✗         | Basic          | ✗           | ✗           | Basic       | ✗        | **✓ (12 stages)**      |
+| **Persistent Memory**     | ✗             | ✗         | ✗         | ✗              | ✗           | ✗           | ✗           | ✗        | **✓**                  |
+| **DORA Metrics**          | ✗             | ✗         | ✗         | ✗              | ✗           | ✗           | ✗           | ✗        | **✓**                  |
+| **Cost Intelligence**     | ✗             | ✗         | ✗         | ✗              | ✗           | ✗           | ✗           | ✗        | **✓**                  |
+| **Git Worktrees**         | ✗             | ✗         | ✗         | ✗              | ✗           | ✗           | ✗           | ✗        | **✓**                  |
+| **Interactive Only**      | ✗             | ✓         | ✓         | ✓              | ✓           | ✓           | ✓           | ✓        | ✗                      |
+| **IDE Integration**       | ✗             | ✗         | ✗         | Native         | Native      | ✗           | Web         | ✗        | tmux                   |
+| **Pricing**               | Enterprise $$ | Free/OSS  | Free/OSS  | $20/mo         | $20/mo      | $19/user/mo | Freemium    | Free/OSS | **Free/OSS**           |
+
+---
+
+## Market Trends & Insights
+
+### 1. **Benchmark Performance Explosion**
+
+- **SWE-bench Verified:** Top models now exceed 80% (Claude Opus 4.6 leads at 80.8%)
+- **Reality Gap:** Despite high benchmark scores, real-world production success remains 23-25% on SWE-bench Pro (stricter evaluation)
+- **Lesson:** The gap between lab performance and production suggests that agent orchestration, workflow automation, and learning systems will be competitive differentiators
+
+**Implication for Shipwright:** Persistent memory, DORA metrics, and pipeline composition address this gap by learning from failures and improving over time.
+
+---
+
+### 2. **AI Agent Market Growth**
+
+- **2025 Developer Adoption:** 85% of developers use some form of AI coding tool
+- **Market Projection:** $8.5B by 2026, $35B by 2030
+- **Risk:** 40% of agentic AI projects could be cancelled by 2027 due to cost, scaling complexity, or risk
+
+**Implication for Shipwright:** Open-source, self-hosted positioning addresses cost and compliance concerns. Autonomous daemon addresses complexity concerns by reducing manual orchestration burden.
+
+---
+
+### 3. **Shift from Code Generation to Workflow Automation**
+
+- **2024-2025:** Focus was on single-agent capability (Devin, SWE-agent, Copilot)
+- **2026 Trend:** Market moving toward multi-agent teams, orchestration, and delivery pipelines
+- **Evidence:** Devin's shift to "fleet management," Copilot's Mission Control, Vercel's agentic workflows, GitHub's Project Padawan
+
+**Implication for Shipwright:** This is exactly Shipwright's core value: multi-agent orchestration, delivery pipelines, fleet operations. The market is moving toward this positioning.
+
+---
+
+### 4. **Model Vendor Lock-in vs. Flexibility**
+
+- **Proprietary Tools:** Devin, Cursor, Windsurf, Amazon Q are locked to specific models
+- **Flexible Tools:** OpenHands, SWE-agent, Claude Code, Aider support model switching
+- **2026 Trend:** MCP (Model Context Protocol) and A2A (Agent-to-Agent) protocols emerging as interoperability standards
+
+**Implication for Shipwright:** Agnostic to Claude Code (could theoretically support other agents). This positions Shipwright as a platform layer, not a vendor lock-in tool.
+
+---
+
+### 5. **Autonomous vs. Interactive**
+
+- **Interactive Tools Dominate:** Most tools (Cursor, Windsurf, Copilot, Aider) require human-in-the-loop
+- **Autonomous Leaders:** Devin and Copilot Agent Mode pioneer background processing
+- **2026 Direction:** Enterprises increasingly demand autonomous, asynchronous processing (teams don't want to babysit agents)
+
+**Implication for Shipwright:** Daemon-driven autonomous processing is a strong differentiator. Competitors are just starting to offer this; Shipwright has it built-in.
+
+---
+
+### 6. **Team Collaboration & Multi-Agent Trends**
+
+- **Current State:** Most tools are single-agent or single-user focused
+- **Emerging:** GitHub Copilot Workspace, Devin teams, Claude Code agent teams
+- **Challenge:** Coordinating multiple agents without conflicts or duplicate work
+- **Solution:** Enterprise frameworks (CrewAI, AutoGen, LangGraph) still generic; none purpose-built for software delivery
+
+**Implication for Shipwright:** Multi-agent team orchestration with git-based coordination (worktrees, branch isolation) is a rare capability. This is a strong market differentiator.
+
+---
+
+### 7. **Enterprise Adoption Requirements**
+
+Enterprises moving beyond proof-of-concept demand:
+
+- **Cost Visibility:** Token usage, budget controls, ROI tracking
+- **Audit Trail:** What changed, why, approval workflows
+- **Integration:** GitHub, Linear, Jira, Slack, CI/CD pipelines
+- **Compliance:** Self-hosted, data privacy, role-based access
+
+**Implication for Shipwright:** Cost intelligence, memory system, GitHub/Linear/Jira integration, tmux-native workflow, open-source self-hosting all address enterprise adoption barriers.
+
+---
+
+### 8. **Specialization vs. Generalization**
+
+- **Specialized Wins:** v0 (React/Next.js), SWE-agent (benchmark optimization), Devin (end-to-end tasks)
+- **Generalist Tools:** OpenHands, Claude Code, Aider (any language, any task)
+- **Market Lesson:** Specialization wins on depth; generalization wins on breadth
+
+**Implication for Shipwright:** Positioned as a delivery platform (generalist), but can specialize via templates, team configurations, and domain-specific agent definitions.
+
+---
+
+## Shipwright's Unique Market Position
+
+### What Shipwright Does That Competitors Don't
+
+| Capability                          | Unique to Shipwright? | Value Proposition                                                                                   |
+| ----------------------------------- | --------------------- | --------------------------------------------------------------------------------------------------- |
+| Multi-agent team orchestration      | Nearly unique         | Parallel feature work, cross-layer coordination (frontend+backend+tests)                            |
+| Daemon-driven autonomous processing | Nearly unique         | Background issue watching → full pipeline without manual intervention                               |
+| Fleet operations (multi-repo)       | Unique                | Scale orchestration across 10+ repos with single daemon                                             |
+| Persistent memory system            | Unique                | Agents learn from failures, improve over time, capture institutional knowledge                      |
+| DORA metrics integration            | Unique                | Measure delivery performance (lead time, deployment frequency, CFR, MTTR)                           |
+| Cost intelligence                   | Unique                | Token budgeting, cost per issue, ROI tracking                                                       |
+| Git worktree isolation              | Unique                | True parallel pipelines without branch conflicts                                                    |
+| 12-stage delivery pipeline          | Unique                | intake → plan → design → build → test → review → quality → PR → merge → deploy → validate → monitor |
+| Issue tracker integration           | Unique                | GitHub, Linear, Jira bidirectional sync with daemon auto-processing                                 |
+| tmux-native workflow                | Unique                | Professional TUI, team panes, session persistence, Claude Code optimized                            |
+| Open source + self-hosted           | Rare                  | All features available without vendor lock-in                                                       |
+
+---
+
+## Market Gaps Shipwright Fills
+
+### Gap 1: No One Orchestrates Multi-Agent Teams for Delivery
+
+**Problem:** Devin, Copilot, OpenHands are single-agent. GitHub/Copilot have limited multi-agent support.
+**Shipwright Solution:** Full multi-agent team orchestration with role-based coordination (builder, reviewer, tester, optimizer, docs, security).
+
+### Gap 2: No One Processes Issues Autonomously at Scale
+
+**Problem:** All tools require human interaction. No daemon watching GitHub for labeled issues.
+**Shipwright Solution:** Daemon watches GitHub, Linear, Jira → spawns teams → full pipeline → auto-merge/deploy.
+
+### Gap 3: No One Operates Across Multiple Repos
+
+**Problem:** All tools optimize for single-repo or single-codebase.
+**Shipwright Solution:** Fleet operations with shared worker pool, rebalancing, fleet metrics.
+
+### Gap 4: No One Learns from Failures
+
+**Problem:** Each agent run is isolated. No institutional knowledge transfer.
+**Shipwright Solution:** Memory system captures failure patterns, injects context into future runs, agents improve over time.
+
+### Gap 5: No One Measures Delivery Performance
+
+**Problem:** No visibility into DORA metrics (lead time, deployment frequency, CFR, MTTR).
+**Shipwright Solution:** Native DORA metrics, self-optimization based on metrics.
+
+### Gap 6: No One Provides True Cost Visibility
+
+**Problem:** Token usage hidden, budgeting impossible, ROI unclear.
+**Shipwright Solution:** Token tracking, daily budgets, cost per issue, cost forecasting.
+
+---
+
+## Competitive Threats & Responses
+
+### Threat 1: Devin Continues to Improve
+
+**Status:** Devin produces 25% of Cognition's code, targeting 50% by end of 2026
+**Risk Level:** High for single-agent use cases
+**Shipwright Response:**
+
+- Devin excels at single complex tasks, but can't coordinate multi-agent teams
+- Shipwright positions as the "orchestration layer" — you could theoretically use Devin agents within Shipwright pipelines (via API)
+- Focus messaging on team coordination, multi-repo ops, autonomous processing
+
+### Threat 2: GitHub Copilot Workspace Becomes Default
+
+**Status:** Copilot is $20/month for 300M+ GitHub users
+**Risk Level:** High for GitHub-native teams
+**Shipwright Response:**
+
+- Copilot is interactive-only and GitHub-only; Shipwright is autonomous, multi-tracker (GitHub + Linear + Jira)
+- Copilot integrations are MCP-friendly; Shipwright can coexist (use Copilot agents within Shipwright)
+- Open source, self-hosted model addresses enterprise compliance concerns
+
+### Threat 3: OpenHands Gains Production Traction
+
+**Status:** 188+ contributors, MIT license, fast-growing
+**Risk Level:** Medium (positioned differently but overlapping audience)
+**Shipwright Response:**
+
+- OpenHands is a single-agent framework at scale; Shipwright is multi-agent orchestration
+- OpenHands lacks daemon, pipeline, fleet, memory, DORA metrics
+- Could integrate: Shipwright could spawn OpenHands agents in pipelines
+
+### Threat 4: Proprietary Tools Commoditize Open Source
+
+**Status:** Cursor, Windsurf, Devin all moving downmarket
+**Risk Level:** Medium for developer mindshare
+**Shipwright Response:**
+
+- Shipwright appeals to enterprises and teams wanting self-hosted, cost-predictable solutions
+- Developer adoption isn't the goal; team delivery efficiency is
+- Focus on DevOps/platform engineers and CTOs, not individual developers
+
+---
+
+## Strategic Recommendations
+
+### 1. **Own the "Orchestration" Market**
+
+Position Shipwright as the orchestration platform for AI agents. Even if Devin or Copilot Agent Mode become the best single agents, Shipwright is the "controller" for teams of agents.
+
+**Messaging:** "Devin is a junior engineer. Shipwright is the engineering manager."
+
+### 2. **Focus on Enterprise Adoption Drivers**
+
+Enterprises care about:
+
+- **Cost control:** Implement token budgeting, per-issue cost tracking, ROI dashboards
+- **Compliance:** Self-hosted, audit trails, role-based access
+- **Integration:** Deep GitHub/Linear/Jira support, CI/CD webhooks, Slack notifications
+- **Metrics:** DORA metrics, burn charts, velocity tracking
+
+### 3. **Build a Market for Autonomous Delivery**
+
+Most tools are interactive. Position Shipwright as "the autonomous delivery platform" — teams configure it once, daemon runs in background, PRs arrive pre-reviewed.
+
+**Differentiator:** "Write once, ship continuously."
+
+### 4. **Develop Agent Marketplace**
+
+Create a marketplace for pre-built agents, team templates, and pipeline configurations. This creates network effects and switching costs.
+
+**Examples:**
+
+- Agent: "Security Specialist" (scans for OWASP Top 10)
+- Agent: "Performance Reviewer" (benchmarks before/after)
+- Template: "Monolith to Microservices" (multi-agent refactor)
+- Template: "Legacy Framework Upgrade" (coordinated dependency updates)
+
+### 5. **Memory as a Competitive Moat**
+
+Invest heavily in the memory system. Agents that learn from failures are 2-3x more effective than those that don't.
+
+**Market Positioning:** "Agents that get smarter with every issue."
+
+### 6. **Target the "DevOps/Platform Team" Buyer**
+
+These teams:
+
+- Want to scale developer productivity without hiring
+- Care about metrics and ROI
+- Manage multiple repos/teams
+- Run in-house infrastructure
+
+**Shipwright fits perfectly:** "A platform engineering tool for AI."
+
+### 7. **Prepare for LLM Model Commoditization**
+
+As Claude, GPT, and others converge on capability, orchestration and workflow will be the differentiator.
+
+**Strategy:** Make Shipwright model-agnostic (can swap Claude for any LLM via API). This future-proofs against model commoditization.
+
+---
+
+## Market Sizing Estimates
+
+### Total Addressable Market (TAM)
+
+- **Enterprise teams** managing 10+ repos: ~100K globally
+- **Cloud-native orgs** with CI/CD: ~500K globally
+- At $50-200/month per team = $50M-100M/year market
+
+### Serviceable Addressable Market (SAM)
+
+- **Tier 1:** Tech companies, fast-growth startups: ~50K teams
+- At $100-300/month = $50M-150M/year
+
+### Shipwright Target (SOM)
+
+- **Year 1:** 100 teams (free/open source, early adopters)
+- **Year 2:** 500 teams (commercial + open source mix)
+- **Year 3:** 2000 teams
+- At average $50/month (blended): $1.2M/year by year 3
+
+---
+
+## Conclusion
+
+Shipwright operates in a market with clear tailwinds:
+
+- Multi-agent orchestration is emerging as critical
+- Autonomous, daemon-driven processing is becoming table stakes
+- Enterprise adoption is increasing, driving demand for self-hosted, auditable solutions
+- Market is moving from code generation (where proprietary tools lead) to delivery pipeline automation (where open, flexible platforms win)
+
+**Unique value proposition:** The only open-source platform for autonomous, multi-agent, multi-repo software delivery with persistent learning and complete observability.
+
+**Key success factors:**
+
+1. Aggressive investment in memory system and agent learning
+2. Deep enterprise integrations (GitHub, Linear, Jira, Slack, CI/CD)
+3. Cost intelligence as a first-class feature
+4. Agent and template marketplace to build network effects
+5. Positioning as "orchestration layer," not single-agent competitor
+
+**6-month priorities:**
+
+- Ship memory system v2 (failure pattern injection)
+- Launch cost intelligence dashboard
+- Add Linear/Jira parity with GitHub
+- Develop 3-5 production agent templates
+- Secure 10 enterprise pilot customers
+
+---
+
+## Sources
+
+- [Cognition | Devin's 2025 Performance Review](https://cognition.ai/blog/devin-annual-performance-review-2025)
+- [OpenHands | The Open Platform for Cloud Coding Agents](https://openhands.dev/)
+- [SWE-agent | GitHub Repository](https://github.com/SWE-agent/SWE-agent)
+- [GitHub Copilot | Agent Mode and Features](https://github.com/newsroom/press-releases/agent-mode)
+- [Cursor IDE vs Windsurf Comparison](https://research.aimultiple.com/ai-code-editor/)
+- [Amazon Q Developer | 2025 Updates](https://aws.amazon.com/blogs/devops/april-2025-amazon-q-developer/)
+- [v0 by Vercel | Building Agents and Apps](https://v0.app/)
+- [Aider | AI Pair Programming in Terminal](https://aider.chat/)
+- [Claude Code | Agent Teams Orchestration](https://code.claude.com/docs/en/agent-teams)
+- [AI Coding Agent Market Trends 2026](https://blog.logrocket.com/ai-dev-tool-power-rankings)
+- [SWE-Bench Performance Leaderboard](https://scale.com/leaderboard/swe_bench_pro_public)
+- [AI Agent Orchestration Frameworks 2026](https://aimultiple.com/agentic-orchestration)
+- [Deloitte | AI Agent Orchestration 2026](https://www.deloitte.com/us/en/insights/industry/technology/technology-media-and-telecom-predictions/2026/ai-agent-orchestration.html)