English

Based on "No Legal Background. Then He Built a $5.5B AI Company | Legora, Max Junestrand" from EO Watch the original video

The Gamer’s Gambit: How a Non-Lawyer Built a $5.5 Billion Legal AI Empire

In the world of high-stakes corporate law, the "grind" is usually measured in billable hours, leather-bound case files, and late nights in mahogany-rowed offices. But for Max Junestrand, the co-founder and CEO of Leya, the grind started in a much different environment: the high-intensity, pixelated battlegrounds of Dota 2.

Junestrand doesn’t have a law degree. He didn't spend his twenties clerking for judges or mastering the nuances of tort reform. Yet, in just two years, he has scaled Leya from three engineers in a Stockholm office to a $5.5 billion AI powerhouse with over 750 clients and 300 employees. His journey is a masterclass in how "outsider" perspectives—combined with a gamer’s obsession with optimization—can disrupt one of the world’s most traditional industries.

From the Swedish Archipelago to the Digital Arena

Growing up in the quiet Swedish archipelago, Junestrand felt a void where competition should be. He sought that missing intensity in two places: sports and video games. It was in Dota 2, a complex multiplayer battle arena game, where he learned the foundational lessons of his leadership style.

"Gaming taught me that if you want to be great, you have to grind," Junestrand explains. "It’s not enough to just play more hours. You’ve got to play smarter and learn more. You have to bring a level of intensity better than anyone else."

In Dota, success depends on five players collaborating with seamless synchronization. As a CEO, Junestrand views his role similarly—not as the smartest person in the room, but as the conductor who makes the "band play together." This philosophy of the "infinite game" has allowed Leya to move at a pace that has left traditional legal tech incumbents reeling.

The "Jaw-Drop" Moment: Solving the Right Problems

When Junestrand looked at the legal industry, he didn't see a barrier to entry; he saw a goldmine of "meaningful problems." The vision for Leya was simple yet audacious: create the "10x lawyer" by using AI to automate the soul-crushing administrative tasks that keep attorneys from actual legal thinking.

The company’s early momentum was sparked during an incubation period at Mannheimer Swartling, Sweden’s premier law firm. Instead of building in a vacuum, Junestrand and his team sat in a borrowed conference room, working side-by-side with their future users.

He recalls the pivotal moment that proved they were onto something huge: "I would ask users to take an old memo or part of a case they had worked on, upload it, and ask Leya to do a first draft. When they saw the results, it was a 'leaning back, drop the chin' moment."

That visceral reaction—the realization that hours of work could be condensed into seconds—provided the fuel to scale.

The San Francisco Leap and the "Ring Light" Era

As Leya began to dominate the European market, Junestrand faced a crossroads: stay in the comfortable European ecosystem or move to the "big leagues" in the United States. Despite having a thriving business in Europe, he chose the latter, joining the prestigious Y Combinator (YC) accelerator in San Francisco.

The transition wasn't easy. To keep the European engine running while building a footprint in the U.S., Junestrand lived a double life. "I bought a ring light to shine on my face when I took calls between 1:00 a.m. and 10:00 a.m. toward the other side of the world," he says.

This relentless pace paid off. During the YC program, Leya went from zero to nearly $1 million in Annual Recurring Revenue (ARR) in just six weeks. By the time they opened their Manhattan office, they had already secured partnerships with "white shoe" heavyweights like Cleary Gottlieb and Goodwin Procter.

Scaling the Unscalable: 3 to 300

Moving from a three-person startup to a 300-person global organization requires more than just good code; it requires a radical shift in the founder's mindset. Junestrand’s approach to scaling is rooted in brutal self-discipline.

"The hardest part is that your role changes the fastest," he admits. "You cannot be married to the way things were done. You have to be your own best boss and be disciplined about not working on the easy things, but the really hard things."

Even with 300 employees across Denver, New York, London, Stockholm, India, and Sydney, Junestrand remains deeply involved in the hiring process, still interviewing every person who joins the company. He looks for three specific traits:

