The Habit You Can’t Afford: Calling Outside Counsel for Routine Contracts

This article was originally featured in Today's General Counsel.

Here is what the outside counsel reflex actually costs: an associate at a top firm billing $600 an hour to review a non-disclosure agreement (NDA) that your team could have handled. Weeks added to a routine vendor agreement because nobody had a playbook for that jurisdiction. A deal that should have closed last quarter still sitting in legal.

Most in-house legal teams have not updated their review infrastructure to match the scope of the business they support. Your company operates across dozens of markets. Your sales team closes enterprise contracts with counterparties whose legal systems look nothing like the ones your playbooks were built for. And every time a contract arrives that falls outside your established framework, the default answer is the same: escalate to outside counsel.

That default is a choice. And it is an expensive one.

The infrastructure gap no one talks about

The conversation about AI in legal has focused heavily on efficiency: how much faster you review a contract, how many issues you catch. That’s the right conversation. But it misses a more fundamental problem.

Most legal review tools and frameworks were built for United States legal contexts. They perform well on agreements governed by familiar common-law concepts, written in English by counterparties in the same legal tradition. Outside of that context, their utility drops sharply—and so does the in-house team’s confidence in using them.

The result is a two-tier legal operation: fast, structured review for the agreements that fit the mold, and expensive, slow escalation for everything else. In-house teams haven’t solved the second tier. They’ve just accepted it.

What it actually takes to review contracts across legal systems

Two things break down when a contract operates under an unfamiliar legal system.

The first is language. A contract drafted in Japanese, German, or Portuguese cannot be reviewed effectively by someone who doesn’t read it. Generic translation tools can render the words in English, but they don’t preserve clause structure and have no understanding of the legal significance of the terminology they’re converting. When redlines go back to the counterparty, the translation needs to reflect precisely what you negotiated. General-purpose tools cannot guarantee that.

The second is standards. Even with a clean translation, the team still needs to know what market-standard looks like in that jurisdiction. What indemnification language is typical in a German Master Services Agreement (MSA)? Without guidance grounded in local legal practice, your team is reviewing against an invisible benchmark.

Outside counsel solves both problems, but it also charges you for the privilege, introduces coordination overhead, and removes the deal from the team’s direct control. That tradeoff made sense when there was no alternative. That’s no longer the case.

The teams carrying the most risk

The outside-counsel reflex is most expensive for teams already under pressure:

• In-house legal teams receiving contracts from counterparties operating under legal systems their playbooks don't cover.
• Legal ops teams trying to standardize review across multiple jurisdictions without scaling headcount.
• Companies entering new markets that need jurisdiction-specific NDA and MSA frameworks immediately.
• Legal teams post-acquisition who suddenly own agreements governed by law they didn’t negotiate and have no institutional framework to evaluate.
• Procurement and supply chain functions managing vendor agreements across dispersed supplier bases with no consistent review standard.

In each case, the root cause is the same: review infrastructure that was built for one legal context and never updated to reflect how the business actually operates.

What good infrastructure looks like

Solving this does not require eliminating outside counsel. It requires being intentional about when outside counsel is actually necessary and building the internal capability to handle everything that is not. Here is how to do that in practice.

1. Start with a contract inventory and an honest gap assessment. Audit the last 12 months of outside counsel spend and identify the contract types and jurisdictions that drove the most escalations. In most organizations, a small number of contract categories—NDAs, MSAs, vendor agreements—account for the majority of routine escalations. Those are your highest-priority targets for building internal capability.
2. Build jurisdiction-specific playbooks for your highest-volume contract types. Generic playbooks do not work across legal systems. For each high-volume contract type and jurisdiction combination, develop a structured review guide that answers three questions: what does market-standard look like here, what clauses require particular attention under local law, and what are the acceptable fallback positions your team is authorized to take. Develop these with input from lawyers who have actual local expertise. Once built, they become repeatable infrastructure that the team can use without escalating.
3. Implement translation workflows built for legal documents. If your team is reviewing contracts drafted in other languages, general-purpose translation tools aren’t sufficient. You need workflows that preserve clause structure, maintain terminological consistency across drafts, and flag where translation introduces ambiguity that could affect legal interpretation. When redlines go back to the counterparty, both sides need to be working from the same understanding of what was negotiated. Build or adopt translation processes designed specifically for legal documents and make them part of the standard review workflow.
4. Define clear escalation criteria and enforce them. Write down, explicitly, what should and should not go to outside counsel. If the criteria don’t exist or aren’t enforced, escalation becomes a habit rather than a decision. Criteria should be contract-type specific—an NDA in an unfamiliar jurisdiction is a different question than a complex acquisition agreement—and should distinguish between situations where outside counsel adds genuine value and where the team simply hasn’t built the right framework yet.
5. Make the infrastructure accessible to the people doing the work. Playbooks, review standards, and escalation criteria only reduce outside counsel spend if the team can actually find and use them when a contract arrives. That means building these resources into the workflow, integrated with the tools the team uses, not stored in a shared drive that nobody remembers to check. The goal is to make the right answer the path of least resistance.

Outside counsel has a role. Complex transactions, novel legal questions, high-stakes disputes—that is where specialist judgment earns its fee. A standard vendor MSA from a counterparty based in Germany is not that.

The in-house teams treating every out-of-framework contract as a reason to escalate are not being cautious. They are operating with infrastructure that has not kept pace with the business they support. The cost of that gap is already showing up in billing statements, delayed deals, and legal teams that are too stretched to do the work that actually matters.

The tools and frameworks exist. How much longer can you wait?

Learn more at legalontech.com or schedule a demo.