The question of when to build an in-house legal function comes up at a predictable moment in a company's life: when the outside counsel bills get high enough that someone does the math and asks whether a salaried attorney would be cheaper. That math is usually the wrong starting point, but it's where most of these conversations begin.
There's a more useful question: what kind of legal work does your company actually need, and is that work primarily transactional volume (contracts, vendor agreements, employment documents) or primarily strategic and situational (M&A, financing, regulatory, litigation)? The answer changes the hiring decision significantly.
Outside Counsel vs. In-House: The Real Tradeoff
Outside counsel makes sense for work that is situational, high-stakes, and requires deep specialization. M&A due diligence on an acquisition target. A securities offering. Litigation in a specialized area. These are things where you need domain expertise that it doesn't make economic sense to employ full-time.
Outside counsel gets expensive — and adds meaningful delay — for work that is transactional, repetitive, and requires company-specific context more than domain specialization. Reviewing the vendor NDA your procurement team needs signed by Friday. Updating the employment agreement template when headcount policy changes. Reviewing a SaaS subscription before the sales team closes the deal. These are things where an in-house attorney with institutional context is faster, cheaper, and often more effective than outside counsel who has to rebuild context on each request.
The signal that you need in-house legal help isn't total outside counsel spend — it's the percentage of that spend going to transactional volume work versus strategic situational work. If more than 40-50% of outside counsel time in a given month went to document review, template updates, and routine contract negotiations, you have a case for in-house capacity. If 80% went to a financing round, you probably don't — that was a one-time event.
The Contract Workflow Problem Before You Have a Legal Team
Most growing companies have a legal workflow problem before they have the headcount to solve it properly. The CEO or a senior business person is personally reviewing contracts. Or outside counsel is reviewing everything, at hourly rates, with the turnaround time that implies. Or — and this is more common than most companies admit — contracts are getting signed without careful legal review because the turnaround problem has made the review process a bottleneck that gets bypassed under deal pressure.
Before you hire a general counsel, a useful intermediate step is to build the minimum infrastructure that a GC will need anyway: a contract repository, a standard template library, and a document for what your company's standard positions are on key clauses (limitation of liability caps, IP ownership, payment terms, auto-renewal notice windows). This doesn't require a lawyer to build — it requires someone to systematically collect what your company has agreed to in the past and make it retrievable.
The companies that hire their first GC into chaos — no contract repository, no standard templates, no institutional memory of past agreements — waste a lot of that GC's first six months on archaeology. The companies that hire into a reasonably organized base of information let the GC focus on improving the process and handling new work, not reconstructing the past.
Who Should Your First Legal Hire Be?
This is a topic with strong opinions and no universal right answer. A few frameworks worth considering:
If your legal workload is primarily commercial contracts: A commercial transactions attorney with 5-8 years of BigLaw or mid-market firm experience handling M&A, private equity, or commercial agreements is often the best fit. They've seen a wide range of contract structures, know market terms, and can build a playbook quickly. They may not have done in-house work before, which means they'll need to adapt to operating without the support infrastructure of a firm — but their substantive knowledge will be immediately useful.
If you're in a regulated industry (healthcare, fintech, biotech): Your first legal hire should have regulatory experience in your specific vertical, even if that means some trade-off on commercial transactions depth. A general commercial attorney learning healthcare privacy law on the job is a real risk. A healthcare privacy attorney learning to review vendor contracts on the job is a more manageable one.
If you're growing fast and expect an M&A exit within 3-5 years: Consider hiring someone who has done M&A work specifically, not just someone who will be adequate for day-to-day and can be replaced when the transaction happens. The institutional knowledge a GC builds about your company's contracts, liabilities, and representations becomes critical in a transaction. A GC who hasn't been through a deal process will be less effective in it than a replacement brought in mid-transaction who doesn't know your company.
Building the Contract Workflow Function
The contract workflow question — who reviews what, what can be approved without legal review, what requires escalation — is one of the first things a new GC will want to establish. Getting some structure here early, even before you have legal headcount, reduces the workload a new GC inherits.
A practical tiering approach that works for early-stage companies:
Tier 1 — Standard, self-serve: Contracts from your own templates, used as-is without counterparty redlines, below a threshold deal value (say, $10K for an early-stage company). Business team can sign without legal review. This requires having good templates in the first place.
Tier 2 — Legal light-touch required: Counterparty paper below threshold deal value, or your paper with moderate redlines on non-material terms. 24-hour turnaround expectation, review should take 30-60 minutes. In-house counsel or a designated reviewer.
Tier 3 — Full legal review: Above threshold deal value, non-standard structure, liability exposure, or any contract in a regulated area. No turnaround SLA commitment — timeline depends on complexity. Legal counsel plus business stakeholder alignment before signing.
The thresholds are company-specific and should be set by the GC or outside counsel advising on the program, not by business stakeholders. Business stakeholders will naturally want thresholds set high (to reduce friction). Legal counsel will set them lower. The right answer is somewhere in the middle, calibrated to actual risk tolerance, and it will shift upward as your templates and playbooks get better.
Tools Before You Have Headcount
We're not going to pretend to be objective here — Winpathio is a contract review tool, and we think it's useful. But the real point is more general: contract review tools and contract lifecycle management (CLM) platforms have become accessible to companies that aren't enterprise-scale. If you're reviewing 20-40 contracts per month without dedicated legal staff, a tool that extracts key terms, flags non-standard clauses, and maintains a repository of what's been signed is a more tractable investment than hiring immediately.
We're not saying tools replace in-house counsel. A tool can tell you the liability cap is 1x fees; it can't tell you whether 1x fees is acceptable given the nature of the relationship, your insurance coverage, and your risk posture. That judgment requires a person. But the orientation work — finding every material clause, comparing to your standard positions, organizing the review — that's something tools can dramatically accelerate, whether you have a one-person legal team or a team of five.
The companies that build the right process infrastructure early — standard templates, contract repository, basic tiering, and tooling for review — find that their first legal hire lands into a functional operation and can focus on judgment rather than basic organization. That's a materially different GC hire than the one who spends their first year building from scratch.
