Roadmap

What is live, what is next, and what is still planned.

Cowrite is being built in public enough to be honest about the boundary between current workflow capabilities and upcoming publishing, integration, and performance features.

Last updated: July 4, 2026

Live focusResearch to export
Next focusPublishing workflows
Later focusPerformance and integrations

Live now

Cowrite is focused on the editorial workflow that takes a technical topic from search opportunity to a reviewable, export-ready article.

  • Search-backed briefs that connect keyword opportunity, competitor coverage, and product context.
  • Article outlines shaped by content type and source material before draft generation begins.
  • Draft generation with source-aware review, citations, visuals, and technical article structure.
  • Human approval gates around outline and draft stages, with revision requests before forward movement.
  • File-based export and handoff for approved articles, including Markdown, HTML, PDF, DOCX, ODT, and ZIP where supported.
  • Brand Voice Profile work that helps drafts reflect existing writing style instead of generic model tone.

Near-term roadmap

The next stage is making publishing safer and more repeatable without pretending that every destination is already live.

  • Publishing destination setup and preflight checks for draft or handoff workflows.
  • GitHub repository publishing paths for teams that publish technical content through pull requests.
  • WordPress and Ghost draft publishing once destination tests and failure handling are reliable.
  • Generic webhook handoff for custom CMSs, agencies, and internal publishing systems.
  • Clearer article status, destination status, and retry behavior when an external publish fails.

Planned after publishing

After the publishing foundation is dependable, Cowrite can connect article outcomes back into planning and improvement loops.

  • Performance tracking for published articles, starting from the canonical live URL when available.
  • Refresh recommendations based on search movement, article age, and product changes.
  • Deeper workspace controls for teams, including review ownership, audit history, and role-aware approvals.
  • More integration surfaces for source ingestion, publishing destinations, and editorial operations.
  • Scalability and latency improvements for larger source libraries, richer visuals, and longer editorial queues.

Not promised yet

Roadmap items are directional and may change as customer needs, provider constraints, and product quality findings evolve. Direct CMS integrations, automated live publishing, analytics-driven republishing, and scheduled publishing should be treated as planned unless the product explicitly marks them live.