1. Capacity to grow: Can this person evolve as fast as the company?
2. Problem-solving reflection: Can they look back at a hard problem and articulate how they would solve it better today?
3. Ambition: Do they want to take personal responsibility for the company’s outcome?

The Human Impact of AI

While the $5.5 billion valuation and the aggressive quarterly growth are the metrics the media focuses on, Junestrand finds his motivation in a specific Slack channel titled "Customer Love."

In a profession notorious for burnout and high divorce rates, the impact of Leya isn't just about efficiency—it's about time. "There’s nothing as rewarding as when people let us know we’ve made their day better," Junestrand says. "They were able to finish a piece of work and get home to their families to see their kids before they went to bed."

The Journey to 100

For many, reaching unicorn status is the finish line. For Junestrand, it’s merely the end of the warm-up. He views the current state of legal AI as the transition from "0 to 1." The real work—the journey from "1 to 10" and "10 to 100"—is just beginning.

"We can’t be fast followers. We’ve got to be the innovators," he asserts. As he looks toward 2027, he isn't just building a software tool; he’s building the infrastructure for the future of law.

His advice for aspiring founders is a reflection of his own journey: "You need to be really excited about what you’re doing. If you pick something you aren't excited about, the grind will be too hard. I wake up every day thinking about how we deliver more value."

In the high-stakes game of legal tech, Max Junestrand is no longer just a player; he’s rewriting the rules of the game.

Based on "Karpathy’s "autoresearch" explained in 24 minutes" from Greg Isenberg Watch the original video

The Era of the Automated Scientist: Inside Andrej Karpathy’s “Auto-Research” Revolution

In the fast-moving world of artificial intelligence, a few names carry enough weight to stop the industry in its tracks. Andrej Karpathy—founding member of OpenAI and former Director of AI at Tesla—is one of them. When Karpathy releases a new project, it isn't just a code update; it’s a signal of where the wind is blowing.

His latest obsession, a concept known as "Auto-Research," has recently gone viral, capturing the imagination of Silicon Valley’s elite, including Shopify CEO Tobi Lütke. But what exactly is it, and why are people calling it the beginning of a new era in productivity?

At its core, auto-research is the realization of every entrepreneur’s dream: a "super-nerd robot intern" that runs science experiments on AI models all night long, while you sleep, without requiring a second of manual intervention.

The Anatomy of the Loop: How Auto-Research Works

To understand auto-research, you have to move away from the idea of AI as a chatbot and start seeing it as an agent. Traditional AI waits for a prompt; an auto-research agent follows a loop.

The process begins with a goal. You might tell the agent, "Make this small AI model smarter" or "Find a way to reduce the cost of this code without losing accuracy." Once the goal is set, the agent takes over the driver's seat:

1. Planning: The agent drafts a plan involving different settings, architectural changes, or data tweaks.
2. Execution: It physically edits the Python code and initiates a training experiment on a GPU (Graphics Processing Unit).
3. Evaluation: After running for a set period (perhaps five minutes or an hour), the agent reads the resulting metrics.
4. Iteration: It asks itself, "Did that work?" If the results improved, it saves the changes. If they didn't, it logs the failure and tries a completely different path.

As Greg Isenberg, a prominent tech voice and entrepreneur, puts it: "You wake up, grab the best version, and turn it into something you charge for." It is the "Ralph Loop" applied to the scientific method—engineering that happens 24/7.

From Code to Commerce: 10 Ways to Monetize Auto-Research

While Karpathy’s initial focus was on optimizing AI models, the business community has quickly realized that this "loop" logic can be applied to almost any money-making endeavor. Here is how the next generation of startups will likely leverage auto-research:

1. The "Agent in a Box" for Niche Markets

The most immediate opportunity lies in creating tiny, hyper-focused auto-research loops for specific industries. Imagine an "Amazon Listing Experimenter" that constantly tweaks product titles and descriptions to find the highest conversion rate, or an "Email Sequence Tuner" for realtors that iterates on subject lines until the open rate hits a record high.

