Before the Problem: What It Actually Costs to Call Your Attorney First

Two business owners. Same size company, same industry, same month. One called me before signing. One called me after something broke.

I want to walk you through what that difference actually looked like — not as a lesson, just as the math.

I spent fifteen years in litigation before I built the kind of practice I have now, and one thing I learned standing in a courtroom is this: by the time a dispute gets to me as litigation, the decision that mattered already happened. Usually months, sometimes years, before anyone called a lawyer at all. This post is about that earlier moment — the one that's easy to skip.

The math nobody runs until they have to

Preventive counsel gets measured in thousands. A contract review. An employment policy audit. A thirty-minute call before you sign something. Litigation gets measured in hundreds of thousands — discovery, depositions, months of distraction, and an outcome nobody can guarantee going in.

I don't say that to scare anyone. I say it because most business owners never actually run the comparison. They see the cost of prevention up front — it's a bill, it's tangible — and they don't see the cost of not doing it, because that cost is invisible until the day it isn't.

Wisconsin commercial disputes back this up. In one real case I've seen referenced, a company defending a real estate and contract dispute here in Wisconsin ran up right around a million dollars in legal fees over roughly two years — and that's just the fees, not the time, the stress, or the deal that didn't happen while everyone was occupied with a lawsuit. Compare that to what a document review or a policy check costs on the front end, and the math stops being close.

The client who called first

A Wisconsin business owner came to me before finalizing an employment agreement — specifically the non-compete language for a departing employee who was about to start a competing venture. Wisconsin law on this is genuinely strict. A restrictive covenant here has to clear five separate tests — it has to protect a real business interest, use a reasonable time limit, use a reasonable geographic limit, avoid being harsh on the employee, and hold up against public policy. Miss any one of those five, and the whole covenant gets thrown out — not just the part that goes too far.

We caught two of those problems before the agreement ever got signed. One quiet conversation, one redraft, done. No dispute ever happened, because there was nothing left to dispute.

The client who called after

Same category of problem, different order of operations. Another Wisconsin business had already signed a similar agreement — drafted without anyone checking it against the five-factor standard — and the day came when they tried to enforce it against a former employee. The whole covenant got struck. Not narrowed, not softened. Gone. Because Wisconsin courts don't get to save the reasonable parts of an unreasonable agreement — the statute doesn't allow it.

What could have been a five-minute read on the front end became a real dispute with real legal fees and zero enforceable protection at the end of it. Same starting point. Different timing. Completely different outcome.

The contract that looked fine until it wasn't

This is where the litigation background actually changes how I work — not as a talking point, as a practical difference. When I review an operating agreement or a vendor contract, I'm not just checking that the language is clean. I'm reading it the way I'd read it in discovery, because I've been the attorney standing in front of a judge trying to make an ambiguous clause say what my client needed it to say.

Wisconsin's LLC statute fills in a lot of gaps when an operating agreement is silent — how a member dissociates, what happens to fiduciary duties, what the default rules are when the document doesn't say. Some of those defaults protect you. Some of them don't, and you don't find out which until there's a disagreement between partners and everyone's pulling out the agreement to see who's right. An attorney who's only ever drafted agreements reads for clarity. An attorney who's litigated them reads for what happens when two reasonable people disagree about what the words mean. That's the difference litigation experience actually makes — not a credential on a bio page, a different lens on the document in front of you.

What "calling first" actually looks like

This is probably the part people misunderstand most about having outside general counsel. It's not a retainer that sits there unused until a crisis. It's a five-minute call before you sign the vendor contract. A quick question before you finalize a hire. A "does this structure hold up" conversation before the deal closes.

None of that feels dramatic in the moment. That's the point. The businesses that avoid the expensive version of this story aren't the ones with the most legal budget — they're the ones with one person who already knows their business well enough to catch the small thing before it becomes the big thing.

The question worth asking right now

I'm not going to tell you something's wrong with your legal setup. I don't know that, and I'm not interested in scaring anyone into a phone call.

But here's a fair question to sit with: when did you last actually look at your operating agreement? Not skim it — read it, the way you'd read it if a partner disagreed with you tomorrow. And do you have one attorney who knows your business well enough to answer that kind of question in five minutes, or do you have someone you call only when something's already broken?

If this sounds like what you've been missing, reach out directly and we'll find a time to talk.