P2P

22 WORKFORCE IMPLICATIONS WHEN EVERYONE CAN BUILD The ability to build software is shifting from a specialized technical skill to a general professional capability. Legal operations roles increasingly list "experience with Python, SQL, or similar" as preferred qualifications. Business development analysts who can build their own dashboards command higher salaries. Knowledge management professionals who can code their own tools are getting promoted into director roles. The shift creates new career trajectories. Legal operations professionals are moving into roles that look more like product management -- defining problems, prototyping solutions, iterating rapidly. Several AmLaw 100 firms have created new roles called "technical translators," "innovation engineers," or "legal technologists" – hybrid positions that sit between IT and business functions. But the transition creates genuine displacement concerns. Roles centered on vendor relationship management, commercial software configuration, and translating requirements into technical specifications face an uncertain future. When legal ops teams can build directly, business analyst roles that historically bridged business and IT become less critical. For law students and young lawyers, the message is clear: technical fluency is becoming table stakes. Law schools are adding legal technology courses and coding bootcamps, recognizing that tomorrow's lawyers will need to be comfortable directing AI assistants to build tools. The lawyer who can identify a workflow problem, prototype a solution, and iterate based on feedback is developing a skillset that will differentiate them throughout their career. The transition is uneven across firms. Some are aggressively embracing the shift, reorganizing departments and creating new career paths around technical capability. Others view vibe coding as a niche skill. But the competitive dynamics are evident where firms that successfully integrate these capabilities will attract professionals who want to build, not just coordinate. THE STRATEGIC IMPLICATIONS OF BUILD, BUY, OR HYBRID? The rise of vibe coding is forcing law firms to reconsider the build versus buy decision. For decades, the answer has been overwhelmingly "buy" -- law firms are not software companies, the reasoning went, and should focus on legal services delivery, while leaving software development to specialized vendors. The debate intensified in early 2026. In a March 2026 Artificial Lawyer analysis titled "Vibe Coding Lawyers and the New Economics of Legal Tech," commentators argued that vibe coding lawyers represent "a real threat to legal tech SaaS," noting that "it's worth asking an uncomfortable question: who says today's legal tech founders are more qualified to build legal software than senior lawyers inside top firms?" A January 2026 article in The Red Line by Version Story noted that "vibe- coding lawyers were undeniably the main topic of conversation" at industry events, with debate about whether it is "fundamentally limited -- insecure and unreliable" or "a genuine shift in how legal software gets built." AI-powered development tools fundamentally change this calculus. When building custom software no longer requires dedicated development teams or long timelines, firms can now build for specific, high-value use cases while continuing to buy for broad capabilities. Firms embracing internal build capability are reorganizing around new roles and team structures, adding "platform teams" focused on enabling business users to build safely. Some firms are creating entirely new departments ("Legal Solutions" or "Innovation Labs") that combine technical capability with legal domain expertise. ain expertise. A PATH FORWARD FOR THOUGHTFUL ENABLEMENT, NOT PROHIBITION The firms navigating this transition most successfully are neither embracing vibe coding uncritically nor attempting to prohibit it. Instead, they are developing frameworks that enable productive citizen development while managing risks. By 2026, this has become urgent.

• Cover