By Asaf Fulks, Esq.
I spent over twenty years running a recording studio before I became an attorney. Since passing the bar, I’ve practiced across a range that most lawyers never touch — lemon law, products liability, personal injury defense, insurance coverage, construction defect litigation, entertainment law, and intellectual property. I’ve handled Song-Beverly warranty cases against automakers, defended premises liability claims, and managed multi-party construction disputes with layered insurance towers. I’ve drafted wills and trusts, advised on wealth management, and put my two decades of music industry experience to work on IP and entertainment matters.
I’ve worked cases at every stage — pre-litigation demands, early litigation strategy, written discovery, depositions, motions, mediations, and trial. I’ve filed in small claims and state superior courts, and handled copyright, trademark, and patent matters from the transactional side. Every practice area had different demands. Every stage had different workflows. And every one of them used the same generic software that couldn’t keep up with any of it.
So I started building my own.
The Problem Nobody Talks About
Every legal case management platform on the market was built by software companies. That’s not a knock — it’s just a fact. And that fact shows up in the product every single day.
When I open a construction defect case, I need fields for Privette doctrine analysis, SB 800 notice compliance, indemnity tracking between general contractors and subcontractors, and multi-layer insurance coverage mapping. When I open a personal injury defense file, I need lien tracking, medical chronologies with treating physician hierarchies, and IME scheduling workflows. When I switch to a lemon law case, I need Song-Beverly warranty tracking, repair attempt logs, and mileage offset calculations.
What does the typical platform give me? A blank text field and a calendar.
That’s not case management. That’s a filing cabinet with a subscription fee.
The tools most attorneys use weren’t designed by people who have actually managed a case from intake to verdict. They were designed by people who interviewed attorneys, synthesized the feedback into a product requirements document, and built something generic enough to sell to everyone. The result is software that technically works for all practice areas but doesn’t truly serve any of them.
What I Wanted to Exist
I wanted a system that understood that a maritime injury case and a trade secret misappropriation case have almost nothing in common — and that the software should reflect that reality. I wanted practice-area-specific data capture across every type of case a firm might handle, not a one-size-fits-all form with custom fields bolted on as an afterthought.
I wanted deadline calculations that actually knew the rules. Not just “add 30 days to this date.” I’m talking about a system with jurisdiction-specific court rules for all fifty states and D.C. — a system that understands the difference between California’s CCP deadlines and New York’s CPLR timelines, that accounts for court holidays and local rules, and that flags hard deadlines versus soft ones without me having to think about it.
I wanted a legal reference library built into the platform — not a separate tab, not a Google search, not a prayer that I remembered the right statute number. I’m talking about thousands of verified legal references with working URLs, covering everything from general civil procedure through specialized areas like bankruptcy, immigration, healthcare compliance, and intellectual property.
And more than anything, I wanted AI integration that didn’t require me to send my clients’ privileged information to someone else’s server.
So I Built It
CaseDesk™ is the result — a personal project years in the making. It covers over 105 practice areas with specialized data capture for each one. It has over 7,000 verified legal reference entries with live URLs spanning all U.S. jurisdictions. It generates documents from over 400 templates with dynamic field population. It handles IOLTA trust accounting that meets State Bar compliance requirements. And it runs entirely offline.
That last part matters more than most people realize.
The AI Question
Everyone in legal tech is racing to add AI. Most of them are doing it by piping your case data to a cloud API and hoping their terms of service are good enough to protect attorney-client privilege. I wasn’t comfortable with that approach.
CaseDesk runs its AI assistant locally on the attorney’s own hardware. No API keys. No cloud inference. No data leaving the machine. The language model runs directly on the attorney’s GPU, and the system injects real case context — active cases, upcoming deadlines, recent communications, settlement activity — directly into the conversation. When the AI answers a question about your caseload, it’s referencing your actual data, not hallucinating case numbers.
And because legal AI hallucination isn’t just embarrassing — it’s potentially sanctionable — the system is engineered from the ground up to stay grounded in the data it can actually see.
For attorneys who prefer to use a cloud-based model they already trust — whether that’s Claude, GPT, or another provider — CaseDesk will also support optional API integration. The choice stays with the attorney, not the platform.
Why This Matters for the Industry
I’m not writing this to sell software. CaseDesk isn’t on the market yet. I’m writing this because I think the legal technology industry has a fundamental design problem, and I don’t see enough attorneys talking about it.
The problem is this: the people building legal software don’t practice law, and the people practicing law don’t build software. That gap produces tools that look impressive in a demo and feel frustrating in daily use. Features get prioritized based on what sells, not what actually reduces the cognitive load of managing a complex case docket.
When an attorney is monitoring excess coverage on a construction injury case with a $25 million exposure, they don’t need a prettier dashboard. They need a system that understands what monitoring counsel does — that tracks carrier reporting deadlines, flags reservation of rights issues, maps the coverage tower, and surfaces the information that matters without requiring twelve clicks to get there.
That kind of depth doesn’t come from user surveys. It comes from doing the work.
What’s Next
CaseDesk is in active development. There’s a long road between a working desktop application and a product that other attorneys can rely on in their practices. I’m focused on getting that right — stability, polish, and the kind of reliability that a legal tool demands — before I focus on distribution.
If you’re an attorney who’s felt the same frustrations I have, or if you’re interested in the intersection of legal practice and technology, I’d love to hear from you. You can reach me through this site or connect with me on LinkedIn.
The tools we use should be as sophisticated as the work we do. It’s time they caught up.
Asaf Fulks is an associate attorney in California specializing in insurance defense, construction defect litigation, personal injury defense and intellectual property. He is also a software developer and the creator of CaseDesk. He can be reached at asaf@asaffulkslaw.com.