Problem
Development teams make technology choices (DB, framework, build vs buy) without structured decision processes:
- ADRs (Architecture Decision Records) are a recognized best practice, but too tedious to write manually — most teams skip them
- Later, nobody can answer “why did we choose this technology?”
- Existing ADR tools only provide empty templates — no AI-powered analysis
- Decision history gets lost, causing teams to repeat the same debates
Pain Intensity: 7/10 - A root cause of technical debt
Market
- Primary Market: Global dev teams, tech leads, architects
- Segment: Startups to mid-size companies needing to document technical decisions
- TAM: Engineering Effectiveness tools market $15-20B
- Key Fact: Zero AI-native commercial ADR tools. Existing tools (adr-tools, Log4brains) are OSS with stalled maintenance
Solution
DevDecision - AI-powered multi-perspective technical decision record generator
Core Features
- Natural Language Tech Comparison: Analyze technology options from a simple question
- 5-Perspective Auto-Analysis: Cost, scalability, team expertise, maintenance, community
- ADR Markdown Generation: Ready to paste into team wiki
- Past Decision Search/Reference: “What was our rationale for choosing this DB?”
- PR/Code Linkage: Bi-directional links between decisions and implementations
Usage Scenario
# Install
$ npm install -g devdecision
# Analyze a technical decision
$ devdecision "PostgreSQL vs MySQL for new e-commerce project"
🔍 Running multi-perspective analysis...
╔══════════════════════════════════════════════════╗
║ ADR-0042: PostgreSQL vs MySQL Selection ║
╠══════════════════════════════════════════════════╣
║ ║
║ 📊 Cost Perspective ║
║ PostgreSQL: Free (OSS), hosting $50-200/mo ║
║ MySQL: Free (OSS), Aurora $100-400/mo ║
║ → PostgreSQL advantage (30-40% lower TCO) ║
║ ║
║ 📈 Scalability Perspective ║
║ PostgreSQL: JSONB, partitioning, complex query ║
║ MySQL: Easy read replicas, fast simple queries ║
║ → PostgreSQL advantage for e-commerce ║
║ ║
║ 👥 Team Expertise Perspective ║
║ Team profile: 5 backend devs, 3 with PG exp ║
║ → PostgreSQL advantage (lower learning cost) ║
║ ║
║ 🔧 Maintenance Perspective ║
║ PostgreSQL: Complex upgrades, mature ecosystem ║
║ MySQL: Easy upgrades, Oracle dependency concern ║
║ → Tie ║
║ ║
║ 🌐 Community Perspective ║
║ PostgreSQL: Active on SO, growing momentum ║
║ MySQL: Larger absolute base, growth stagnant ║
║ → PostgreSQL advantage ║
║ ║
║ ✅ Conclusion: PostgreSQL recommended (4/5) ║
╚══════════════════════════════════════════════════╝
📄 ADR generated: ./decisions/adr-0042-postgresql-selection.md
# Search past decisions
$ devdecision search "database"
→ ADR-0042: PostgreSQL vs MySQL (2026-03-09)
→ ADR-0031: Redis vs Memcached (2026-01-15)
# Export to team wiki
$ devdecision export --format notion --id 0042
Competition
| Competitor | Price | Weakness |
|---|---|---|
| Workik AI ADR | Free | Basic templates only, no multi-perspective analysis |
| adr-tools | Free (OSS) | Bash scripts, no AI, no collaboration |
| Log4brains | Free (OSS) | Maintenance stalled, static site generator |
| Backstage ADR Plugin | Free | Requires full Backstage adoption, heavy infrastructure |
| dotnet-adr | Free | .NET ecosystem only, no cross-platform |
Competition Intensity: Low - Zero AI-native commercial ADR tools Differentiation: AI-powered multi-perspective auto-analysis + CLI integration — existing tools only provide empty templates
MVP Development
- MVP Timeline: 4 weeks
- Full Version: 4 months
- Tech Complexity: Low
- Stack: Node.js CLI, LLM API (Claude/GPT), Markdown templates
MVP Scope
- Natural language query → LLM-based multi-perspective analysis
- ADR markdown auto-generation
- Local decision repository (JSON/SQLite)
- npm package publish
Revenue Model
- Model: Freemium + Subscription
- Pricing:
- Free: 5 decision analyses/month
- Pro: $7/mo (unlimited analyses, team sharing, history search)
- Team: $19/mo (org decision repository, trend analytics, Notion/Confluence integration)
- Expected MRR (6 months): $1,000-3,000
- Expected MRR (12 months): $5,000-12,000
Risk
| Type | Level | Mitigation |
|---|---|---|
| Technical | Low | CLI + LLM API = perfect skill match |
| Market | Low | New category needs education → dev blogs/conferences for awareness |
| Execution | Low | 4-week MVP for rapid validation, manage LLM costs |
Recommendation
Score: 90/100 ⭐⭐⭐⭐⭐
Why Recommended
- Zero AI-native commercial ADR tools — category creation opportunity
- 4-week MVP enables rapid market validation
- Perfect dev_tools domain fit
- Technical decision recording is a universal pain point — every dev team needs it
- Low technical complexity leveraging LLM APIs
Risk Factors
- “ADR” as a category has low awareness — market education needed
- LLM API costs impact margins
- Analysis quality depends on LLM performance
First Actions
- Develop CLI MVP (LLM multi-perspective analysis + ADR markdown generation)
- Test with 10 common technology decision scenarios
- VS Code extension for improved developer accessibility
This idea transplants ManyLens’ multi-perspective analysis concept into the technical decision-making domain, structuring the technology choice dilemmas developers face daily.