Market Positioning
Summary
ToneForge’s strategy is developer-first, stay narrow. The broad AI writing style market is dominated by well-capitalized incumbents: Writer.com (29-39/user/mo), Jasper (49-69/mo), and Grammarly (30M+ daily users, $12/mo). Claude Custom Styles and ChatGPT Custom Instructions provide free alternatives within their respective platforms. A two-person team with no marketing budget cannot compete in that market.
The developer CLI niche is uncontested. No tool currently analyzes writing style and injects it into AI developer toolchains. Adjacent surfaces are equally open: the .toneprofile format has no real competition (identity.txt has 0 GitHub stars and is effectively dead), and no MCP server for style queries exists anywhere. The addressable market is 2-5M developers using AI coding tools, with a realistic year-1 install target of 5,000-20,000.
The go-to-market follows three phases: CLI on PyPI to establish the format and user base; MCP server on registries (~200-400 LOC, same audience, new surface); then Phase 3 as an honest data-driven decision point — deepen into CI/git-hook integration or expand based on actual usage signals. Phase 3 is not a predetermined expansion plan.
Timeline
- 2026-04-13: Developer-first strategy formalized in v2 research plan. Web portal evaluated and rejected (puts ToneForge in direct competition with funded players). Phase 3 framed as decision point, not roadmap commitment.
Current State
Developer CLI niche has zero competitors as of April 2026. Distribution plan covers PyPI, npm (optional), Homebrew, GitHub, Show HN, Product Hunt, DevHunt, and MCP registries. Phase 1 (CLI) is the active build target. Phase 2 (MCP server) is designed but not started.
Key Decisions
- 2026-04-13: Stay narrow, developer-first — entering the broad market means competing with $200M+ funded players on their terms. The CLI niche is uncontested.
- 2026-04-13: Web portal rejected — a consumer web surface repositions ToneForge against Writer.com and Jasper, eliminating the competitive moat.
- 2026-04-13: Phase 3 framed as open question, not expansion — avoids premature roadmap commitments before real usage data exists.
Open Questions
- What specific usage signals in Phase 2 data would trigger deepening vs. expanding in Phase 3?
- Which MCP registries have the most developer traffic in Q2 2026?
- Whether npm distribution adds meaningful reach or just maintenance overhead.