What My JD/MBA Taught Me About Building Companies

Two Degrees, One Operating System

I earned my JD from the University of Baltimore School of Law and my MBA from Duke's Fuqua School of Business. At the time, pursuing both felt like hedging my bets — a way of keeping doors open in a career that hadn't yet defined itself. What I didn't fully appreciate until years later was that these two degrees weren't parallel paths. They were, in fact, complementary cognitive frameworks that would eventually fuse into a single operating system for building companies.

Thirty-plus years across Wall Street, enterprise SaaS, healthcare technology, fintech, and AI have tested that operating system repeatedly. It has held up — not because a JD and MBA make you smarter, but because they train you to ask fundamentally different questions about the same problem. And in company building, the quality of your questions almost always determines the quality of your outcomes.

What Legal Training Actually Teaches You

Most people assume law school is about learning the law. It isn't — or at least, that's not the part that matters most. What a legal education actually instills is a systematic obsession with downside protection: the habit of stress-testing every structure, every agreement, and every assumption before you commit to it.

Lawyers are trained to read every contract looking for the clause that will eventually be litigated. They model the adversarial scenario before the friendly one. They ask, "What does this look like when the relationship breaks down?" before asking, "What does this look like when everything goes right?" That instinct is invaluable in company building, where most catastrophic failures aren't caused by bad strategy — they're caused by unforced structural errors that nobody thought to scrutinize.

Early in my career, I watched companies implode not because their market thesis was wrong, but because of preventable mistakes:

• Founders who hadn't properly vested equity, triggering ownership disputes the moment a co-founder departed
• Enterprise SaaS deals structured without data processing agreements that later created HIPAA exposure
• Capital raises closed without anti-dilution provisions that eviscerated founder economics in the next round
• AI companies building on third-party model APIs without understanding the IP and data ownership implications buried in the terms of service

None of these are sophisticated legal problems. They are basic structural errors that legal training teaches you to catch before they become existential. At HedgeNova, where we are building AI infrastructure at the intersection of financial services and machine learning, regulatory structure isn't an afterthought — it is built into the architecture from day one. That doesn't happen by accident. It happens because the person designing the company has spent years thinking like a lawyer.

"The most expensive legal advice you'll ever receive is the advice you needed six months ago but didn't ask for."

What Business School Actually Teaches You

If law school trains you to protect downside, business school trains you to manufacture upside. An MBA — particularly one anchored in rigorous strategy and finance, as Fuqua's program is — forces you to think about markets, capital allocation, competitive positioning, and growth mechanics in a structured, disciplined way.

The core habit an MBA builds is the ability to evaluate opportunity cost with clarity. Every dollar of capital, every hour of engineering time, every enterprise relationship has an alternative use. Business school teaches you to make those tradeoffs explicitly rather than by default. That discipline is rare in founders, many of whom operate on intuition and momentum — which works until it doesn't.

The MBA lens also shapes how I think about sales and revenue architecture. As a Chief Revenue Officer across multiple SaaS organizations, I've led go-to-market transformations that required simultaneously redesigning incentive structures, repricing contracts, rebuilding channel strategy, and aligning product roadmap to revenue outcomes. That kind of systems-level revenue thinking doesn't come from hustle — it comes from understanding how the financial model, the market structure, and the customer acquisition motion interact with each other.

Where the Two Frameworks Collide — and Why That's the Point

The honest tension between a legal mindset and a business mindset is that lawyers instinctively pump the brakes while operators instinctively press the accelerator. In a single person, those impulses can create productive friction — or they can create paralysis. Learning to manage that tension is, I would argue, one of the most underrated skills in company building.

At VoyagerMed, where we were operating at the intersection of healthcare logistics and technology, that tension was constant. The business opportunity demanded speed — faster market entry, faster contracting, faster partnership development. The legal and regulatory environment demanded precision — HIPAA compliance, provider credentialing, liability allocation in clinical settings. Neither instinct alone would have built a viable company. It required holding both simultaneously and making judgment calls about when each lens should take priority.

That's the real value of the JD/MBA combination — not the credentials themselves, but the forced fluency in two distinct modes of professional reasoning. Most founders are naturally wired toward one or the other. The growth-obsessed operator who never thinks about structure will eventually step into a hole they didn't see coming. The risk-averse lawyer who never stops analyzing will miss the market window while modeling every scenario.

What I Would Tell a Founder Considering Either Degree

I'm not here to argue that every founder needs formal legal or business education. Many of the best builders I know have neither. What I am arguing is that the thinking habits these programs develop are non-negotiable if you want to build something durable at scale.

You need to understand how legal structure creates or destroys optionality. You need to understand how capital efficiency and market positioning interact. You need to be able to read a term sheet, evaluate a market, structure an enterprise deal, and anticipate the regulatory environment your company is entering — all before you've hired the relevant specialists.

If you get those degrees, treat them as frameworks, not credentials. The certificate on your wall is irrelevant. The way you reason through a problem under pressure — that's what compounds over a career.

Looking back across three decades of building companies, closing enterprise deals, raising capital, navigating regulatory environments, and launching AI platforms, the single most durable competitive advantage I've carried isn't a specific technical skill or domain expertise. It's the ability to simultaneously ask, "How do we capture this opportunity?" and "How do we make sure it doesn't destroy us in the process?"

That's what a JD and an MBA taught me. Everything else was just experience.