GitLab’s Playbook for the AI Era: How to Leverage Jevons Paradox in Software Development

Introduction

GitLab, a leader in developer tooling, has long championed a unified platform for the full software development lifecycle. Now, the company is undergoing a major transformation to prepare for what CEO Bill Staples calls the "agentic era" — where AI agents handle most coding, and developers shift to supervising, reviewing, and coordinating machine-generated code. This shift is grounded in a 19th-century economic theory: Jevons paradox, which posits that making a resource cheaper actually increases its total consumption, not decreases it. GitLab is betting that as AI makes software production cheaper and faster, demand for software will skyrocket. This step-by-step guide breaks down GitLab’s strategy, helping you understand how they plan to navigate the AI era.

What You Need

Before diving into the steps, ensure you have a basic understanding of these concepts:

• Jevons paradox: The economic principle that increased efficiency in using a resource leads to higher overall consumption of that resource.
• AI agents: Autonomous software entities that can plan, code, review, deploy, and repair code with minimal human intervention.
• GitLab’s platform: Familiarity with its core offerings like source control, CI/CD, security scanning, and collaboration tools.
• Orchestration: The coordination of multiple AI agents and human developers across the software lifecycle.

Step-by-Step Guide: Understanding GitLab’s AI-Era Strategy

Step 1: Recognize the Paradigm Shift from Writing Code to Supervising Agents

GitLab’s restructuring starts with a fundamental acknowledgment: the role of developers is changing. Instead of writing every line of code, developers will focus on higher-level system design, architecture, governance, and coordinating fleets of AI agents. As Staples writes, "Software will be built by machines, directed by people." To align with this, GitLab is reorganizing its product and team structure to prioritize tools for agent supervision and orchestration, rather than just code creation.

Step 2: Embrace Jevons Paradox as the Core Economic Driver

The company’s entire strategy hinges on the belief that falling production costs will expand the software market. Staples argues: "As the cost of producing software collapses, demand for it will expand." This mirrors Jevons paradox, where more efficient steam engines led to more coal consumption, not less. GitLab’s leadership is betting that AI will make software so cheap to produce that businesses will demand far more of it — increasing the total volume of code that needs to be managed, reviewed, and deployed. This belief justifies investments in scaling up orchestration capabilities.

Step 3: Architect for “Machine-Scale” Software Development

To capitalize on the Jevons paradox, GitLab is undertaking a “machine-scale” rebuild of its platform. This means engineering the system to handle thousands of AI agents operating in parallel, generating code, running tests, and deploying updates simultaneously. The reorganization includes product consolidation and executive changes to streamline decision-making around agentic workflows. GitLab is also investing heavily in AI-native features like automated code review, intelligent CI/CD triggers, and self-healing deployments, ensuring the platform scales with the explosion of AI-generated code.

Step 4: Reposition Developers as Coordinators and Architects

Rather than diminishing the role of engineers, GitLab’s strategy elevates it. Developers will move from writing mundane code to architecting systems, reasoning through failures, and coordinating multiple AI agents. This requires new tooling for visibility into agent actions, policy enforcement, and approval workflows. GitLab is building features that allow developers to define guardrails, review agent-generated code, and oversee the entire lifecycle — effectively turning the developer into a “fleet manager” for AI.

Step 5: Implement Organizational Restructuring to Support the Shift

Transforming a company’s culture and technology isn’t just about product changes. GitLab announced layoffs and executive changes to align the organization with the agentic era. This includes reducing headcount in roles that may be automated, while hiring for AI orchestration, ML engineering, and developer experience. The company is also consolidating product lines to focus on a unified AI-driven platform. These tough decisions reflect a belief that the current market valuation drop (from ~$11B to ~$3.7B) requires bold action to regain investor confidence.

Step 6: Communicate the Vision Through Transparent Leadership

Staples published an open letter explaining the changes, directly addressing market doubts. The letter serves as a strategic anchor, outlining why GitLab is betting on Jevons paradox and how the reorganization will prepare for an AI-native future. This transparency helps align employees, customers, and investors around a single narrative: AI won’t shrink the software industry; it will expand it. GitLab is positioning itself as the orchestration layer for that expanded market.

Tips for Success

• Stay Agile: The transition to an agentic era won’t happen overnight. Continuously revisit your strategy as AI capabilities evolve.
• Invest in Orchestration: The biggest bottleneck in AI-driven development is coordination. Build or adopt tools that manage agent workflows, approvals, and quality gates.
• Focus on Developer Experience: Even as agents take over coding, developers need intuitive interfaces to review and guide them. A poor experience can negate productivity gains.
• Monitor Economic Indicators: Track metrics like cost per feature, deployment frequency, and team velocity to validate whether Jevons paradox is indeed boosting demand in your context.
• Communicate Openly: Like GitLab’s open letter, share your strategic rationale with stakeholders. Uncertainty breeds doubt; clarity builds confidence.

GitLab’s bet on Jevons paradox is a calculated risk. By following these steps, you can gain a deeper understanding of how one company is restructuring for an AI-dominated future — and perhaps apply similar principles to your own organization.