Last week, one of our Product Managers (PMs) created and released a feature. Not specified. He did not present a fine for it. He built it, tested it, and sent it to production. In one day.
A few days earlier, our designer noticed that the visual appearance of our IDE plugins had deviated from the design system. In the old world, that meant screenshots, a JIRA ticket, a conversation to explain the intent, and a sprint slot. Instead, he opened an agent, tweaked the design himself, experimented, iterated and tweaked in real time, and then pushed the solution. The person with the strongest design intuition set the design directly. No translation layer required.
None of this is new in theory. Vibe coding opened the doors of software creation to millions of people. That was the aspiration. when i shared the data about how our engineers doubled performance, moved from coding to validation, advanced design for rapid experimentation, it was still an engineering story. What changed is that theory became practice. That’s how it really played out.
The bottleneck moved
When we adopted AI first in 2025, the cost of implementation plummeted. Agents took care of the scaffolding, testing, and repetitive gluing code that used to eat up half the sprint. Cycle times decreased from weeks to days, from days to hours. Engineers began to think less about files and functions and more about architecture, constraints, and execution plans.
But once engineering capacity was no longer the bottleneck, we noticed something: decision speed was. All the coordination mechanisms we had created to protect engineering time (specs, tickets, handoffs, backlog preparation) were now the slowest part of the system. We were optimizing for a constraint that no longer existed.
What happens when building is cheaper than coordinating?
We started asking a different question: What would it be like if the people closest to the intent could ship the software directly?
PMs already think about specifications. Designers already define the structure, layout and behavior. They don’t think about syntax. They think about the results. When the cost of turning intent into working software dropped enough, these roles didn’t need "learn to code." The cost of implementation simply fell to their level.
I asked one of our PMs, Dmitry, to describe what changed from his perspective. Told me: "While agents generate tasks in Zenflow, there are a few minutes of downtime. Just dead air. I wanted to create a small game, something to interact with while you wait."
If you’ve ever managed a product team, you’ll know these types of ideas. It doesn’t move a KPI. It is impossible to justify it in a prioritization meeting. It is postponed forever. But it adds personality. It makes the product look like someone cared about the small details. These are exactly the things that are optimized in every backlog preparation session and exactly the things that users remember.
He built it in one day.
In the past, that idea would have disappeared into a prioritization spreadsheet. Not because it was bad, but because the cost of its implementation made it irrational to implement. When that cost drops to almost zero, the calculus changes completely.
Shipping became cheaper than explain.
As more people started building directly, entire layers of process quietly disappeared. Fewer entries. Fewer transfers. Less "Can you explain what you mean by…?" conversations. Fewer moments lost in translation.
For a significant class of tasks, it became faster to simply build the object than to describe what you wanted and wait for someone else to build it. Think about that for a second. Every modern software organization is structured around the assumption that implementation is the expensive part. When that assumption is broken, the organization has to change with it.
Our designer who fixed the plugin UI is a perfect example. The old workflow (screenshot the issue, file a ticket, explain the gap between intent and implementation, wait for a sprint slot, review the result, request adjustments) existed entirely to protect engineering bandwidth. When the person with the design intuition can act directly, that whole pile disappears. Not because we eliminated the process itself, but because the process was solving a problem that no longer existed.
The compound effect
This is what surprised me the most: it is composed.
When PMs build their own ideas, their specifications become more precise, because they now understand what the agent needs to execute well. Sharper specifications produce better agent results. A better result means fewer iteration cycles. We’re seeing speed increase week after week, not just because the models got better, but because the people using them got closer to work.
Dmitry put it well: the feedback loop between intention and result went from weeks to minutes. When you can see the result of your specification immediately, it learns what precision the system needs and starts providing it instinctively.
There is a second-order effect that is more difficult to measure but impossible to ignore: ownership. People stop waiting. They stop filing tickets for things they could just fix. "Builder" It stopped being a job title. It became the default behavior.
What this means for the industry
many of the "everyone can code" Last year’s narrative was theoretical or focused on individual founders and small teams. What we live is different. We have ~50 engineers working on a complex industrial code base: multiple programming surfaces and languages, enterprise integrations, all the weight of a real production system.
I don’t think we are unique. I think we were early. And with each new generation of models, the gap between who can build and who can’t is closing faster than most organizations realize. Every software company is about to discover that their PMs and designers are sitting in an unrealized development capacity, locked not by skill, but by the cost of implementation. As that cost continues to fall, the organizational implications are profound.
We started with the intention of accelerating software engineering. We are becoming something different: a company that everyone ships to.
Andrew Filev is founder and CEO of Zencoder.