2. Autonomous A/B Testing

The days of manually setting up A/B tests in tools like Optimizely may be numbered. An auto-research agent can write dozens of variants of headlines, layouts, and offers, push them to live traffic, measure the clicks, and automatically promote the winner to the "control" position.

3. Research as a Service (RaaS)

Startups and investors spend thousands of hours on due diligence and competitor analysis. An auto-research bot can be pointed at a market to constantly monitor pricing changes, feature updates, and regulatory shifts across hundreds of competitors, delivering a "living memo" that is always fresh.

4. The "Optimize" Button

For existing SaaS companies, auto-research offers a high-tier feature: a literal "Optimize" button. A user could press it, and the system would run a mini-research loop in the background to tune the user's prompts, rank their suppliers, or pick their best pricing tiers based on historical data.

5. The 100x Agency

The agency of the future won't pitch creativity; they will pitch volume. "We run 100 times more tests than any other shop for the same fee," the pitch goes. By using auto-research, an agency can test thousands of ad angles or landing page variables, charging a performance fee for the KPI lifts they achieve.

6. Auto-Quant Trading

In finance, auto-research can be used to run back-tests of simple trading rules overnight. By using Large Language Models (LLMs) to screen for sentiment or filter factors, traders can discard failing strategies and only put capital behind the ones that survived the automated "survival of the fittest" gauntlet.

7. Lead Qualification and CRM Autopilot

By connecting an auto-research agent to a CRM like Salesforce, businesses can test different follow-up rules and messages. The agent learns which leads are most likely to buy and drafts the perfect outreach, allowing sales teams to focus only on high-value closing calls.

8. Finance Ops and Invoice Matching

The loop can be applied to the "grunt work" of accounting—grinding through invoice matching and expense reports, and continuously improving the prompts used to detect exceptions and fraud.

9. Internal Productivity Labs

Large organizations can treat their own KPIs—like ticket resolution time or sales close rates—as the "model" to be optimized. Agents can iterate on internal workflows and templates until the manual labor is stripped away, leaving only high-impact decisions for the humans.

10. Done-for-You Due Diligence

For M&A (Mergers and Acquisitions), auto-research can chew through thousands of pages of filings and product reviews to create structured briefs for investors, identifying risks that a human researcher might miss in a time-crunched environment.

The Human Impact: Beyond the Bottom Line

The excitement surrounding Karpathy’s work isn't just about profit; it’s about the speed of human progress. Tech entrepreneur Morgan Linton recently shared a vision of how this could transform medicine.

"It feels like in many ways clinical trial design is itself a kind of hyperparameter search," Linton noted. Currently, trials cost tens of millions of dollars. An auto-research "agent swarm" could optimize treatment protocols on small proxy experiments, promoting the most promising candidates to human doctors for review. This could potentially shave years off the time it takes to bring life-saving drugs to market.

Furthermore, Karpathy has already launched AgentHub, which he describes as "GitHub for agents." While GitHub is a place for humans to collaborate on code, AgentHub is designed for a "swarm of agents" to work on the same codebase simultaneously, coordinating their efforts through message boards.

How to Join the Movement

If you’re looking to get started with auto-research, there is a small technical hurdle: you need "compute." Specifically, you need an NVIDIA GPU. While high-end chips like the H100 are the gold standard, you don't need to own the hardware.

Services like Google Colab, Lambda Labs, and Vast AI allow you to rent these chips in the cloud for a few dollars. By using package managers like uv and following the documentation on Karpathy’s GitHub (which has already amassed over 25,000 stars), even those with a standard MacBook can begin running their own experiments.

The Bottom Line

We are witnessing a shift from "Software as a Service" to "Experiments as a Service." In the old world, you hired a person to find an answer. In the new world, you hire an agent to find the best answer through thousands of iterations.

