Introducing Zenflow Work: AI Orchestration for the Other 75 Percent

When we launched Zenflow in December, the premise was simple. As AI agents get more capable, we should run them the way companies run people: with multiple specialists, structured workflows, and clear handoffs, not one cowboy agent winging it. Four months later, two things have become clear.

First, multi-model orchestration isn't just "nice in theory." We now have the data to prove it works, and it works well enough to build product around. More on that below.

Second, developers are already using coding agents for non-coding work. Anthropic published data showing roughly half of Claude Code usage happens outside of coding. We see the same pattern in Zencoder usage, and I hear it from users of Cursor and Codex too. The tools are powerful enough that people reach for them even when the task isn't strictly "write me this function." The problem is that the interfaces were designed for engineers who are comfortable with Git, PRs, work trees, and command-line configuration. Most of the rest of the world (including many engineers doing non-coding work) doesn't want to touch any of that.

I've seen this movie before. When I started Wrike more than a decade ago, engineers had Jira and loved it. Marketing teams tried to use Jira and hated it. Not because Jira was a bad tool, but because the power was wrapped in complexity that didn't match how non-engineers wanted to work. That gap is what created Wrike, Asana, Monday, Notion, and the whole modern work management category. The same gap exists today with AI agents, and closing it is exactly what Zenflow Work is built for.

What's new in Zenflow Work

Three changes worth understanding, all layered on the Zenflow platform that engineering teams already run in production.

1. A simpler interface for non-engineering work. The full Zenflow coding experience is intact. On top of it, we added a streamlined mode that doesn't expose Git, work trees, PRs, branches, or commits. It's just a prompt, the integrations, and your agent. Business users can ask for what they need in plain language, and when a workflow needs configuration, our AI assistant turns the natural-language description into the right config behind the scenes. It's given us several "wow" moments, and we hope you'll feel the same.

2. Scheduled automations. Instead of prompting the agent every time, you can put work on autopilot. A Zenflow agent can assemble your standup brief from Jira every morning before you sit down. It can compile release notes from merged PRs every Friday. It can draft a weekly stakeholder update from real project data and save it to your Gmail drafts for review. These are things every team "should" do and most teams skip because they take time. Now they happen without anyone having to remember. We love putting busy-work on auto-pilot, so we can focus on things that really require our attention.

3. Goal-oriented agents that chase outcomes across sessions. Today, when an engineer opens a PR, they typically come back, check for review comments, and either address them by hand or re-invoke the agent. Zenflow Work lets you hand the agent a goal instead of a prompt: "Open the PR, watch for review comments, and address them until it's ready to merge." The agent stays on the goal across hours or days, waking up when there's work to do and standing down when the goal is met. The same pattern applies to sales follow-ups, invoice collection, incident response, and plenty of other workflows that used to require a human in the loop for every single step.

On top of these three, we've added a curated set of business integrations. Jira, Linear, Notion, Amplitude, Miro, and Sentry are production-ready today with user-friendly authentication. This is where most of our early usage is concentrated.
We also support native file handling for PPTX, PDF, XLSX, and DOCX, covering a wide range of common business workflows.

Integrations with Gmail, Google Calendar, and Drive, as well as HubSpot, are currently in early access. Setup can still be a bit involved, but we're actively improving the experience and expanding the list of supported tools.

To round it out, there's a built-in browser tab that lets the agent read websites, inspect elements, and capture screenshots as part of its workflow.

We're building toward a messaging-first experience. You can already talk to your agent from Telegram, with Slack and Discord support in early access.

Today, that means interacting with the Zenflow agent to start new tasks remotely, ask data questions, or trigger workflows in integrated apps. Richer interaction patterns, like channel mentions, acting on running workflows, and threaded conversations, are on the near-term roadmap, alongside support for more messengers.