Episode Summary
Executive Summary: Dave Berner, co-founder and CTO of Parachute, explains how the company is building an AI-native operating system for small and mid-sized law firms in Australia. The discussion covers lean product development, legal-domain expertise, customer-led roadmap decisions, scaling challenges around token usage and document processing, a costly production issue with Australian-hosted AI inference, and Parachute’s future around client-facing legal workflows.
Main Topics: Building Parachute for SME law firms (Priority: 5/5): Parachute targets law firms with 1 to 200 lawyers, aiming to automate the first 80% of legal work: drafting, document review, advising, note-taking, and email intake across the matter lifecycle. Lean AI-native product development (Priority: 5/5): The team deliberately stayed small and used AI tools plus third-party services to move quickly, balancing speed with trade-offs in compliance and control. Roadmap driven by legal expertise and customer discovery (Priority: 4/5): Three co-founders and several lawyer-team members provide direct legal domain knowledge, while in-person events and customer conversations shape product priorities. Scaling and throughput constraints (Priority: 4/5): Scaling concerns center less on user count and more on token usage, heavy document ingestion, OCR workloads, and unexpected load from solo practitioners handling very large files. Production mistake with Australian AI inference (Priority: 5/5): An early attempt to keep AI inference in Australia led to degraded model output and throughput issues in production, causing the loss of a major pilot and prompting a slower rollout approach. Future of AI-native legal services (Priority: 4/5): Parachute is extending toward lawyer-client collaboration, enabling firms to offer clients a grounded AI workflow that shares full context rather than raw AI output. Founder mindset and startup advice (Priority: 3/5): Dave emphasizes that distribution and selling are harder than building, and advises founders to publicly commit to launch dates to force execution.
Key Arguments: Parachute is designed specifically for smaller law firms, not enterprise megafirms, because SMB/boutique firms need legal AI tools aligned to their workflows and budgets. Keeping the team lean was a deliberate choice after a modest raise, so the company relies on AI coding tools and third-party infrastructure rather than building everything in-house. Hiring prioritizes people who are open to AI-native development, since some experienced engineers reject the tooling as mere autocomplete or refuse to adopt it. Roadmap decisions are best made by combining internal lawyer expertise with direct customer feedback gathered through recurring in-person events. The biggest technical scaling issue is not user volume alone but token costs, OCR-heavy document uploads, and occasional power users who submit extremely large matter files. Moving AI inference to Australian-hosted endpoints seemed strategically aligned but failed in production due to worse output quality and restricted throughput, showing that local hosting trade-offs can be real. The product’s future is about redirecting users toward a lawyer-grounded workflow that preserves context and makes it easier for firms to monetize ongoing client collaboration. In startups, shipping and go-to-market matter more than perfect code; founders should commit publicly to a date to force momentum.
Data Points: Initial raise: 1.8 million AUD - Small raise completed just before Christmas to fund a lean build strategy Target customer segment: 1 to 200 lawyers - Parachute is aimed at SME law firms rather than large enterprises Typical sweet spot firm size: 25 to 50 person law firm - Primary B2B market segment discussed for the product Team size: 2.5 engineers - Dave described the engineering team as very small, with himself contributing about half an engineer Pilot/customer timeline: Within six months - Parachute moved from starting up to running pilots and pitching alongside major incumbents Event attendance: 40 to 50 law firms - In-person education/customer discovery events in Sydney, Brisbane, and Melbourne Document size issue: 10,000-page documents - Early customers sometimes uploaded extremely large PDFs that stressed OCR and throughput Model hosting strategy: Australian-hosted inference - The team attempted to keep AI inference in Australia to align with their local-market positioning
Pivotal Quotes: "We handle that first 80% of legal work, so drafting, document review, advising." — Dave Berner: Describing Parachute’s core product value proposition "The confidence that we got from being told by the providers it's going to be fine and testing it in those environments probably should have rolled it out slower." — Dave Berner: Reflecting on the failed Australian inference rollout "Coding and building the product was never really the hardest part of it all; it's always been taking it to market and selling it and actually getting people to engage in what you've built." — Dave Berner: Advice to younger founders about what matters most in startups
Implications: Parachute’s story shows that AI legal startups win by combining domain expertise, lean execution, and careful rollout discipline. For the industry, local compliance goals must be balanced against model quality and reliability, especially when serving real customers in production.
About Code Story
Code Story is a podcast featuring startup founders, tech leaders, CTO's, CEO's, and software architects, reflecting on their human story in creating world changing innovation, disruptive digital products. Their tech. Their products. Their stories.