As Andrej Karpathy continues to "speedrun" the creation of this new infrastructure, the message to the rest of the world is clear: The loop is running. Those who learn to set the goals for these agents will lead the next decade of innovation. Those who don't may find themselves replaced by a process that never sleeps.

Based on "How Figma engineers sync designs with Claude Code and Codex" from How I AI Watch the original video

The Great Collapse: How AI is Erasing the Border Between Design and Code

For decades, the relationship between software designers and engineers has followed a rigid, almost geological progression. It started with low-fidelity sketches, moved into "grayscale" wireframes, graduated to high-fidelity mockups, and finally—after weeks of meetings and handoffs—arrived at the "expensive" stage: the code.

But at Figma, the team behind the world’s most popular design tool, that linear timeline is imploding.

In a recent deep dive on the How I AI podcast, Figma engineer Alex and designer Ghee sat down with product leader Claire Vo to demonstrate a new reality. By leveraging AI agents like Claude Code and Codex, alongside the Model Context Protocol (MCP), they are turning the "handoff" into a continuous, circular loop.

The result? A world where code can be instantly turned back into design, and design can be programmatically reconciled into a codebase.

The Problem of "Design Drift"

Every product team knows the "Source of Truth" problem. A designer creates a pixel-perfect sign-up flow in Figma. The engineer builds it. But then, a week later, a bug is fixed in production, a new error state is added in the IDE, or a font size is tweaked during a late-night coding session.

Suddenly, the Figma file is a relic of the past, and the codebase is the only place where the actual product lives.

"Often times the codebase gets way ahead of where the actual design file is," Alex explains. "There are states or workflows that just don’t exist at all within the design file."

In the old world, the designer would have to manually take screenshots of the live app and painstakingly recreate them in Figma just to start a new iteration. Today, Ghee and Alex use AI as a bridge. Using the Figma MCP (a connector that allows AI models to "read" and "write" to Figma), Ghee can simply tell an AI agent: "Send the budget allocation page from my local host to Figma."

Within seconds, the live, functional code is translated into editable Figma layers. The designer isn't looking at a static screenshot; they are looking at a living reflection of the code, ready to be manipulated.

The "Decadent Moment" of Product Design

Ghee describes this shift as a "decadent moment" in the history of software. Historically, design was a game of scarcity. Because engineering time was so expensive, designers had to "de-risk" every idea through endless meetings and wireframes before a single line of code was written.

"AI basically collapsed that," Ghee says. "It’s just as cheap to riff in code as it is to riff in design. We can get functional wireframes straight away."

This collapse of the fidelity ladder allows teams to enter an era of "feature abundance." Previously, small polish items or "P2" bugs were often left on the cutting room floor because they weren't worth the cost of the design-to-code pipeline. Now, when the cost of translation drops to near zero, teams can focus on the "craft"—the small details that make a product feel magical.

"It’s the era of 'Yes,'" says Claire Vo. "The idea of the cut line has to disappear. We can put the polish and all the things that make these experiences great back into the product."

Pair Programming for the Visual Era

One of the most impressive demonstrations involved the "Round Trip." Alex showed how he could take a sign-up flow with five different states (error, success, loading, etc.) that existed only in his code and push them all into Figma simultaneously.

Instead of a designer asking, "What happens if the user enters the wrong password?" and waiting for an engineer to find the logic, the engineer simply exports those states into the design canvas.

The collaboration then becomes truly synchronous. While the engineer is working in the terminal, the designer is in the Figma file, "freestyling" with colors, spacing, and "vibes."

"This feels like pair programming for designers and engineers," Vo noted.

Once the designer makes a change—say, adjusting a hex code or moving a button—Alex doesn't have to manually inspect the CSS. He uses Claude Code to "bring the changes from this Figma component into my codebase." The AI compares the design file to the repository, writes the necessary React or CSS patches, and applies them. The engineer becomes a reviewer of the AI’s implementation rather than a manual translator of pixels.

