When You Need Outside General Counsel — And When You Just Need a Lawyer

Technology companies often conflate two distinct types of legal relationships: outside general counsel (OGC), which is a strategic ongoing advisory relationship, and transactional legal representation, which is engagement of a lawyer to handle a specific matter. Both are legitimate and valuable. They serve different purposes, operate on different economic models, and create different kinds of value for the client. Confusing them leads to either overpaying for services you do not need or under-investing in the legal infrastructure your company actually requires.

This post explains the distinction and provides a framework for deciding which relationship your technology company needs at a given stage of its development.

What Outside General Counsel Actually Is

Outside general counsel is a relationship, not a transaction. An OGC is a lawyer or law firm that serves as the company's primary legal advisor across all areas of law — the legal equivalent of an in-house general counsel, but outside the company. The OGC knows the company's business, its people, its technology, its competitive landscape, and its legal history. That institutional knowledge is the core of the relationship's value.

An OGC relationship for a technology company typically involves: regular communication with the founding team or executive leadership about legal dimensions of business decisions; proactive legal risk identification as the company's activities evolve; coordination of specialized outside counsel (patent prosecutors, litigators, regulatory specialists) when matters require expertise beyond the OGC's scope; maintenance of a legal knowledge base about the company that enables efficient handling of new matters; and availability for quick consultations on questions that arise in the normal course of business.

The OGC relationship is valuable precisely because it is continuous. A lawyer who knows your company's IP situation, your employee agreements, your customer contracts, your cap table, and your regulatory posture can give you faster, more accurate, and more cost-effective advice than a lawyer who is encountering your company for the first time on each engagement.

What Transactional Legal Representation Is

Transactional legal representation is engagement of a lawyer to handle a specific defined matter: negotiate and document an acquisition, file a patent application, respond to a regulatory inquiry, handle a contract dispute, or prepare SEC filings. The relationship begins when the matter begins and ends when the matter concludes. The lawyer brings expertise in the specific type of matter and applies it to your facts.

Transactional representation is appropriate when: the matter is clearly defined and bounded; the matter requires specialized expertise that does not exist in an OGC relationship; the matter is unlikely to recur; or the company does not yet have the volume of legal activity that justifies an OGC relationship.

The limitation of purely transactional legal relationships is that each engagement starts from scratch. The lawyer must be brought up to speed on the company's background, technology, business model, and prior legal history before they can give advice that is properly calibrated to the company's actual situation. For a company with complex IP, regulatory, and contractual relationships — which describes most serious technology companies — this ramp-up cost is significant and is paid repeatedly.

The Right Model for Technology Companies at Different Stages

Early-stage technology companies — pre-revenue, pre-product, pre-team — typically do not have enough legal activity to justify an OGC relationship. What they need is a lawyer who can handle entity formation, founder agreements, and IP assignment agreements efficiently and at reasonable cost. That is transactional representation with a lawyer experienced in start-up formation.

The inflection point toward OGC typically occurs when the company has: multiple active legal fronts running simultaneously (IP prosecution, customer contracts, employment matters, regulatory compliance, fundraising); recurring legal questions arising from normal operations that require quick answers without full engagement overhead; and a business complex enough that a lawyer without institutional knowledge is meaningfully handicapped in advising the company.

For most technology companies, this inflection point occurs somewhere between seed funding and Series A (first institutional venture capital funding round). By the time a technology company is executing its first enterprise customer contracts, managing an IP prosecution portfolio, dealing with employment matters as the team scales, and preparing for Series A due diligence, the cumulative cost of purely transactional representation — with its repeated ramp-up costs and lack of cross-matter integration — usually exceeds the cost of an OGC relationship that handles all of these areas with full institutional context.

The Engineering-Fluent OGC Dimension

For embedded systems companies and other engineering-intensive ventures, the OGC relationship has an additional dimension that purely legal practices cannot provide: the ability to engage directly with technical decisions as they are being made by your Chief Technology Officer (CTO) and engineering team, not just with their legal consequences after the fact.

When an engineering team is choosing between safety architectures for an Automotive Safety Integrity Level D (ASIL-D) system, the legally relevant question is not just "what does ISO 26262:2018 (Road Vehicles — Functional Safety) require?" — it is "what Hazard Analysis and Risk Assessment (HARA) documentation, Threat Analysis and Risk Assessment (TARA) records, and process evidence will make this system legally defensible if a product liability case arises in five years?" process, and design choices will make this system defensible if a product liability case arises in five years?" That question can only be answered effectively by someone who understands both the engineering decision and its legal context simultaneously.

When a founding team is evaluating whether to build a feature using a third-party machine learning framework, the legally relevant questions include open-source license compliance, intellectual property (IP) ownership of outputs, European Union General Data Protection Regulation (GDPR, Regulation (EU) 2016/679) implications if the feature processes personal data, and export control implications if the framework has cryptographic components. A lawyer who needs to be briefed on what machine learning is cannot provide useful real-time input on these questions. A lawyer who has spent decades in embedded systems development can.

---

Attorney advertising. The information in this post is provided for general informational purposes and does not constitute legal advice. Prior results do not guarantee a similar outcome. © 2026 guibert.law