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

Live now

Cowrite covers the editorial workflow that takes a technical topic from search opportunity to a reviewed article, out to the places you publish, and back to how it performs.

• 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.
• Brand Voice Profile work that helps drafts reflect existing writing style instead of generic model tone.
• File-based export and handoff for approved articles, including Markdown, HTML, PDF, DOCX, ODT, and ZIP where supported.
• Publishing destination setup with connection tests, so a destination can be checked before an article is sent to it.
• Direct publishing for approved articles to WordPress, Ghost, Hashnode, dev.to, X articles, a GitHub repository, or your own webhook.
• Scheduled publishing, so an approved article can go out on a date and time you set instead of the moment it is approved.
• Google Search Console performance tracking for the accounts you connect.

Near-term roadmap

Publishing and performance data are already in the product, so the next stage is making failures legible and turning what the data shows into concrete editorial decisions.

• Clearer article status, destination status, and retry behavior when an external publish fails.
• Refresh recommendations based on search movement, article age, and product changes.

Planned later

Further out, the work is less about the editorial loop itself and more about the teams and volumes running through it.

• 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. Automated republishing and analytics-driven refresh loops are planned rather than live. If a capability is not listed above as live now, treat it as planned.