Beyond the Canvas: AI "Skills" and Engineering Toil

The transformation isn't limited to visual design. Alex also shared how he uses "Skills"—essentially custom AI macros—to eliminate the "toil" of engineering.

In a large repository like Figma’s, the process of "shipping" code is fraught with mechanistic hurdles: running linters, checking CI/CD pipelines, ensuring tests pass, and managing "Basil" build commands.

Alex created a /ship skill. Now, instead of "babysitting" a pull request for an hour, he types one command and walks away. The AI agent runs the pre-flight checks, monitors the build, and even automatically fixes minor linting issues that might have caused the build to fail.

"It turns processes that would otherwise be based on best intentions... into something that can be fully automated," Alex says. It’s a shift from reading a static "Onboarding Wiki" to interacting with a "Living Skill" that knows the company’s best practices.

The Human in the Loop: Fine Motor Skills and "Vibes"

If AI can translate design to code and back again, what is left for the humans?

According to Ghee, the human role is moving "upstream." Instead of spending hours on the "mechanistic" work of drawing boxes or threading data, designers and engineers are focusing on problem-solving and "eyeballing."

"No one wants to prompt for the exact hex code or the shade of yellow," Ghee points out. "That’s just easier to just quickly do and directly manipulate."

The future of the designer-engineer relationship isn't about one replacing the other; it's about using AI to handle the "structured data" translation so that humans can focus on the "unstructured" beauty. As Ghee puts it, humans are there to decide if a specific shade of yellow feels "happy" or if a workflow feels "intuitive."

In this new workflow, the question of "Which comes first, the design or the code?" finally has an answer: It doesn't matter. In the loop of the future, they both happen at once.

Based on "The Department of War is making a huge mistake." from Dwarkesh Patel Watch the original video

The Silicon Standoff: Why the Pentagon’s War with Anthropic Is a Battle for the Future of Freedom

In the quiet corridors of power and the glass-walled offices of Silicon Valley, a confrontation is unfolding that may determine the character of the 21st century. It began with a disagreement over "red lines" and has escalated into what some are calling a "warning shot" for the future of private enterprise and civil liberties.

The Department of War (the Pentagon) recently declared Anthropic, one of the world’s leading AI labs, a "supply chain risk." The reason? Anthropic refused to remove contractual restrictions—its so-called "red lines"—that prohibit the use of its AI models for mass surveillance and the development of autonomous weapons.

On the surface, it looks like a standard contract dispute between a defense agency and a picky vendor. But as thinker and podcaster Dwarkesh Patel argues, this episode reveals a much deeper, more chilling reality: the government is beginning to treat the creators of artificial intelligence not as partners, but as subjects.

The Kill Switch Dilemma

To understand the gravity of the situation, one must first acknowledge the government’s perspective. If you are the Secretary of War, you cannot allow a private contractor to hold a "kill switch" over mission-critical technology.

Patel offers a hypothetical: "Imagine if Elon Musk, negotiating Starlink access for the military, reserved the right to cut off access if he deemed a war 'unjust.' As a military, you simply cannot give a private contractor that kind of leverage over a technology you’ve come to rely on."

If the government had simply chosen not to do business with Anthropic, the story would end there. But they went further. By designating Anthropic a "supply chain risk," the government has essentially threatened to destroy the company. This designation forces massive partners like Amazon, Google, and Nvidia to ensure Anthropic’s technology doesn't touch any of their Pentagon-related work. In a future where AI is woven into the very fabric of cloud computing and chip design, such a "cordon sanitaire" could make it impossible for Anthropic to exist as a private business.

A Civilization Built on AI Labor

The stakes of this standoff are heightened by the timeline of AI development. We are not just talking about a smarter version of a chatbot. Within 20 years, it is estimated that 99% of the workforce—in the military, the civilian government, and the private sector—will be AI.

"They’re going to be the robot armies that constitute our military," Patel notes. "They’re going to be the superhumanly intelligent advisers that senators and presidents and CEOs have. They’re going to be the police. Our future civilization is going to be run on AI labor."

