The Cottner Firm · AI & Automation Assessment
Findings and recommendations from our call, in plain English.
Kyle Cottner has built an independent personal injury practice that grows almost entirely on referrals. He takes care of his clients and they tell others whenever someone they know needs help. That referral network is a compounding asset, the kind most firms spend six figures a year on marketing trying to buy. It is also the source of his next problem: every satisfied client makes the workload heavier.
The numbers tell the story. Years of 65-hour weeks, somewhere between 70 and 130 open cases at any time, and 3 to 5 new ones arriving every week, with nearly every consultation becoming a client. The service that earns those referrals still runs on Kyle personally, and the strain is landing on the two things the practice exists to protect: the deep legal work only he can do, and time at home with a young family.
The good news: the tools to fix this exist, they're affordable, and most of them he already pays for. He just needs a partner who can figure it all out, set them up in the right order, hand him the keys, and teach him as they go. That's the engagement proposed here. It starts small, making sure IP and client information is secure and a foundational repair of his Clio setup, and grows only as each step proves itself.
Your practice runs on your attention. You're carrying 70 to 130 open cases at a time, signing 3 to 5 new ones a week, and you've worked 65-hour weeks for years to keep up. The growth is the good kind of problem. Nearly everyone who sits across from you hires you. Clients have your cell number, and a few have invited you to weddings and graduations. But the machinery holding it all together is mostly you, and the strain shows in the two places you care about most.
The first is the deep work. The handful of active lawsuits, the depositions and motions only you can handle, keep sliding to nights and weekends because the days get eaten. Tom said it best: you're the brain surgeon, and you're spending the day on everything but the surgery.
The second is the one you told us you're most worried about losing: the early client contact that built the firm. "When I can have that bond, the value of the cases goes up... and now I'm struggling to kind of have it." And there's a new son at home you'd like to actually be home for.
None of this is a discipline problem. The systems that should be carrying this weight aren't carrying it yet, so you are.
Tap each one to read it in full.
A spreadsheet stays open all day while you sweep 100+ files to reassure yourself nothing is slipping. Most of that effort is defensive, re-confirming that cases already in a fine place are still fine. "It just takes a lot of effort to constantly be auditing each file... giving myself this constant reassurance, okay, this case is in a totally fine place, you can stop looking at it."
Every fax means saving the original, saving the confirmation, and scheduling the retry by hand. The same 4 or 5 letters get copy-pasted onto every case because the templates won't auto-fill. Intake gets typed by you, then re-typed into Clio by staff. Reminders are set by hand and sometimes land a month off: "instead of 6/11 it ends up on 7/11, and then the call never happens."
When the lawsuit work finally happens at 10pm, getting back into it has a price. "I'm spending 8 or 10 minutes just to find out what my last thought was and where I was going with it."
You can't fully put a file down. Partly that's because nothing tells you which 20 of the 100 actually need you today, and partly, in your own words, "I'm neurotic too... I've got to see it get done." We don't treat that as a flaw to fix. It means whatever we set up has to show its work, so you can verify with a glance instead of a re-check.
The Clio you inherited from the old partnership was templated for a different kind of law. The fields are wrong, so everything you've tried to automate on top of it stalls out. "I don't use Clio to 1% of what it can do." This leak matters more than it looks. It's the reason the letters won't merge, the reason the spreadsheet exists at all, and the reason past automation attempts went nowhere.
The encouraging finding of this assessment: most of the fix lives in Clio, Microsoft 365, and Claude, three subscriptions you already carry. The "magic elf" you described, the one that does the morning scan and reports "these five cases are ready for a demand, these five clients have appointments in three days," doesn't have to be invented. Most of it is a correctly configured Clio plus AI working over clean data.
The sequence matters more than any single tool. The foundation gets fixed first, because almost nothing else fires correctly until it is. The more ambitious builds come later, after the cheaper moves have proven what's still needed and we've learned how to work together.
Effort to stand up, against the value that comes back. Tap a dot.
| Move | Effort | Value | When |
|---|---|---|---|
| Fix the Clio foundation | Medium | Very high | Foundation, first |
| AI "Personal Trainer" | Low | High | Foundation |
| Clio Matter Stages, workflows, and a "today" board | Medium | Very high | Quick win |
| Clio Work AI | Low | High | Quick win |
| Enter intake once | Low to medium | High | Quick win |
| One-button fax-and-file | Medium to high | High | After quick wins |
| The case auditor ("magic elf") | High | Very high | After quick wins |
Most of the relief sits in the cheap, already-paid-for cluster. The two moves that carry the most weight are fixing the Clio foundation and turning on the workflows it already includes. The one genuinely ambitious thing is the case auditor, and it comes last on purpose.
These four changes are fast, they live inside tools you already pay for, and they land properly once the foundation work below is done. You know Clio and your own practice far better than we do, so some of this you may already run, or have weighed and set aside for reasons we can't see from the outside. Where that's the case, we'd rather hear your thinking than talk you into ours. Treat the list as a starting point for the call.
Turn on Clio's Matter Stages, task lists, and a "what needs me today" board. Configured to match how your cases actually move, a status change can do the next step on its own: it assigns the task to the right staffer, sets the due date, and queues the letter. The board becomes the native answer to "these 20 need you, the rest are fine." And because Clio shows what it did, you can verify with a glance. This is roughly 80% of the magic elf with no new vendor.
Ask Clio instead of scanning it. Clio's own Work AI, working over clean data, can answer "which matters are missing a demand?" in plain English, inside Clio's privacy boundary. The daily sweep becomes a question you ask when you want reassurance.
Enter intake once. Capture the consultation one time and let it flow into a Clio matter. That ends the double-entry where you type notes and staff re-types them. This was your own wish: "Clio could look at these notes and open the matter."
Close the privacy gap. You were right to ask about Claude reading SharePoint folders that might still hold an SSN. On the consumer tier that's a real exposure, and there's now a federal ruling on point. If you haven't already closed this, the fix is cheap and quick: turn off the training setting, move to a compliant tier. If you've handled it, even better, and we'd just confirm it together.
This is the keystone. We rebuild the matter template and fields so every new
personal injury case is born organized, and re-author your 4 or 5 standard letters as templates that actually auto-fill.
Every failure you described (letters that won't merge, fields that don't carry) matches what happens when the matter
template is wrong for the practice area. In fairness: certified Clio consultants
do these setups as their primary business, and you could hire one of those. We'd genuinely like to do this part ourselves,
because getting into the foundation is how we learn your practice well enough to build everything after it. But you should know the option exists.
Rather than just build things for you, we help you grow your existing
interest in using AI, so that you can use it on whatever you come up with next. We meet twice a month, go over ideas
you have and I answer any questions, we spot you, give you ideas to try and act as an accountability partner.
Part of the job is getting your setup in shape: closing the privacy gap you mentioned as a concern is one example of what we'd fix early.
You already have the instinct that matters: "the lawyers who excel over the next 10 years are the ones
who take what makes them great and embrace AI to optimize it."
These are the two places where building beats buying, because each one encodes your workflow or your judgment. We'd scope them as one or two focused Clio integrations, with a larger build only if you want to go further.
One-button fax-and-file. Press once. It sends, files the original and the confirmation in the right folder, and schedules the retry if the fax fails. No off-the-shelf product does that whole chain, so this is glue we build and maintain for you.
The case auditor, your magic elf. Each morning it reviews every open case the way you would ("treatment complete but no demand drafted, flag it") and hands you the short list, with its reasoning shown so you can trust it. This is the one build worth owning, because it bakes in your sense of what makes a case need you today. It appears there's a product, Case Status Triage AI, that does something to this effect. If that doesn't look like it'd work we can build something simple that does just what you need.
Every hour reclaimed goes to the two things you said you're losing: the lawsuit work only you can do, and the early client relationships that built the firm (and the new son at home). None of these systems touch the bond itself. That stays yours. What changes is that the defensive scanning, the copy-pasting, the double-entry, and the hand-set reminders stop coming out of your evenings, so the referral engine that's compounded for years keeps compounding without costing you the things it was supposed to pay for.
You put your own position well: "I'm not at the tip of the iceberg, I'm 100 yards out at sea, and I can see it." You're right, but the distance is shorter than it feels.
James Hollister is a father of 4 girls that he is raising with his wife in the small town of Duvall WA, just east of Redmond in the hills of the scenic PNW landscape of the Snoqualmie River valley.
He grew up in Las Vegas and fell in love with building software when he was a freshman in high school. He has been trying to solve problems for people with technology for over 20 years. Most of his early career was working with small businesses as he learned his craft and worked his way through university at UNLV. More recently he joined big tech when he moved his family to the Seattle area.
His experience with machine learning and AI is diverse. His first encounter with Large Language Models was with OpenAI's GPT 2 while working at Microsoft in 2020 within their Teams chat bot division. He then got to apply ML to predicting trucking rates while working within Uber's Freight logistics organization. More recently he moved to Amazon to help build their satellite internet offering and used machine learning to understand how to build and operate a fleet of thousands of low earth orbit satellites. He now builds agentic AI systems to help operate Amazon.com's massive fulfillment network.
As the developments within AI continue to accelerate he saw the enormous opportunity to help the millions of small and medium sized businesses adopt and adapt to this new world. Big tech no longer feels like the right place for him to make an impact. So he's hanging up a shingle and is excited to talk to anyone that is feeling left behind when it comes to AI. He hopes to build a practice doing this, similar to Kyle's, where his clients can't help but refer him to their friends.
The company he's starting is called Blue Bridge Logic. A nod to the Novelty Hill bridge he crosses every day as he leaves to commute into the city and the one which welcomes him home to the small town community he loves. That's the kind of attention he intends to bring to your practice.
The next step is a short call, about 30 minutes. We walk the plan in order and confirm the few things only you can answer: which Clio plan you're on, learn more about your faxing plan, and a quick look at one letter template so we can size the fix precisely. None of it changes the plan. It lets us put exact numbers and a real sequence in front of you.
We'd start small on purpose, with an engagement contained enough that you can feel how we work before committing to anything bigger. In addition to those fixes we could start with an AI Personal Trainer (see what you've been using it for, make sure you're set up to use AI safely, with the privacy question among the first things we get in shape). The bigger builds come later, after we've delivered good value.
Your expected investment:
The Clio rebuild: matter template, fields, and auto-fill letter templates.
01 · foundationDone with you. The safe private space plus a standing partner between calls. Two 45 min calls each month + message any time with questions.
01 · foundationWire up the Matter Stages, the "today" board, Clio Work AI, and single-entry intake, and train your staff.
02 · quick winsAround $1,000 to $3,000 for a focused integration and $3,000 to $5,000 for a larger one, with final scope and price confirmed together on the call.
03 · custom buildsNothing here is a commitment today. The call is where we walk through it, confirm the open details, and you decide what to check the box on.