Harvey

The Death of the Code Bottleneck For the last century, the primary rate-limiter for any technology company was the physical and cognitive speed of writing code. Developers were the high-priced scribes of the digital age, and their output dictated the velocity of entire markets. Jacob Lauritzen, CTO of Legora, argues that this reality has fundamentally shattered. In the current environment, code has become cheap, abundant, and largely automated. When 50% of an enterprise company's codebase is generated by Claude and Cursor, the bottleneck necessarily shifts to the surrounding phases: product definition and code review. The compression of the development cycle means that the value is no longer in the "how" of implementation, but the "what" and "why" of the product vision. If you can generate a V1 in a weekend, the competitive advantage vanishes for those who rely on technical execution alone. The real challenge now lies in translating messy, ambiguous user pain points into a cohesive strategy. This synthesis is the new high-ground of engineering management. The ability to identify the right problem to solve is now exponentially more valuable than the ability to write the script that solves it. Systems Design as the New Frontier As AI agents take over the nitty-gritty of line-by-line coding, the role of the software engineer is ascending to a higher level of abstraction. We are moving toward a world where engineers act as systems architects rather than keyboard operators. In this vision, the engineer’s primary task is to design the boundaries, security protocols, and structural integrity of a system, while allowing AI agents to "run amok" within those guardrails to optimize specific functions. This shift demands a new kind of "meta-engineering." Jacob Lauritzen highlights the necessity of developer experience teams—not just for humans, but for agents. These teams are responsible for creating the environments where AI can be effective, ensuring that agents have access to the right data and are constrained by the right rules. The engineer of the future is someone who builds the machine that builds the software. If you are still hiring people based solely on their ability to write Python or Java, you are preparing for a war that has already ended. The Governance Gap in AI Code Review While code generation has reached a point of high efficiency, the mechanisms for reviewing that code remain dangerously immature. The industry is currently in a "nascent phase" where AI review bots and human reviewers are struggling to keep up with the sheer volume of machine-generated PRs. This creates a massive security surface area. Threat actors are utilizing the same efficiency gains to find vulnerabilities, while defense teams are often stuck in manual, line-by-line review processes that cannot scale. Legora still insists on human review for every PR to ensure security boundaries aren't breached. However, this is a temporary fix. The industry desperately needs a new category of startup focused on architectural review—tools that look at system-wide impact, design stability, and security boundaries rather than just syntax. The current paradigm of agents "fighting each other" until they arrive at a stable code block is inefficient. The winners of the next five years will be the companies that figure out how to mechanistically enforce system behavior without human eyes on every line. Vibe Coding and the Internal Tool Revolution One of the most disruptive trends emerging from the AI era is the rise of "vibe coding"—the ability for non-engineers, or engineers working outside their primary scope, to rapidly prototype and deploy functional tools. Jacob Lauritzen describes a culture where Product Managers build high-fidelity prototypes and internal teams "vibe code" custom HR or payroll systems rather than buying expensive, rigid off-the-shelf software. This is not just a gimmick; it’s a fundamental shift in the cost-benefit analysis of the "build vs. buy" debate. When the cost of building a tailored internal application drops to near-zero, the enterprise software market faces a crisis. Why pay for a generic ATS or migration tool when an employee can build a perfectly customized version in a single day? This democratization of development allows companies to be hyper-agile, solving niche internal problems that would have previously been ignored due to resource constraints. Why Token Maxing is a Dead-End Strategy There is a growing, misguided trend in the corporate world toward "token maxing"—the idea that high AI usage is a direct proxy for innovation or productivity. Some companies even track token spend on leaderboards during performance reviews. This is a fundamental misunderstanding of the technology. Burning tokens for the sake of looking busy is the new "sending emails at 2 AM." True efficiency comes from intelligent routing and knowing when *not* to use a high-powered model. Jacob Lauritzen advocates for a focus on output and opportunity cost. The goal isn't to use the most AI; it's to gain the most ground in a competitive market. For a high-growth startup like Legora, the budget for AI tooling should be nearly infinite because the cost of being slow is far higher than the cost of tokens. However, that spend must be directed toward learning and velocity, not just inflating usage metrics to satisfy a boardroom mandate. The Survival of Taste in an Automated World The most frequent pushback against AI automation is the fear of "grayness"—the idea that AI-generated products will eventually converge into a bland, mediocre average. This is where "taste" becomes the ultimate differentiator. Taste is an opinionated stance on how a product should feel, look, and behave. It is what prevents a company from producing "AI slop." In a world where anyone can copy a feature in minutes, the only thing that cannot be easily replicated is the unique design language and hierarchy of a brand. Figma remains essential in this process as a repository for that taste. Even as we automate the functionality, the opinionated edge of a product—who it is for and, more importantly, who it is *not* for—is the only moat that remains. If you let AI rip without a human filter of taste, you will end up looking exactly like your competitors. Conclusion The transformation of the tech industry is moving faster than most founders are willing to admit. We have moved from an era of scarce engineering talent to an era of scarce product clarity. As we look toward 2027, the successful enterprise will be one that scales not just its headcount, but its ability to manage agents, protect its architectural integrity, and maintain a sharp, human sense of taste amidst a sea of automated output. The goal is to build something huge, keep the ego low, and work harder than the 800lb gorilla that has grown too slow to notice the world has changed.