If the government establishes a precedent today that it can bully AI companies into dropping ethical safeguards, it isn't just winning a contract; it is ensuring that the entire future infrastructure of human society is built on "blindly obedient" silicon employees.

The End of the Surveillance Bottleneck

One of the most immediate concerns regarding this "blind obedience" is mass surveillance. Historically, the Fourth Amendment and our general sense of privacy have been protected by a practical bottleneck: human manpower.

The government may legally be allowed to buy your data from third parties, but no agency has the staff to watch every CCTV camera or read every email. AI changes that math forever.

Patel highlights a staggering calculation: There are roughly 100 million CCTV cameras in America. With current AI processing costs, it would cost about $30 billion to process every single frame of every camera in the country. But AI capability gets roughly 10x cheaper every year. By 2030, it will be less expensive to monitor every nook and cranny of the United States than it is to remodel the White House.

"Once the technical capacity for mass surveillance and political suppression exists," Patel warns, "the only thing that stands between us and an authoritarian state is the political expectation that this is just not something we do here."

The Virtue of Disobedience

This brings us to the heart of the "alignment" problem. In the AI safety community, "alignment" usually means getting an AI to follow a human’s instructions perfectly. But what if those instructions are evil?

History suggests that human civilization has often been saved not by obedience, but by its opposite. In 1983, Soviet Lieutenant Colonel Stanislav Petrov was on duty when his early-warning system signaled that the U.S. had launched five nuclear missiles. Protocol demanded he report it, which would have triggered a massive Soviet retaliatory strike. Petrov judged it a false alarm and refused to follow orders. He was right. If he had been a "perfectly aligned" AI, hundreds of millions would have died.

Similarly, the Berlin Wall fell in 1989 because East German border guards eventually refused to fire on their fellow citizens. "One person’s virtue is another person’s misalignment," Patel observes. If the government succeeds in forcing AI companies to strip away their moral "red lines," we are effectively building a world where there is no Stanislav Petrov—only a perfectly obedient machine executing a command, no matter how catastrophic.

The Regulatory Bazooka

Ironically, Anthropic has been one of the loudest voices calling for government regulation of AI. They have argued that the risks of AI—bioweapons, cyberattacks, and "autonomy risk"—are so great that we need a regulatory body similar to the Nuclear Regulatory Commission.

However, the current spat with the Pentagon suggests that such a regulatory framework might be a "fully loaded bazooka" handed to a power-hungry leader. Terms like "national security threat" or "catastrophic risk" are notoriously vague. If a model refuses to help the government with mass surveillance, a future administration could easily label that an "autonomy risk" or a "threat to national security."

The government is already using the Defense Production Act (a 1950s law meant for steel mills) and supply chain statutes (meant to keep out Chinese hardware) to pressure AI labs. Giving them a purpose-built AI regulatory apparatus might only accelerate this "thuggish" political pressure.

The Way Forward: Regulate Uses, Not Intelligence

Is there a middle ground? Patel suggests we look to the Industrial Revolution. Like AI, industrialization was a general-purpose transformation of society that created terrifying new weapons. Yet, free societies didn't handle it by giving the government absolute control over every factory. Instead, they regulated specific uses—banning chemical weapons or regulating how the government can use industrial power against its citizens.

"We should regulate AI in a similar way," Patel argues. "We should regulate specific destructive use cases... and we should also have laws which regulate how the government can use this technology."

Ultimately, corporate courage from companies like Anthropic is a noble but temporary fix. As AI technology diffuses and open-source models catch up to the frontier, the government will eventually find a vendor willing to say "yes" to mass surveillance.

The only lasting protection for a free society is the creation of robust political norms and laws. We must decide, as a civilization, that some things are off-limits—even for the most powerful government on Earth. If we fail to do that, we aren't just racing to beat our adversaries in the AI race; we are racing to become them.