Convoworks, 2025 – Status and Next Steps

From idea to pivot

Convoworks started in 2021 as a voice-workflow framework for smart speakers. EU grants and an investment from FRC helped us launch the first version, but the smart-speaker boom never took off as forecasts predicted; in fact, that market has since almost disappeared. At the time I had little entrepreneurial experience and quickly learned that building a great framework is not the same as turning it into a successful product.

By early 2023 the original team had moved on, and I had to decide whether to close the project or reshape it. The release of ChatGPT made the choice clear: the same component workflow engine that once powered voice skills is a natural fit for AI-driven chat and automation inside WordPress, so I chose to keep building.

Since then I have been working part-time on freelance projects—mostly building admin tools and back-end systems for a German startup—while dedicating the rest of my time to Convoworks. I have a couple of early test users, and the goal now is to keep exploring ideas and emerge with a truly delightful AI experience.

Where we are today

This phase began with a mail-server glitch that caused WordPress.org to suspend the plugin until outgoing email was restored. Once fixed, the directory triggered a full review—now far stricter than the one we passed in 2021. I am using that process as an opportunity to remove outdated Alexa/NLP code, rebuild core parts of the plugin, and align workflows with today’s standards.
The cleanup is a rolling effort, and I will keep shipping private builds while version 1 takes shape. Realistically, it will not be complete this year—especially with a new website coming—but progress is steady.

Where we’re heading

Better modularity. Even before the WordPress Feature API and the Model Context Protocol (MCP) began formalising expectations, it was clear that Convoworks needed stronger plugin-style modularity. The aim is to support truly self-contained, updatable, composable components so workflows can be assembled from reusable blocks rather than one-off structures.

Agent infrastructure. Until now, Convoworks services have centred on the chat API model. The next step is to add agent-specific components and an execution layer that supports background processing, persistent memory, and, eventually, inter-agent communication. This will lay the groundwork for more dynamic, cooperative automation flows.

AI-first builder. A natural-language interface is in development: describe a goal and Convoworks assembles the workflow for you, making service design more conversational than technical. The build dialogue itself will double as the specification, prototype, and documentation.

MCP client. An MCP client would let Convoworks consume remote toolsets and make outside capabilities feel native to WordPress workflows. It is a technically hard problem, but it remains on the wishlist for the doors it could open to distributed, multi-platform automation.

Stay connected

• Personal updates on X
• Video walkthroughs on YouTube
• Convoworks news on X
• WP AI Collective community

The Convoworks WP plugin remains available for download on convoworks.com and will continue receiving updates as version 1 evolves.