Zencoder’s chasing non-coders now.
And it’s got that familiar whiff of overreach — you know, the kind that built empires and then sold ‘em off.
Look, Zencoder kicked off as your friendly IDE code completer. Solid gig. Developers loved it. But Thursday? They drop Zenflow for Work. First stab at non-coders. Suddenly, they’re an ‘orchestration layer for AI engineering.’ Agents for planning, coding, testing, reviews. Fancy.
CEO Andrew Filev — guy who cashed out Wrike for billions — spins it smooth. Tools to speed up devs’ grunt work: standups, release notes, meeting prep. Pulls from Jira, Linear, Notion, Gmail. Schedules ‘em too. Clean backlog daily? Weekly stakeholder reports? Sure, why not.
But here’s the pivot. They built the pipes for coders already. Performant. Scoped right. Now, stretch to ‘proactive work.’ Chase goals like herding PRs through reviews to prod. Integrations galore. Non-coding tools baked in. So, boom — open to sales, marketing, HR, finance. HubSpot next.
Filev’s Wrike ghost haunts this. Bug trackers ruled for engineers. Jira wizards. Then marketing balks: ‘Hell no.’ Needed simpler UX. Wrike born. Sold big. Now Zencoder apes it: tech smarts for the masses.
“This reminds me a lot of my Wrike journey. First there were bug trackers for engineers and tools like Jira, which were awesome. Engineers are typically very smart, and they build advanced workflows, and customizations, and it’s wonderful,” Filev says. “And then you’re looking at a marketing department, and you’re like: ‘well, marketing departments should also organize their work.’ And then you try to implement Jira, and they’re like: ‘oh my god, we’re never going to use it.’ So they need a much simpler product with better UX — and this is what kind of gave birth to Wrike.”
Charming origin story. But Wrike worked because it ditched Jira’s cruft entirely. Zenflow? Cloud-run agents for collab. Team shares with agents. Missing in most AI toys, Filev claims. Fine. Except non-devs crave Slack bots or email summaries, not agent swarms.
Is Zenflow Just Jira for Lazy Marketers?
Nah, not quite. But close enough to snort at.
Zencoder bets on integrations and schedules. Devs get speedups; suits get automation. Pull requests auto-piloted? Cool for eng. Backlog scrubs for sales? Meh. And collaboration — that’s the hook. Agents don’t silo; teams poke ‘em together. Cloud-only for now. Makes sense. Local IDEs won’t cut it for Gmail trawls.
Yet Filev’s history screams caution. Wrike scaled because it was fresh. This? AI agent hype du jour. Anthropic’s Coworker vibes — Claude Code gateway for normies. Everyone’s piling on. Zencoder’s edge? Proven coder platform. But expanding screams dilution.
My unique take: this echoes Atlassian’s Jira-to-Confluence flop. Jira owns eng. Confluence? Bloated wiki nobody loves. Zencoder risks the same — coder gold turns to marketer mush. Prediction: 18 months, then spinout or acquisition. Filev’s playbook.
Short para punch: Hype alert.
Bonus nugget they slipped in: dual-model magic. Flagship for specs (Opus shines). Cheapie for code (Gemini Flash crushes impl). Saves 70% tokens. Better output too — Opus plans deep, no need for its code pass.
“The results were that Gemini Flash did a better job at implementation than even Opus, because Opus already kind of put its best foot forward in the plan, so then running Opus for implementation didn’t add much,” Filev says.
Smart. Devs hack this manually. Zencoder wraps it neat. Token thrift amid API Armageddon. Underrated win. But tucked quiet — smart PR, hide the real juice behind non-coder fluff.
Why Should Developers Care About Non-Coder AI?
You shouldn’t. Much.
This splinters focus. Zencoder’s coder core? Gold. Agents that ship code? Yes. But wooing suits dilutes. Resources split. UX tuned for point-and-clickers means dev tools soften. Remember Replit’s pivot? Fun playground to enterprise slog. Momentum killer.
Filev insists platform’s ready. ‘Straightforward move.’ Sure. Integrations primed. But non-devs hate eng tools — even prettied. They’ll bolt to Zapier ghosts or no-code darlings. Notion AI scraps suffice.
And cloud agents? Latency laughs. Collab dreams hit reality: permission hell, data silos. HR won’t feed Gmail to randos.
Punchy doubt: Overpromised. Underwhelms.
Deeper worry — agent fatigue. Everyone promises ‘orchestration.’ Devin, Cursor, now this. Multi-step workflows? Brittle. Hallucinations cascade. PR shepherd? One bad comment parse, stalled.
Filev’s right on one: eng pioneered. Time to export. But packaging matters. Wrike nailed UX. Zenflow? Demo me skeptical.
History bites: Basecamp fled Jira complexity for simplicity. Won hearts. Zencoder risks reverse — eng power overwhelms suits.
Zencoder’s Real Play: Cost-Cutting Sneak
That dual-model bit? Buried lede.
70% cheaper. Better code. While non-coders distract, devs get efficiency hack. Tooling auto-switches models. No manual dance.
This — not Zenflow — sustains. Token wars rage. Claude, GPT, Gemini prices tumble, but scale hurts. Zencoder positions as smart layer.
Critique PR spin: ‘Beyond coding’ headlines woo VCs. Real value? Coder thrift. Non-coders? Growth metric fluff.
Wandering thought: Filev’s exits timed markets. Wrike rode remote work. This? AI bubble peak? Sell high?
Final jab: Ambitious. Reckless. Watch.
🧬 Related Insights
- Read more: I Just Fired Up a Pirate Radio Station from My Dynamic IP – Here’s the No-BS Linux Hack
- Read more: MCP: Finally, a Leash for Your Rogue AI Agents
Frequently Asked Questions
What is Zencoder Zenflow?
Zenflow for Work: AI agents for non-devs. Schedules tasks, pulls Jira/Notion data, preps reports. Cloud collab focus.
Does Zencoder Zenflow replace Jira?
Nope. Builds on it. Simpler for sales/marketing, per Filev. But UX gap looms large.
Is Zencoder’s dual-model trick worth it?
Yes. 70% cheaper, better code. Devs, ignore non-coder noise — grab this.
