Dominic Jainy stands at the forefront of the modern technological landscape, possessing a deep understanding of how artificial intelligence, machine learning, and blockchain are fundamentally rewriting the rules of business. With years of experience navigating the complexities of enterprise IT, he has become a go-to expert for understanding how high-growth companies must evolve to survive the “agentic” era of software. As traditional workflows give way to autonomous systems, Dominic provides a critical perspective on the structural and strategic shifts necessary to turn technological potential into operational reality. His insights are particularly timely following the recent announcement that monday.com is undergoing a radical transformation to prioritize AI integration over traditional management layers.
This discussion explores the strategic logic behind a high-growth company cutting one-fifth of its workforce not out of financial distress, but as a “deliberate reset” to foster a flatter, more autonomous organizational structure. We delve into the concept of a “governed runtime” where AI agents and humans collaborate within a structured workspace, the competitive pressures from tech giants like Microsoft and ServiceNow, and the shift from predictable seat-based licensing to more complex, behavior-driven consumption models. The conversation also addresses the tangible risks to enterprise buyers during such transitions, emphasizing the need for roadmap consistency and sophisticated contract management as the industry moves from managing work to actually performing it via AI.
Software companies experiencing 19% to 20% year-over-year growth are usually hiring aggressively, yet we are seeing a major player like monday.com cut 20% of its workforce. How should we interpret this move in the broader context of the AI era?
It is a fascinating and somewhat counterintuitive move that signals a profound shift in how we define “productivity.” When a healthy company like monday.com decides to reduce its global workforce by about 620 people, it is not a distress signal; rather, it is a calculated decision to shed the weight of a previous era. They are betting on the idea that the organization built for the pre-AI chapter simply does not fit the speed and structure required for the next phase. By creating a flatter organization with fewer management layers and smaller, more autonomous teams, they are trying to become more decisive and responsive to a market that changes overnight. This isn’t about padding margins or replacing humans with bots, but about reinvesting the vast majority of those savings back into talent and products that specifically fuel an AI-driven strategy.
The concept of “doing the work with AI” rather than just “managing it” was a central theme in the recent announcement. What does this transition look like for the average employee or manager in a high-growth tech firm?
The shift from management to execution is perhaps the most visceral change for the workforce right now. In the old model, you had layers of people whose primary role was to facilitate communication, move tickets, and report on progress, but we are moving toward an environment where people and AI agents work together in a single, unified workspace. This means the day-to-day workflow becomes much more about “implementation depth” rather than just tracking status updates. We are seeing roles adapt or be created entirely from scratch to focus on how AI agents can handle the “heavy lifting” of the work itself. While this promises a leaner, more focused operating model, it also creates significant internal pressure, as the “hidden bruises” of losing 20% of one’s colleagues can surface long after the initial restructuring is complete.
There was a mention of “structured substrate” being a key advantage for certain platforms. Why is having a firm foundation of boards and workflows more important for AI agents than just having a massive history of chats or documents?
In the world of AI agents, context is everything, but unstructured context—like a long chain of emails or a folder full of PDFs—is often messy and prone to error. A “structured substrate” refers to the boards, permissions, and typed workflows that provide a governed runtime where an agent can safely and predictably act. For an AI to be truly effective, it needs a firm ground to stand on, and structured work provides a serious claim on that runtime by giving agents specific parameters to follow. This allows for natively built agents to be configured by any team member, rather than requiring a team of data scientists for every small task. It is essentially the difference between asking an agent to find a needle in a haystack versus asking it to pull a specific lever in a well-oiled machine.
Competition in the enterprise space is fierce, with giants like Microsoft and ServiceNow bundling AI into their existing stacks. How can smaller, specialized platforms maintain their “pull” against these massive, all-in-one ecosystems?
The competitive “gravity” of incumbents like Microsoft, which is embedding AI across its entire productivity stack, or ServiceNow, which covers enterprise operations, is a massive challenge for anyone trying to grow in the large-account space. These giants have the advantage of integrated identity management and procurement already built in, which often decides the deal at the enterprise level. To compete, specialized platforms have to prove they offer a “control-plane depth” that the generic bundles lack, such as more flexible agent builders or more intuitive no-code environments. For instance, seeing a tool like “monday vibe” pass $1 million in annual recurring revenue within just two and a half months shows there is a hunger for specialized, agile AI tools. However, the pressure remains high to move beyond “beta” labels and prove that these new agent estates can deliver consistent, long-term outcomes for the biggest clients.
We are seeing a shift in pricing models, moving toward hybrid structures that include both traditional “seats” and mandatory AI credits. What are the long-term implications of this for a company’s bottom line and its relationship with customers?
The shift from a fixed license cost to a “metered” model is a fundamental change in the economics of software. A license was a known, predictable cost that finance departments could easily budget for, but a meter is a behavior, and human behavior is notoriously harder to forecast than headcount. This hybrid model forces customers to think about the value of every AI interaction, which could lead to “bill shock” if not managed correctly with strict credit governance and admin controls. While it allows software companies to capture more value from high-usage power users, it also places a burden on the vendor to provide monthly consumption reporting by capability. If the implementation doesn’t lead to a measurable increase in outcomes per unit of effort, customers might start looking for those “side exits” in their contracts.
For enterprise buyers looking at companies going through these massive AI-driven restructures, what should be their primary focus during the first six months of the transition?
Buyers need to look past the headline risk of layoffs and focus intensely on operating risk, which translates to continuity of service and roadmap consistency. During the first month, I would advise tracking named account continuity and checking if escalation times for support are slipping, especially since many companies are moving mid-sized clients to an “AI-first” support model. By the first quarter, you want to see if the promised admin controls and credit governance features are actually maturing on schedule. Finally, by the half-year mark, you have to determine if the “deeper implementation support” you were promised is actually producing better outcomes or if it’s just resulting in more billable engagement. It is crucial to contract for portability of workflows and agent configurations in advance, so you aren’t trapped if the relationship sours during the transition.
What is your forecast for the future of the autonomous team model?
I believe we are entering a period where the “headcount-to-revenue” ratio will be completely redefined, as autonomous teams of three or four people perform the work that previously required a department of twenty. Over the next two years, we will see the “governed runtime” become the most valuable real estate in the enterprise, as companies stop buying software for its features and start buying it based on how effectively it can host and manage a fleet of specialized AI agents. The companies that survive this shift will be the ones that can prove their AI isn’t just an “add-on” or a chatbot, but a core component of a flatter, faster, and more effective operating model. However, the transition will be painful, and we will likely see more “deliberate resets” as the industry realizes that you cannot build a twenty-first-century AI powerhouse on the foundations of a twentieth-century management hierarchy.