Show Notes
Daniel Taylor runs a criminal and child protection law firm in Victoria, Australia, handling 800+ clients a year. When every client is in crisis and needs to be heard, there's no room for admin overhead or missed details.
In this episode, Daniel shares his journey from paper files and mega spreadsheets to a fully systematized Notion workspace that's evolved over 6+ years with consultant Tim Jeffries and Jerwin Parker.
We explore: From Paper to Digital: How Daniel discovered Notion through a fellow law firm owner The challenge of moving from Google Drive + spreadsheets to one source of truth Change management: navigating the cycle of denial, anger, bargaining, and acceptance with staff
AI Transcription as a Game-Changer: Why clients come to lawyers to be heard, not lectured Using live transcription to stay fully present in client conversations Drafting letters that reflect clients' own words back to them ("98% done" from the transcript)
The Next Frontier: Custom Agents: Automated file audits that catch billing gaps and missing documents Intake and outtake processes that run in the background when you're too busy Training junior lawyers through AI feedback on client interview transcripts
Three Actionable Takeaways: AI lets you be more human, not less. Transcription handles admin so you can focus on listening. The client's words land better than yours. Draft from transcripts using their language. Agents will catch the stuff that falls off when you're busy. Automate the tasks that should happen but don't.
🎁 Free Resource from This Episode 📞Call Review Playbook — Your Free Gift Daniel's workflow for using AI to review call transcripts inspired us to create a ready-to-use playbook you can adapt for your business. ✅ A structured framework for defining your own review criteria ✅ Three different approaches to developing criteria ✅ AI-ready instructions that turn transcripts into actionable coaching feedback ✅ Real examples across different contexts (sales, support, consulting) Link: https://www.notioninpractice.com/Call-Review-Playbook-Setup-Guide-2fbdbd5e653480898b60d4adc27db738?source=copy_link
Show Notes
Resources Mentioned: Guest: Daniel Taylor Criminal and child protection law firm owner, Victoria, Australia
Subscribe to Notion in Practice: 🎵 Spotify • Apple Podcasts • YouTube Contact: 💼 LinkedIn 🌐 www.notioninpractice.com 🪄[email protected]
More from Notion in Practice
Flight Centre Travel Group's Matt Upton explains how his automation team uses Notion, Notion Workers and Notion AI skills at enterprise scale, and why nothing gets automated until the process behind it is fixed. Matt is Head of Automation and Innovation for Flight Centre's Asia Pacific corporate brands, leading a team of around 30 across five brands from India and the Middle East to Japan, Australia and New Zealand. Inside a 12,500-person business, the work ranges from multi-step customer onboarding automations to five-minute tasks done 500 times a day. He joins Tim Jeffries and Jerwin Parker on Notion in Practice to walk through how his part of the business made Notion its single source of truth. Information used to be spread across Confluence, Azure DevOps, SharePoint, OneDrive and local files, and nothing joined up. Flight Centre's corporate technology teams now have roughly 1,000 Notion seats. "I tell people if it's not in Notion, it doesn't exist," Matt says, and that rule is what made the change stick. Who this is for Operations, automation and technology leaders fitting Notion, Workers and Notion AI into an existing enterprise stack, and smaller teams who want the same discipline without the headcount. Why can't you automate a bad process? Because automation speeds up whatever process it runs on. Matt's team won't automate anything until it has been through a continuous improvement pass. As Tim puts it, automating a bad process just makes the chaos go faster and the mess grow quicker. How did Notion take hold at Flight Centre? Microsoft Loop opened the door. Notion had been in the business for years with only a handful of real users, and once teams saw collaborative documents working in Loop, a few people pointed out that Notion already did this at scale. How does Matt's team sync Smartsheet and Azure DevOps with Notion? With Notion Workers, small pieces of code deployed to Notion. Matt has seven or eight Smartsheets plus Azure DevOps syncing into Notion databases this way, set up in a short conversation with a coding tool and left to run without babysitting. Most Workers do one plain job like this. How do you build a Notion Worker? Start with a brief. Tim gets clear on the problem with Notion AI, then hands the brief and the Worker docs to Claude Code. His Worker was deployed and working within an hour. Do you have to migrate everything into Notion? No. Smartsheet and Azure DevOps stay where they are as the data layer, Notion becomes the context and reporting layer on top, and Workers keep the two in sync. The episode also covers Notion as "the Switzerland of AI", connecting different models and tools. Three actionable takeaways Run a continuous improvement pass before you automate anything. Leave your system of record where it is and use Notion Workers to sync the data into Notion. Start every Worker with a brief from Notion AI, then point a coding tool at the brief and the Worker docs. Resources mentioned Tim's article "You already have a digital operating system": https://smoothopsconsulting.substack.com/p/you-already-have-a-digital-operating
AI doesn't run in a vacuum. It runs inside a world: the platforms your work lives on, the records that hold the truth, the rules about what happens next. Most AI disappointment isn't a model problem. It's that there was never a world built around it.
Tokens don't grow on trees. So what are you actually paying for when you pay for AI agents?
In Episode 9 of Notion in Practice, Tim Jeffries and Jerwin Parker tackle the question on every Notion power user's mind: what will custom agents actually cost and is it worth it?
What happens when a former lawyer becomes Head of Operations at a scaling startup and decides to build an entire ops function using Notion agents?