You're Not Behind

Let me tell you where I started, because it matters more than where I ended up.

I am not an engineer. I never was. I came to America from Denmark to take over my father's small woodworking company, selling sanding machines to the people who smooth rough lumber for a living. For years, that was my whole world. If you had told me then that I would one day build software that hundreds of law firms rely on, I would have laughed, brushed the sawdust off my hands, and gone back to my sanders.

But I have always had one habit I cannot shake. I like to take the cover off of things and see how they work. Machines, businesses, whole industries, it makes no difference to me. I look inside, I watch the parts move, and then I ask the question that has shaped my entire life, the one that makes comfortable people shift in their seats. Not how does this work, but how should it work, and why has no one built it that way yet?

That habit, not a degree, is the only thing that separates the people who build from the people who wait. It is the only thing this book asks of you. If you have read this far, you already have it.

I know the worry that brought you here. I have watched it cross the faces of very good lawyers for years. A colleague mentions, a little too casually, the tool that drafts his motions while he sleeps. A vendor promises to transform your firm by Friday. Someone on a stage warns that the lawyers who don't adapt will be buried by the ones who do. And underneath the noise sits a quiet fear that everyone else was let in on a secret, and you somehow missed it.

Set it down. You are not behind.

Here is the truth the salespeople will never tell you. Almost nobody has this figured out. Most of what you are hearing is noise and commission. Beneath it, a small number of people are doing quiet, useful work without making a show of it. This book is your invitation to join them, and the door sits far lower than the racket makes it sound.

The question that matters

Most lawyers are asking the wrong question about AI. The hard question is not whether to use it. That argument is over. The hard question is who holds the information when you do.

And that question is yours. Not a technologist's. You have spent a career deciding who is allowed to know what. Confidentiality, privilege, the line between a conversation you can have and one you cannot. The whole game with AI runs on that exact instinct. You are not a beginner here. You are an expert who has not yet been shown where the expertise applies.

So look at how most lawyers use this technology today. They type into a chatbot that belongs to someone else. That is fine for a retirement toast. It is the wrong instinct for a medical history, a settlement posture, the facts of a sensitive matter, because the moment you paste those words into a stranger's website, you have handed the most protected thing you keep, your client's confidence, to a machine you do not own and cannot see inside. The duty of confidentiality does not pause because the tool was convenient, and the profession now expects you to understand the tools you use well enough to protect what your client trusts you with. Most lawyers using AI have never once stopped to ask whether they do.

The unease you feel is that question, unasked. You are right to feel it. The answer is not to retreat from the tool. The answer is to be the one holding the keys.

What this book promises

By the last page, you will have set up your own private AI, running on a machine you own, sitting in your own office. You will have built, with your own hands, a small set of tools that do real work in your practice. No engineer. No IT department. No becoming someone other than the person reading this sentence.

And at one point you will switch off your internet, ask your machine a question, and watch it answer anyway, with the cord pulled and no one listening. That moment, a working intelligence that needs nothing and no one beyond your four walls, is the entire argument of this book made real. For most people, it is the moment the fear lets go.

A few honest things

Some plain talk first, because a book that only flatters you is one you should not trust with your livelihood.

AI gets things wrong. It will hand you a wrong date with the calm confidence of a man who has never once been mistaken. It will, if you let it, invent a case that does not exist and dress it in a citation so clean you would swear it was real. Lawyers have already been sanctioned for filing exactly that. So the real skill here is not which buttons to press. It is knowing when to reach for this thing and when to keep your hand at your side, and how to build it so it can never quietly do you harm. This book spends as much of its breath on that judgment as on the tools themselves. The judgment is the point. The tools are only where you practice it.

I should also tell you that I did not build my own working life by being clever once. For more than fifteen years I have worked beside plaintiff firms, six hundred of them by now, with more than two hundred and fifty million dollars in advertising run on their behalf. What I build takes the world's messy public information, the records of hailstorms and wildfires, the registries of nursing-home abuse, and turns it into something a firm can use to reach the people who need it. None of it required a computer science degree. All of it required showing up and trying the next small thing, and then the one after that. I am not telling you this to impress you. I am telling you because you need to believe the one thing that makes the rest possible. I started exactly where you are sitting, and the distance from there to here is shorter than it looks.

One last disclosure, because it would be strange to hide it. This book was written with the help of an AI. That is not a gimmick and it is not a confession. It is the whole idea, proven before you have turned ten pages: a person steering a machine toward something worth having, with a careful hand on every word. If it can be done with a book, it can be done with the small, sturdy tools your practice runs on. These pages are the first exhibit. The tools you build will be the rest, and you will not have to take my word for any of it, because you will watch them work with your own eyes.

How to read this book

The book comes in two halves, and they ask different things of you.

The first half, the one you are in now, asks only for your attention. No keyboard, no setup, nothing to buy. Read it in a chair by the window. Its job is to make the rest make sense: where your data really goes, when you are safe and when you are not, and why owning beats renting for the things that matter.

The second half asks you to sit down at a desk. There you will set up your own model first, so that everything you build afterward lives inside your own walls from its first day. Then you will build, one small tool at a time, each one teaching a single hard rule by making you live it.

The cure for feeling behind was never a better explanation. It was doing one small thing and watching it work. That is what the back half of this book is. For now, all I ask is that you keep reading.

Own your data. Own your tools. Let's begin.