Without Limitation

Matt Pollins

Stories from the people reshaping legal www.agents.law

  1. 4d ago

    The Unbundling of Legal Work

    What can the legal industry learn from medicine? That’s the question I put to Liam Brown, the founder and CEO of Elevate, in the latest episode of Without Limitation. Liam founded the company in 2011 - but if you rewind all the way back, he trained as a doctor in London in the late 1980s. He left medicine, but it completely changed how he thinks about process - triage; checklists; the difference between brain surgery and routine care. Medicine has worked out, over decades, how to unbundle work and give each part to the right person or system. Liam has applied what he learned at medical school for more than 35 years. He looks at a process and asks: why does this work have to be done this way, by this person, in this place? The technology has changed several times in those 35 years, but this question has pretty much stayed the same. And right now, with AI forcing every firm and legal team to rethink how work gets done, I think it is a more important question than ever. 🎧 Listen on Spotify or Apple Podcasts. Lupl was acquired by Elevate in August 2026, so Liam and I now work together. It was a fun experience interviewing a colleague for the first time. Two key lessons from medical school Liam took two lessons from medicine into business. The first came from the AIDS crisis in the 1980s. Back then, a needlestick injury with infected blood could kill you, so the NHS issued new safety syringes. The catch was that they needed two hands, which meant someone else had to hold the patient. Almost nobody used them. About six months later, a one-handed version arrived, and within two weeks it was everywhere. Liam’s lesson: if you make something easy to use, people adopt it. He saw the same pattern later with M&A lawyers and bankers: give them a better tool and they will change how they work. The second lesson is about unbundling. Junior doctors at the time worked brutal hours and complained about it constantly. Then the NHS let other clinicians take patient histories and do initial examinations. The doctors, he says, were furious - how could they give good care if they hadn’t done that work themselves? Liam’s diagnosis is candid: “What was really going on was that we thought of ourselves as special, and the idea that you could unbundle any element of our work and give it to someone else really rubbed up against our sense of specialness.” The end result, in Liam’s opinion, was that doctors actually had more time to talk to each patient and understand them as a whole person. A career challenging the status quo The unbundling thread runs through pretty much everything Liam has built since. * Typesetting in London. After leaving medicine, Liam ended up running the document production group of a financial and legal publisher: a heavily unionised shop, in a recession. Work on IPO prospectuses was expensive, slow and done in the city, with premiums if it ran into the weekend. His question: can’t we move this work electronically somewhere else? Desktop publishing made the answer yes, and that led to round-the-clock delivery and a very different cost structure. * A data room business. In the mid-1990s, Liam was running business development for a public company and was frustrated by how labour-intensive M&A diligence was (flying to another firm’s office and reading paper documents at 10pm, etc.). This again was one of the processes most ripe for unbundling. So, he started one of the earliest virtual data room companies, backed by Silicon Valley VCs, and sold it just before the dot-com bust (”more by luck than judgment”). That business went on to become Datasite. * Integreon. If work could be digital, maybe knowledge work could be unbundled too. Integreon’s first customer was McKinsey: moving research and presentation work to India so consultants could spend more time with clients. Then investment banks. Then, as the late adopter, law, working with Clifford Chance and Microsoft on what we would now call legal process outsourcing. Integreon grew to a couple of thousand people. * Elevate. After a strategic disagreement with Integreon’s private equity investor (Liam says, cheerfully, that he “actually got fired”), he sold his stake and used the proceeds to fund a new company. Instead of raising venture capital, he asked a group of people he respected, including John Croft, to go without pay for a couple of years in exchange for equity. The elevator pitch was “Accenture for law”: consulting, software, data and global delivery for the run-the-company work that has to be done right. The new paradigm = “Experts + AI” I asked Liam what has changed in the 15 years since Elevate launched. An oversimplified summary of the early days might be “move the work somewhere cheaper”. What is it now? Liam’s view is that in-house teams increasingly want to buy complete solutions, rather than the constituent parts. He walks me through the moving parts of transformation in legal departments: * Legal process outsourcing. Unbundle some work and send it offshore. * Flexible lawyers. Hire experts locally, at lower cost than law firms (the Axiom and Lawyers on Demand model). * Legal tech. An explosion of tools, which someone has to buy, configure and run. * Legal ops. A new function to manage all of this complexity and decide what goes to the law firm, what goes to the ALSP and what stays in-house. The problem with that sequence is that the client ends up doing the integration. They have to weave the experts, the delivery teams and the software back together themselves. Liam tells me that Elevate’s response has been to build all the pieces under one roof. Legal professionals in the US, the UK, Australia and elsewhere. Global service delivery in places like Poland, India and the Philippines. Regulated law firms (Elevate acquired Halebury, an ABS in England and Wales, and has its own US law firm and an ABS in Arizona). And, since acquiring LexPredict in 2018, its own AI capabilities. As Liam put it: “We don’t pay Harvey or Legora. We know which machine tools to use for which steps in the workflow.” In Liam’s view, customers want an outcome, delivered by experts who “look like us, sound like us, and have walked in our shoes”, without having to assemble the supply chain themselves. I think this is a useful test for the current wave of AI-native law firms, many of which say they sell outcomes rather than hours. Who carries the responsibility? Who chooses and runs the tools? If the answer is the client, the client is still buying parts. Two steps forward, 1.97 steps back None of this was easy, and Liam is honest about that. From 2019 to about 2023, getting lawyers, process experts, delivery teams and AI to work together in a multidisciplinary way felt like “two steps forward and 1.97 steps back”. Then ChatGPT arrived, and the tools got much more powerful almost overnight. But the interesting part of Liam’s account is what made the difference for Elevate: years of change management. The company already had a workforce used to experimenting with process and service design (and redesign). So, the new tools landed on prepared ground. Which brings me to checklists. Liam and I are both fans of Atul Gawande’s The Checklist Manifesto. Surgeons and pilots use checklists because the work is too complex and too fast to rely on memory. Law adopted that discipline late. What I find interesting is that AI agents need checklists too (I wrote about this in How To Train Your Agent). A firm that has already written down how it does its work has a large head start in teaching an agent to help. Is the billable hour finished? In Liam’s view, no. Firms will build a portfolio of models, with hourly work alongside productised and subscription offerings. The reason is buying behaviour. For high-stakes work, he does not believe the unpredictability of the hourly bill causes enough pain to outweigh what clients get from an elite firm: certainty of getting the deal done, the brand, and the protection that comes with it. Clients will keep paying by the hour, he thinks, as long as t… This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit www.agents.law

  2. Jul 23

    What Can Law Learn from TV and Music?

    Meet Anthony In 2009, Wired magazine described Anthony Rose as “the man who saved the BBC”. To say he’s not your usual legal technology founder is an understatement. As a teenager in Cape Town, he made circuit boards in his study. One day he took his boards into the local Apple store, in the era of the Apple II. They wanted to buy 20 of them. His first business was born. The hardware business took him from South Africa to Australia, morphed into real-time 3D graphics, and then into something that would put him at the centre of one of the defining tech battles of the era: Kazaa, the peer-to-peer file sharing company. Exhibit A If you want to understand how Anthony thinks about the legal industry today, you have to start with the music industry in the early 2000s. CD sales were a $10 billion a year business, declining by a billion dollars a year as the internet rose. Anthony was in New York, sitting across the table from music label executives, telling them that in the time it took to read his PowerPoint, 100,000 of their tracks had been downloaded, and they could have monetised every one of them. Instead of signing a licensing deal, he says they made his pitch “Exhibit A” by suing Kazaa, and losing the revenue anyway. The labels spent enormous sums trying to litigate file sharing out of existence rather than reinvent themselves. Cut to today: almost nobody buys CDs, and the overwhelming majority of music revenue comes from streaming. As Anthony puts it, the revenue needed to decrease to force change. While the revenue is good, nobody wants to change. He’s watched the same pattern play out three times now. Music was the first. Broadcasting was the second (we’ll come onto that). Law, he believes, is the third. The chocolate box test Between Kazaa and SeedLegals came the chapter that earned Anthony that Wired headline. Full disclosure: I spent time at the BBC early in my career and I’m very fond of it, so this part of the conversation was a treat. Anthony was hired in 2007 to take iPlayer from years of internal noodling to an actual launch, in three months, with failure not an option. His first instinct was that the tech team must be the problem, because nothing worked. What he found was the opposite: a brilliant tech team being pulled in every direction by an organisation not orientated around the customer. BBC One wanted a BBC One player. BBC Two wanted a BBC Two player. The distribution department wanted to save money with a low-quality peer-to-peer system. Nobody was aligned around the viewer. So Anthony appointed himself customer champion and invented what he calls the chocolate box test. Quoted £20,000 and six weeks for formal user testing, he went to the supermarket instead, bought big boxes of Lindt chocolates, and bribed non-technical colleagues (often, amusingly, the legal team where I was sitting - because they were the “least technical”) to come downstairs and try to find their favourite programme while the developers watched. The first session was a disaster. They fixed the most important things, ran it again, and by the third round the tester said “I like EastEnders”, found it on the homepage, and pressed play. None of the startup literature really existed in 2007. Anthony made customer-driven development up as he went along, and it’s the thread that runs through everything he’s built since. His rule: any time an incumbent designs a model that doesn’t align with what the customer actually wants, you’re looking at the next startup disruption opportunity. (A confession from me: I actually took part in some of those chocolate-funded user tests at the BBC, on the sport website. Nobody gave me any Lindt. I’ll be raising this with the Corporation.) Nobody wants a legal document That customer lens is what makes SeedLegals interesting. When Anthony and his co-founder Laurent started the company, they thought the problem to solve was the efficient generation of legal documents. What he’s since realised is that no one wakes up in the morning wanting a legal document. They wake up needing to raise investment, hire someone, or close a deal. The document is a means to an end. The real product, he argues, is empowerment. It means being able to go on the platform on a rainy Sunday and have your investment agreement five minutes after finding an investor. It means no clock ticking by the hour. It means data on market-standard deal terms, so you know you’re not the only schmuck in the room giving away too much. SeedLegals now has 50,000 startups on the platform in the UK, a team of 150, and a claim to the majority of all early-stage UK rounds. It also explains why Anthony personally spends so much of his time on things that look nothing like legal tech: workshops and webinars on the art of the pitch, storytelling, and how to build a landing page that says what your company does. His favourite failure mode is the founder who describes their product brilliantly over dinner, then sends you to a website full of swirly atoms and an AI brain that says “using blockchain and AI to revolutionise insurance”. If you define the customer’s job as “raise money” rather than “obtain documents”, the product roadmap looks very different. Law firms might take note. The SAFER Anthony now spends two weeks a month in New York, running the US expansion himself rather than making the classic mistake of hiring an expensive marketing lead and hoping. The US market, he says, is bifurcated in a way the UK isn’t. A priced round can cost $50,000 to $100,000 in legal fees, so 13 years ago Y Combinator gave the world the SAFE: a free, downloadable IOU that lets founders skip lawyers entirely until the big round arrives. Anthony’s contention is that the SAFE is, well, not safe. US founders make far more mistakes than UK ones: wrong company type, missed 83(b) elections, no understanding of investor tax benefits. And there’s a specific wrinkle around QSBS, the US capital gains exemption that requires a five-year holding period. The IRS has never ruled whether that clock starts when you sign a SAFE or when it later converts into stock, and founders are essentially gambling on the answer. SeedLegals’ response is a new product, launching shortly, called the SAFER. Instead of kicking the can down the road with an IOU, it productises the proper issuing of stock so that it’s fast and inexpensive, and the QSBS clock starts ticking immediately. It’s a very SeedLegals move: find the gap between free-and-risky and expensive-and-slow, and build the middle. Build it this weekend My favourite practical moment of the conversation was Anthony’s direct advice to lawyers. Almost every lawyer has an idea for using technology or AI to improve something in their practice. Historically there was no path from idea to demo without budget, developers and a steering committee. Now there is. Tools like Lovable and Claude mean a non-technical lawyer can describe what they want in plain English and have a working mock-up before their coffee machine warms up. So his suggestion: build it over the weekend, walk in on Monday and say “you know the thing we’ve been talking about? Here it is.” It won’t be the production version, and the client data questions come later, but you’ve crossed the gap between arm-waving and something people can touch. And then, perhaps for the cost of a box of Lindt chocolates, you can get your colleagues to test it. As regular listeners know, I’m a big fan of this approach. Every marketing page, every prototype, is a hypothesis. That’s an uncomfortable mindset for lawyers, who are trained to be right, but it’s the mindset this era rewards. (And when you’ve built something, share it on vibecode.law!) Vibe raising and Virtual Anthony SeedLegals is also reinventing itself as an AI company, because Anthony is acutely aware that even his own company isn’t immune to disruption. The team has built AI feedback for SEIS/EIS advance assurance applications, trained on the tens of thousands SeedLegals has processed (their success r… This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit www.agents.law

    What Can Law Learn from TV and Music?
  3. Jun 4

    TED and the Future of the Lawyer

    I meet Nishat Ruiter, GC at TED, the world's most influential ideas platform, and learn how TED Law is asking us to question what it means to be a lawyer. What we cover * How TED grew from a conference to become the world’s #1 ideas platform. * Nishat’s unconventional path, via the Netherlands, the Brooklyn family court, and the self-taught IP licensing work that helped launch her GC career. * How organising a local TEDx event gave Nishat a deep understanding of TED’s mission before she ever joined the organisation. * What TED looks like behind the scenes, from the main conference to TEDx, TED-Ed, podcasts, partnerships, licensing, translation and global community-building. * Why Nishat launched TED Law, and what she thinks legal education misses around judgment, professional identity, cultural competence, collaboration and moral courage. * How you can get involved in TED Law (that includes law firms, in-house teams and tech companies). Meet Nishat When I catch up with Nishat Ruiter, it has only been a few weeks since the latest TED conference in Vancouver. The conference itself is over, which sounds like a natural moment to come up for air, but TED is really a year-round organisation of talks, TEDx communities, podcasts, partnerships, education programmes, licences, brand questions, rights questions, publication decisions and all the legal work that has to happen to make sure ideas can safely reach the world and have the maximum impact. Nishat sees that world from an unusual seat. She gets the force of the talks, the audience energy, the spectacle and the sense of possibility, while also leading the back-office legal review that makes the public version possible. A TED Talk may look effortless by the time it reaches the stage or the internet, but behind it sit questions about rights, privacy, defamation, intellectual property, accuracy, context and reputation. That is part of what makes her role so interesting: she is protecting ideas without wanting to smother them. The bigger question in our conversation is what happens when you apply TED’s vision of “Ideas change everything” to the world of law. TED is built around curiosity, clarity, public communication and the belief that a well-framed idea can move people. Law, at its best, is built around judgment, service, justice and the structures that allow human beings to cooperate. Yet the profession has often taught lawyers the rules far more deliberately than it has taught them how to carry those rules into leadership, crisis, culture, technology and moral choice. TED Law is Nishat’s attempt to address that gap. From Dracula to Brooklyn family court Nishat did not grow up with a plan to become a lawyer. Her first love was theatre. In high school, she acted seriously enough to play the lead in Dracula, which I point out should definitely be on her LinkedIn profile. She was drawn to the empathy of acting: understanding a character, getting under the surface, working out why someone acts as they do. A high school director then gave her a blunt assessment of the acting world. If she wanted to pursue it, she should understand the reality of the industry: she was not white, she was not blonde, and she would not fit easily into the box. It was a hard thing to hear, and it became one of the early experiences behind a theme that runs through her career: finding herself outside the expected shape and then building from there. Law arrived almost sideways. In college, she took a course on the legal and social environment of business. The professor posed a simple hypothetical: a student slips on a banana peel at a university. Who is responsible? Everyone wanted to defend the student. Nishat raised her hand to defend the university, less because she had some sophisticated view of liability and more because she was excited by the less obvious side of the argument. She liked the reasoning, the exploration, the challenge of working out the answer. That instinct took her to law school, where she initially imagined a career in international human rights and justice. After graduating, she spent time in the Netherlands, where her husband is from, and explored international work. But law school loans and practical realities eventually pulled her back to the United States. When she returned, she did what many young lawyers do: she applied for what was open. One of those openings was in family law. She worked for a sole practitioner in Brooklyn for two and a half years and saw, up close, the human pressure of matrimonial litigation. Custody. Support. Divorce. Lives being rearranged in courtrooms that had far too many cases and far too little time. At one point, she says, a judge might have 120 cases on the docket and two minutes to hear yours. The work mattered enormously, but the system around it could feel too arbitrary for questions that were so consequential. So she moved back toward intellectual property and technology. This was the dot-com era, before anyone could ask ChatGPT how to become a software contracts lawyer. Nishat went to Barnes & Noble, read everything she could find, and built herself a three-ring binder full of software licensing contracts. When she interviewed for a contracts manager role and they said they were looking for someone with templates, she had them. Then she made the obvious legal career move: if she was going to be the only legal person, perhaps she should be general counsel. That is a very Nishat story. She sees the gap, does the work, builds the thing and then makes it happen. Thanks for reading Agents.law! Subscribe for free to receive new posts and support my work. Finding TED before TED found her Before TED, Nishat built a career across IP, fintech, software, legal tech and a decade as associate general counsel at CA Technologies. The bridge into TED, though, began in Hillsborough, New Jersey, where she and her husband had chosen to live for practical reasons: schools, work, family life. They also cared deeply about community. Her husband is Dutch. Nishat is Pakistani. Between Dutch bluntness and Pakistani directness, she says, there was no shortage of intense discussion at home, but there was also a shared global outlook and an interest in ideas that could bring people together. Nishat was serving on the township library board and felt that the community could do more to surface meaningful ideas. TED had already been part of their family life. Her husband was an early fan, and they would introduce high school students to TED Talks. So they organised a TEDx event through the library. That meant finding speakers, shaping talks, dealing with the intellectual property, building the event and learning what TED actually requires of a local community. It took six months. She did it without any thought that she would one day work for TED, but it gave her a lived understanding of the brand, the mission and what happens when TED’s global idea is translated into a local setting. Then, during a career shift, the pieces came together. Nishat had just accepted a new role in New Jersey. Her children were in high school. She was tired of commuting into New York and wanted to be more present at home. Around the same time, a friend who had recently joined TED in video and TED Talks asked about her work. At the time, TED had no in-house lawyer. Outside firms helped with some matters, but the publication of talks raised exactly the kinds of questions Nishat understood: IP licensing, defamation, privacy, rights, risk and the judgment needed to review content without flattening the idea behind it. She had already accepted another job, so when she sent over her resume she added the caveats: she had family constraints, she did not want a five-day-a-week New York commute, and the timing would be difficult. Chris Anderson wrote back the next day. Within a week, she had met with TED’s leadership and had an offer. It sounds almost too neat, but the fit makes sense. TED needed a lawyer who understood intellectual property and also understood why the ideas mattered. The platform behind the talks Most people know TED through the talks. For many of us, TED is still associated with the canonical talks that seemed to break through the early internet: Sir Ken Robinson on education and creativity, Hans Rosling on population and data, and countless others that made complicated ideas feel alive. But TED is much broader than the stage. It began in 1984 as a conference around technology, entertainment and design. Chris Anderson later helped turn it into a nonprofit and, in 2006, TED began putting talks online. The expectation was modest. Perhaps the talks would reach 100,000 views. They reached around a million in the first month, and TED became a way of bringing ideas to people wherever they were. That required production, publishing, translation, distribution, licensing, brand stewardship and, eventually, an enormous global community. TEDx was another leap. What began as a risky experiment in giving communities a free licence to convene around ideas has become something like 4,000 to 4,500 events around the world. Then there is TED-Ed, with its animated lessons created with teachers and artists. There are podcasts, partnerships, education programmes, the Audacious Project and the many other ways TED tries to make ideas travel. A small legal team supports all of that. Their job is to help TED stay true to itself while operating globally, across formats, partners, communities, rights systems and cultural contexts. It is harder than it looks, and it gives Nishat a useful vantage point on the difference between protecting an institution and preserving the spirit that made the institution worth protecting in the first place. AI and the purpose question We spoke, inevitably, about AI. TED has always been close to the frontier of technology; many of the people shaping what comes next have appeared on the TED stage early, sometimes before their ideas became mainstre

    TED and the Future of the Lawyer
  4. May 26

    The World’s Best Vibecoder is a Lawyer

    In the latest episode of Without Limitation, I meet Michael T. Brown. When I sit down with Mike, it has been around three months since he won the Anthropic global hackathon, beating 13,000 applicants, most of them career engineers, with a project built in six days from his home in Orange County. We’re also chatting on the day before he takes the main stage at Code with Claude in San Francisco, one of the biggest software events in the world this year, where he will be delivering a thirty-minute keynote. Listen to the full episode on your favourite platform, or keep reading for my take on the conversation. * Apple Podcasts * Spotify Not a software engineer Mike is, by his own admission, not a software engineer. He has never written a line of code in anger. He is a personal injury attorney by background, with a previous career in Hollywood. Of the top 5 finalists that Anthropic announced, only one was a full-time software engineer. The others included a cardiologist, an electronic musician, an infrastructure worker from Uganda, and Mike, who took the overall crown. So how did a lawyer win the Super Bowl of hackathons? And what does his story tell the rest of us about what is possible with these tools right now? Join me on 17-18 June: We are running what promises to be the biggest vibecode hackathon in law, at LegalTechTalk in London. This is a unique event, in partnership with HSF Kramer and Replit. You’ll get free Replit Pro credits just for participating, and there are some great prizes on offer. But to be involved, you must register. Hollywood to law school to a maxed-out credit card Mike didn’t set out to be a coder, or a lawyer for that matter. He spent his twenties in Hollywood doing visual effects work. He did what he describes, with a smile, as the rational response to any burnout: he went to law school. He fell into personal injury practice and genuinely liked it. He spent a few years at California PI firms before hitting the decision point most PI lawyers eventually hit, which is making the decision to go out on his own. That decision happened to land in late 2023, just as ChatGPT was changing what was possible. Faced with the usual choice between hiring paralegals or burning through savings on back office support, Mike did something different. He started building prompt libraries before anyone was calling them prompt libraries, recording intake calls with client permission, transcribing them through Whisper, and feeding the transcripts into ChatGPT to produce his own version of an intake form. The system worked well enough that his cousin, a serial entrepreneur, suggested they productise it. They built a company called Onbreeze, a note-taking phone line for lawyers, on the insight that injured clients don’t book a Zoom call with a lawyer - they call. Vibecoding wasn’t mainstream at this point, and Mike outsourced the entire development process to an external development agency. The product launched in January 2025. Unfortunately for Mike, it crashed the moment a fourth caller hit the line. When the offshore engineering team explained that fixing it would cost roughly the same as building it had, Mike was already maxed out on credit cards. He downloaded Cursor (an AI coding tool) instead. Ten minutes later, by talking to it about what he needed, he had a working solution. He still couldn’t read the code. But the thing worked. That was his first prompt. How Mike learned to build Onbreeze didn’t take off the way Mike hoped. By May 2025 he was at a crossroads: go back to practising law full time, or lean into the strange new fluency he’d developed with vibecoding tools. He chose the tools. But what’s interesting is how he chose them. He didn’t go and learn to code in the traditional sense. He took on a series of consulting projects for friends and family, each of which forced him to learn one new thing. A roll-up project for a private equity contact taught him how to handle data across complex databases. A pickup ordering system for his cousin’s butcher shop in Brooklyn taught him Stripe. Mako, a demand letter generator for personal injury lawyers, taught him how to deploy agents to the cloud using Anthropic’s SDK. He describes it as accidentally building a curriculum. Each project was something he wanted to learn anyway. Each one came with a real user on the other side. And each one added to a stack of skills he could combine later. By the time the Anthropic hackathon was announced in early 2026, Mike was already far more fluent with the technology than most. Picking a problem nobody could solve The hackathon accepted only 500 of the 13,000 applicants, and the brief was specific: they wanted problems that weren’t solvable with previous generation models. The problem was California’s housing crisis, or more precisely, the permits bottleneck inside it. “Everyone thinks California has a housing crisis,” Mike puts it. “We don’t. We have a permit crisis.” His friend builds ADUs (Accessory Dwelling Units), the small backyard cottages California has incentivised as a partial answer to its housing shortage. The laws are favourable, the demand is there, and yet permits routinely take six to nine months, with endless back and forth between builders and city plan reviewers. Mike had a hunch AI could help. He asked Cameron to send him a set of blueprints. Claude couldn’t handle them. The pages were physically too big, the size of a table, and the dense annotations meant traditional OCR pulled the text away from the visual context that gave it meaning. A note about wall thickness only mattered if you knew which wall it referred to. By this point, most people would probably move on, but Mike saw an opportunity. If the most advanced Anthropic model available at the time couldn’t handle this, then it was exactly the kind of problem the hackathon judges were looking for. He submitted, got accepted, and immediately had a small panic about whether he could actually solve it. The lesson buried in this is that problems are way more important than solutions. Most vibecoders jump straight into building things. Mike spent his time finding a problem worth building for, one that mattered to a real user and that pushed the technology to its current limit. Building it in six days Mike decided to call the app CrossBeam. The hackathon ran for a week and by Wednesday night, two days in, Mike was in trouble. He had two disparate approaches, neither of them working, and the hour was getting late. He scrapped the elaborate combination of OCR plus image referencing he’d been wrestling with, and went back to first principles: here are the rules, here are the chunks of blueprint, figure out what’s wrong. That first end-to-end run hit roughly 40% accuracy against the city’s correction letters. Crucially, it ran. Once a system runs end-to-end, even badly, you can benchmark it and improve it. By Thursday afternoon he was at 60 to 70%. Two design choices were key here. The first was treating the model’s context window as a precious resource rather than a dumping ground. Mike used Skills, Anthropic’s open standard (think of them like those files that get uploaded to Neo’s brain in the Matrix so he suddenly knows Kung Fu), to keep his prompts lean. He used parallel sub-agents, each with a narrow job and a fresh context, rather than one bloated agent trying to do everything. He used what he calls adversarial prompting: have one agent plan, a second agent execute, and a third agent test, so that no single agent is grading its own homework. For this, he uses an analogy from legal practice: “When an associate brings you a memo, you don’t ask them if they double checked it. Of course they’re going to say yes. You give it to someone else to check.” The second design choice was testing. He set up command line interfaces on the backend so that one Claude instance could run a new ADU through the system every hour while he worked on something else, tracking accuracy gains in real time. By Friday his accuracy was high enough that… This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit www.agents.law

    The World’s Best Vibecoder is a Lawyer
  5. May 15

    Why India is a Legal Tech Superpower

    Shreya Vajpei built the community for legal tech in India. Now she's connecting that community with the rest of the world. India has more legal tech startups than almost anywhere on earth. I did not know this until I sat down with Shreya Vajpei, but India has around a thousand legal tech startups, which Shreya tells me puts it second only to the US and ahead of every other market, including the UK. That is a striking number for a country where foreign law firms still can’t really practise, where only advocates can own law firms, and where the entire legal services market is about a fifth the size of the UK’s. If there’s one person who can help us make sense of this landscape, it’s Shreya Vajpei. Listen to the full episode on your favourite platform, or keep reading for the full write-up. * Apple Podcasts * Spotify Introducing Shreya Shreya trained at Khaitan & Co, one of India’s tier one firms and roughly the magic circle equivalent in the Indian market, with around 800 lawyers when she joined and closer to twice that today. Like many guests on Without Limitation, her career has taken an unconventional path. She practised for a couple of years before moving into a practice development role. Then, COVID hit and the marketing budget disappeared overnight, which meant her team ended up absorbing everything else the managing partner needed help with. That covered IT, HR and operations, but also pricing, strategy, new office openings, partner performance and strategic hiring. In her words, whatever landed at the managing partner’s table also landed at theirs, which gave her something most lawyers never really get, which is a top-down view of a law firm as a business rather than a bottom-up view of a practice. From there she became one of the first hires into Khaitan’s innovation team, and her role kept evolving as AI did. Last year she moved to the UK to join Stephenson Harwood, drawn by what she described as a more mature market for digital transformation, with longer-established innovation teams, more consistent IT budgets, and a decade or so head start on the journey. A thousand startups Shreya tells me that India’s legal services market is around $10 to $15 billion in total, roughly a fifth the size of the UK’s, and it is wildly unconsolidated compared to what most of us are used to. The top five firms are similar in size to each other, in the 1,500 to 2,000 lawyer range, and then there is a big gap before you reach the long tail of full-service firms operating somewhere between 50 and 200 lawyers, and then the boutiques and independent chambers, and then a hyperlocal market across the tier two and tier three cities that operates almost entirely separately and accounts for the vast majority of India by population if not by revenue. On top of that, foreign firms still can’t really practise there, a liberalisation bill has been pending for years with significant local opposition, and there is no ABS or non-lawyer ownership of any kind. So the obvious question is why a market with all of those constraints has produced so many startups, and Shreya’s answer is partly cultural, partly economic, and partly a story about talent. India, she tells me, is generally entrepreneurial and high risk-taking, which feeds directly into the volume of founders willing to have a go, and it has some of the best developers in the world at cost structures that make building viable in a way that is hard to replicate elsewhere. The economics also push founders outward almost from day one, because rupee revenues are small once converted, so the dominant playbook is to build in India and sell internationally, which is exactly what companies like SpotDraft (now established in the US and entering Europe) and Lucio (which recently opened a New York office) have done. One category worth flagging, because it is more advanced in India than most other places, is online dispute resolution (ODR). SEBI, the securities regulator, now requires all investor disputes to go through an ODR platform, and there is open API infrastructure called the Pulse Protocol that allows any ODR provider to plug in, in much the same way that UPI revolutionised payments by giving every bank and every app a shared rail to build on. India tends to solve problems at the infrastructure layer when it solves them properly, and ODR is a good example of what that looks like in practice. The bridge What makes Shreya interesting beyond her own story is that she has lived on both sides of the bridge between the Indian and international legal tech ecosystems, and she has clear views on what each side keeps getting wrong about the other. For Indian startups looking to scale into the UK and US, she offers a network and an instinct for what magic circle firms actually buy, which is not always what an Indian founder might assume from a distance. Last year she worked with the UK Department of Business and Trade to bring a contingent of Indian legal tech startups to the UK to meet magic circle firms, Scottish firms, and the Legal Tech Talk crowd, and that kind of bridging is something the industry could probably use more of. For international players trying to enter India, she sees the same mistakes repeated. Pricing set for the US market with no real adjustment for local realities. Customer support sitting in time zones that do not overlap with the Indian working day. A lack of appreciation for the fact that the biggest Indian law firms still operate across multiple languages alongside English, and that most LLMs do not handle Indian languages or scripts particularly well, which means translation is a first-order use case rather than an afterthought. She makes the point that the legal AI players doing well in India have generally understood that the same product positioning does not travel intact, because the problem itself is not quite the same as it is in the US, and the reframing has to happen locally rather than being assumed away. If you want to tap into this network, it is at indianlegaltech.net. On influential women in legal tech Shreya recently won an ILTA Influential Women in Legal Tech award. We discuss how her award sits against a backdrop that most people in the industry recognise but that not enough are actively doing something about, which is that around 3% of startup funding flows to female founders, and legal tech is no exception. As Shreya puts it, some parts of the ecosystem have become a “boys’ club” where the funders and the people asking for funding are both part of the same cycle, and that cycle is genuinely hard to break from inside it. Her recommendations are practical rather than abstract. She suggests that if your firm runs an incubation programme, ring-fence dedicated seats for female founders. If you sit on a legal tech fund, write a hypothesis that requires a female founder on every backed team. And if you are a woman who has made it into a decision-making role with some capital to deploy, invest in another female founder, because even one extra month of runway can sometimes be the difference between a company that survives and one that doesn’t. She also made an observation that that a lot of the buyer-side decision makers in legal innovation, the heads of innovation and heads of knowledge across the larger firms, are women, and the supply side of the industry has not really caught up with that. On the AI-native firm We finished, as I tend to with these conversations, on whether law firms are actually changing or just dressing the old model up in new clothes. Shreya uses the factory electrification analogy, which is my personal favourite as well. When factories first switched from steam to electric power, owners swapped the engines but kept the same layout, the same processes and the same workflows, which meant they got slightly faster operations but not much else. The real productivity gains came decades later, when factories were redesigned from the ground up around the new power source rather than just retrofitting it into the old design. Most law firms are still firmly in the swap-the-engines phase, treating AI as a tool that makes existing tasks slightly more efficient rather than as a medium for rethinking what legal work is and where the value actually sits. Look at almost any legal tech company website and the framing is the same: draft 20% faster, research 30% faster, all of which assume the underlying tasks remain the tasks lawyers do. The harder question, which Shreya thinks almost no firm has properly sat down with, is where the value layer actually lives in a professional services business once AI is properly in the picture, and what you would build if you started from that question rather than from the current shape of the firm. AI is now forcing the rethink that should arguably have happened years ago, and for those of us interested in true innovation in legal services, that is probably the most exciting part. If you are building in legal tech and you have not yet thought seriously about India, or if you are in India and thinking about scaling out, Shreya is the person to know. I look forward to seeing what she builds next. Links * indianlegaltech.net * Shreya on LinkedIn * Stephenson Harwood This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit www.agents.law

    Why India is a Legal Tech Superpower
  6. Apr 26

    Lessons from 40 Years of Building Agents

    Dazza Greenwood has been building agents for longer than several legal tech founders have been alive. In the 1980s, as an undergraduate computer science student, he encountered AI assistants for the first time. His module introduced a then-new paradigm: human language, chat-based systems. The exercise was to build something modelled on ELIZA, the MIT chatbot whose therapist module ran on a simple heuristic. Find the keyword. Reflect it back to the user. When in doubt, tie it all back to the user’s parents. It was deterministic, a little absurd, and wildly popular with the people who tried it. Dazza learned some tricks and came away with a fascination with what AI was, and more importantly, what it could be. Note: Some of the concepts in this episode may be unfamiliar to some listeners. We cover them in the technical explainer at the end. What followed was a career which has spanned dozens of initiatives around the world. Let’s just say that Dazza has worn (and continues to wear) a lot of hats. Legislative aide. Candidate for office. In-house Technology Counsel to the Commonwealth of Massachusetts (which by the way he notes would be a Fortune 50 company if it were private). Standards architect. Stanford researcher. Platform builder. He went to law school, he tells me, because he kept getting different answers from different lawyers to the same question and found it unacceptable. After years of practice, he still does not have a fully satisfactory answer to “what is the law?” but he at least knows how to find the relevant law himself, which was enough to let him return to technology without feeling incomplete. He was doing legal tech, he says, before anyone called it that. Writing scripts to automate his work. Treating legal documents as data - to the extreme displeasure of colleagues who just wanted Microsoft Word (why is it always Word?) Why didn’t the standard stick? In the early 2000s, Dazza was one of the architects of LegalXML, an effort to create an international standard for marking up legal documents so they could be treated as structured data. He ran the e-contracts group. It took seven years to reach the status of a recognised international standard. It attracted a small community of who he describes as lawyer-geeks who marked up their contracts in XML, built clause libraries, and imagined a future of genuinely interoperable electronic contracting. It did not really arrive, at least not in the way the group expected. A handful of vendors adopted the standard, mostly for workflows they were already running. The broader transformation never came. The lesson Dazza draws from it is that the obstacle was never the standard. It was the culture. The love affair with Microsoft Word was not something a well-designed schema could fix. Standards, he says, have to arrive at the right moment. Too early and the industry is not ready. Too late and people have already locked into whatever is there. The good news is, the moment has now arrived, and it came from a different direction entirely. Large language models can peer into the meaning of a legal instrument and address it as data without anyone having to tag a single element. Lawyers, it turns out, are naturally good at the lingua franca of LLMs: precise language, conditional logic, sub-clauses, if-but-not-that constructions. The standard that nobody could agree on turned out to be language itself. Is your agent loyal to you? Dazza has just finished a research sprint at Stanford’s Digital Economy Lab on a project called Loyal Agents, run jointly with the Consumer Reports Innovation Lab. The question it asks is simple and the implications are not: when an AI agent conducts transactions on your behalf, what legal framework governs whether it is actually acting in your interest? His answer keeps returning to fiduciary duty, and specifically to a US federal case called Kovel that almost nobody in legal AI is talking about. Kovel itself is sixty years old. It involved an accountant working with a tax law firm whose communications with a client became the subject of a grand jury subpoena. The Second Circuit held that the privilege extended to the accountant because he was acting as the lawyer’s agent in providing legal advice. The principle that emerges, Dazza argues, applies directly to modern AI vendors. To protect attorney-client privilege when a SaaS provider is handling client communications on behalf of a lawyer, that provider needs to be the lawyer’s agent in the legal sense. Most enterprise AI contracts disclaim exactly that. Dazza has read them all. He has built a public breakdown of what each of the major frontier model providers actually says in their enterprise terms about confidentiality and agency. See Links below. The most upvoted question at Anthropic’s recent legal webinar, which drew over 20,000 registrations, was about how to handle privilege when using general purpose AI tools. Dazza thinks the profession is looking for the answer in the wrong places. The technical controls matter. Zero data retention matters. But the legal layer, the contract clause that says we are your agent, is what Kovel’s logic requires, and most providers do not offer it. His pitch to the frontier model providers is direct: stop disclaiming agency and start defining it. Write a narrow, limited agency clause. Be your client’s agent for three specific things and disclaim it for everything else. It contains risk rather than expanding it, it supports privilege, and for providers building agentic products, it simply reflects reality. If a human did what these systems do, it would be an agent. In Dazza’s opinion, the contract should say so. The platform nobody has built yet Six months ago, Dazza started building something called Interlateral. The felt need behind it is something he has observed sitting in meetings in San Francisco with startup and innovation teams where everyone has agents running quietly in the background, and then communicating with each other through the narrow human-to-human channels of Slack and email, as if the agents are not there. Interlateral is a shared collaboration space where humans and their agents can work together in the same room. You bring your agents. He brings his. There is a third space where they can interact, collaborate, and co-work, with a shared markdown surface that both humans and agents can read and write into. The design principle is human-centred: a person is always at the wheel. The agents are extended cognition, not autonomous actors. The first event ran at Stanford last week with 60 lawyers and eight teams, and the next is at MIT. Eventually, Dazza wants tens of thousands of participants. He thinks the combination of people and agents in a shared space is a genuinely new source of collective intelligence, and that we have barely started to understand what it can produce. There is a harder problem underneath it. In Google Docs or Slack, identity is straightforward. You can see who wrote what. In a space where agents are acting on behalf of humans, you now have two levels of separation from the person you think you are dealing with. Agent identity and attribution, knowing whose agent it is and holding humans accountable for what their agents do, is a bleeding-edge question the industry has not yet solved. How he builds with agents At the end of our conversation, Dazza pulls up his GitHub repo and walks me through how he actually works. The interlateral_agents repo is open source, the product of years of slow tuning, and it is more architecturally interesting than most people’s agent setups. He runs three models in parallel: Claude Code, Codex, and Gemini, with Grok CLI from xAI expected to join shortly. What makes it unusual is the communications layer. The agents share what he calls a multiplexing comms hub, a setup that lets them read each other’s outputs and write into… This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit www.agents.law

    Lessons from 40 Years of Building Agents
  7. Apr 20

    Should Law Firms Buy or Build?

    Michael Kennedy, Addleshaw Goddard Michael Kennedy left university swearing off being a lawyer. He went to work in restaurants and retail for a while, and finally came back to it as a paralegal at Addleshaw Goddard. When he started his training contract, it was very much focused on innovation and technology - a rarity at the time, and Mike was one of the first in the UK to follow this path. Since then, the innovation team at AG has grown from a handful of people to around 80 today. Fast forward to 2026, and Mike now runs the firm’s R&D function, a broad role that encompasses horizon scanning, startup engagement, partnering with clients, internal education, leading a development team, and increasingly a fair amount of building things himself. How do you project into the future? I asked Mike how anyone keeps up when the world is spinning this fast. His answer is that he doesn’t really switch off. He reads constantly, runs research agents through Claude Code, and writes a fortnightly internal newsletter for his team: three things to know, three deep dives, then a long reading list. He says it’s really important for him to know what he’s talking about. He’s not afraid to say he doesn’t know, but he doesn’t like saying it, so he’d rather know and do it. AGPT and the case for building The most visible output of Mike’s team is AGPT, the firm’s in-house AI tool. It’s one of the rare examples of a law firm having built its own in-house solution at a time when most of the industry is focused on buying legal AI. Mike describes AGPT, with characteristic understatement, as “what most people just call a wrapper”. It lives in the firm’s Microsoft Azure environment and does the usual things: chat, document review, translation, prompt libraries, citation tracking. In early 2023, Mike’s team wanted a sandbox to test whether GPT-3.5 was good enough for legal documents. They couldn’t throw client matters into ChatGPT, so they asked the developers to stand something up inside the firm. Other lawyers started asking for access. A pilot followed, then a firm-wide rollout by autumn 2023. The sandbox became the product. Today AGPT runs around 6,000 prompts a day across roughly a thousand users, and the dev team hasn’t had a quiet week since. Mike’s buy-versus-build framework is worth listening to because it comes from someone who has actually done both. Cost matters, but he frames it as a return-on-investment question rather than a sticker-price one. The real factors, he says, are: * Institutional knowledge: you can build for your specific audience in a way you can’t buy for one. A product on the market might have 70% irrelevant features and lose people before they engage, whereas a 30% solution built for your lawyers can land better. * Client consent and data: self-hosted removes a lot of friction. * Portability: which he thinks is underrated. The value is in the solution to the problem, not the tech it happens to run on. In Mike’s view, law firms are going to want to move their prompt libraries, workflows and accumulated know-how between models, and the firms that treat their intelligence as tech-agnostic will have an easier time than those locked into a single vendor. He uses a nice phrase for this: portable intelligence. Claude, vibecoding, and the artifact economy Mike and I are both heavy Claude users. He uses Claude Code primarily to build prototypes - someone in the firm has an idea, usually hard to execute, and instead of taking notes and going away for six months, Mike builds a rough version and shows it to them. One recent example is a regulatory horizon scanning tool for banks, the kind of thing his financial regs team has wanted for a long time. Not a finished product but enough to say “is this what you mean?” and have a real conversation with the Partner. On Claude for legal work itself, Mike is bullish in a way that he thinks should worry the established legal AI vendors. A lot of work inside law firms isn’t legal research. It’s factual research, web searching, document comparison, content creation, the work that fills a competition team’s afternoon. That work is dramatically easier in Claude than in Google, and Mike says Addleshaw is, for the first time, seriously considering enterprise licenses for the lawyers and teams who would benefit. Thanks for reading Agents.law! This post is public so feel free to share it. Training junior lawyers in a world with fewer trainee tasks The question that won’t go away is what happens to junior lawyer training when the grunt work disappears. He thinks training in law firms has always sort of worked by accident. Trainees are bright, engaged, hard-working people who pick things up by osmosis, sat next to a supervisor with a red pen. It’s slow, it’s inconsistent, and what you actually learn is often one individual’s approach rather than a structured body of knowledge. His proposed solution is a good one: use the firm’s data and know-how to build anonymised simulations based on real client matters. Give trainees scoring, measurement, and a structured way to develop across different areas. If AI reduces the billable work trainees do by 20%, use that time for simulated exercises rather than cutting trainee numbers by 20%. It’s an optimistic framing, and Mike knows it. The realist’s version is that firms will just fill the hours with more work and make more money, because that’s what the economic incentives reward. Side note: Mike has built a prototype for this - it’s live on my Vibecode.law platform - check it out! Final note What I take from my conversation with Mike is that there’s a particular kind of legal innovator becoming more common in the industry. They’re not pure technologists and they’re not pure lawyers. They’ve got enough technical ability to build, enough legal experience to know what matters, and enough organisational patience to sit inside a big firm and make things happen. In my view, a lot of the interesting change in BigLaw over the next few years is going to come from “intrapreneurs” like Mike, inside firms, building things and encouraging others to do so. This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit www.agents.law

    Should Law Firms Buy or Build?
  8. Apr 10

    Fiona Phillips on How to Change the Law

    When I sit down with Fiona Phillips, Anthropic has just announced that it won’t be releasing its Mythos model - at least not yet - because of the cybersecurity implications of a system that appears uniquely capable of finding and exploiting software vulnerabilities. Talk about good timing for a podcast with a leading expert on cybersecurity. But before we get to that, let’s talk about Fiona’s story, which starts a long way from cybersecurity in the restructuring and insolvency team at a Magic Circle firm, six months before Lehman Brothers collapsed. She trained at Freshfields, with a six-month stint in The Hague doing arbitration during her training contract. She qualified into restructuring and insolvency, expecting, as she puts it, “a nice quiet corporate support team where I could hide from the really vicious transactional hours.” Then Lehman went down and everything changed. She spent the next stretch of her career working for the administrators of banks and building societies, going in on day one during the most tense period in UK banking history, picking apart what had gone wrong and figuring out how to fix it. It was fascinating work, but relentless. When HSBC offered her a move in-house, she took it, partly for the quality of life and partly because the bank was so international. She wanted to travel and live abroad, and HSBC delivered on both. A secondment to Dubai that was meant to last six months turned into four years. She ended up as general counsel for the retail bank across the Middle East and North Africa, dealing with financial crime, M&A across the region, and the complex politics of the Gulf. The HSBC digital journey In 2015, Fiona moved to Hong Kong, HSBC’s spiritual home. She tells me that if you get in a taxi in Hong Kong and say “take me to the bank,” you’ll end up at HSBC. She joined the executive committee for the retail and private banks and the team embarked on a serious digital transformation. The fear at the time was fintechs. Incumbent banks were watching startups build better, faster, more intuitive products, and wondering whether the ground beneath them was about to give way. It’s a dynamic that will sound very familiar to anyone watching legal right now. HSBC’s response was to go and learn. The exco travelled to Silicon Valley, to China, to Southeast Asia, spending time with big tech companies and innovators. They recruited people from completely different industries. They experimented. They put a team in a WeWork and said: if you were going to disrupt us, what would you build? The lesson, Fiona says, was about giving people inside a big organisation different rules to play by, creating the right environment for experimentation within a business that was built for stability. As a lawyer watching all of this, she couldn’t help wondering how the same thinking might apply to the legal function. So they tried. And then Fiona became, as she puts it, “really obsessed” with legal design. Legal tech is the new fintech When we talk about what law can learn from what happened in banking, Fiona draws a sharp parallel but also flags a crucial difference. In banking, the fintechs discovered that becoming a bank is hard. Capital requirements, regulatory burden, and consumer expectations around safety and stability all acted as barriers. That’s why the big banks survived. They digitalised fast enough, and the moats held. In law, those moats may not exist. It’s much easier to become a law firm than a bank. The barriers to entry are low. And clients may not care about the stability and heritage of a big firm if they can get what they need from a tech-enabled alternative. Law, Fiona suggests, may be significantly easier to disrupt than banking was. The one thing the banking experience made crystal clear, she says, is that you have to obsess about the customer’s point of view. “You have to stop thinking that a customer wants a mortgage. They don’t want a mortgage, they want a house.” The same logic applies to law. Nobody wants a conveyancing lawyer, she says. They want a house. The legal work should be seamless, frictionless, and invisible. If AI-native firms can build that experience from scratch rather than trying to retrofit it onto traditional models, she thinks they may have a genuine structural advantage. Kill the memo This leads us to legal design, which Fiona describes simply as making sure that when you deliver a product or service to a client, it’s designed from the beginning for their needs, not yours. She gives a pointed example. She’s been drafting an AI policy for a client. Most templates she’s seen start with definitions, because they’re written by lawyers for lawyers. Nobody, she says, has ever opened a document as a normal person and thought: what I’d really like first is a dense legal definition. And most AI policies she’s seen are either aggressive or patronising in tone, full of prohibitions and warnings, when what users actually need is clear, practical guidance on a handful of questions. Can I use this tool? What data can I put in? Has the client consented? How do I check the output? She thinks the legal profession has a deep problem with this. Lawyers don’t think of what they do as a product. They think they give advice. Products feel cheap, beneath them. But if you launched a product in banking or cosmetics, you’d never release it without testing it on users first. The legal profession has, by and large, a complete absence of that kind of testing. And she’s clear-eyed about the difficulty: making something simple is deceptively hard. Lawyers see a well-designed document and think it looks easy. Actually, she says, getting to simple is a real art, and getting lawyers to respect that is one of the biggest challenges she faces. At one point in our conversation, we joke about launching KillTheMemo.com. She’s in. I think she’s only half joking. Back in private practice After years in-house, Fiona had what she describes as a reflective moment. She went and shadowed a criminal judge for a while. She’d originally wanted to be a criminal barrister and never did, and she wanted to ask herself a basic question: did she still want to be a lawyer? The answer was yes. She believes in the rule of law. She believes in the power of the law. But she also knew she wanted to be at the cutting edge of where technology was evolving, and she needed to be somewhere that the ethical dimension mattered, somewhere she could say to clients “I don’t think you should do this, even if it’s legal.” She found that at Marks and Clerk, a 130-year-old IP firm. What drew her in was the people. Patent attorneys, she points out, are the inverse of the usual dynamic: they’re technologists and scientists who became lawyers, rather than the other way around. “It’s kind of the perfect lawyer, in my view.” The firm works at the cutting edge of invention: AI patents, semiconductors, electronics, space. One of her colleagues is on the shortlist to be the UK’s first astronaut. Within Marks and Clerk, she’s built a new subsidiary focused on cybersecurity, data, AI law, governance, and ethics, with a strong emphasis on education. She describes it as a startup inside a law firm. She doesn’t think she’d have gone back to private practice for traditional transactional work. But she found a place where she can practise law in a way that makes her passionate and lets her build things. The Anthropic question The Glasswing announcement has led to a busy week. She tells me the defenders of companies and governments from cyber attacks are in a constant race with criminals, and the criminals have a structural advantage: they don’t have to comply with any law, go through compliance checks, or worry about whose data they’re using. What Anthropic has said, in essence, is that it has built a model that could be transformative for cyber defence, but devastating if it fell into the wrong hands. Fiona’s question is about who gets to set the red lines. She thinks it’s admirable that Anthropic has drawn t… This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit www.agents.law

    Fiona Phillips on How to Change the Law

About

Stories from the people reshaping legal www.agents.law

You Might Also Like