A patent portfolio is not a moat just because it is long.
I have seen companies enter fundraising, M&A, and strategic partnership discussions with impressive patent counts. The slide looks strong. The founder feels protected. The investor leans in for a moment.
Then the practical questions start.
Which patents map to the current product? Which claims cover the economic feature customers actually pay for? Which filings protect the roadmap rather than last year's prototype? Where is the freedom-to-operate analysis? What is protected as trade secret instead of disclosed? Who owns the IP created by contractors, universities, or early employees?
That is where a patent count can fall apart.
Defensibility is not measured by the number of filings. It is measured by how well the company's intellectual property protects the value creation plan.
IP Must Follow the Business Model
A business does not get credit for protecting inventions that do not matter commercially.
In early technical companies, patent strategy is often driven by invention events. An engineer creates something novel. Counsel files. The company adds another asset to the list. That is fine as a starting point, but it can drift away from the business.
At scale, IP needs to follow the revenue model.
If the company wins because of a proprietary workflow, the protection strategy should address that workflow. If the value sits in data, labeling, model training, process know-how, or integration depth, a patent-only approach may miss the point. If customers buy performance, accuracy, durability, or cost reduction, the claims need to protect what enables those outcomes.
I worked with a company that had several patents around early product architecture. The market had moved. The current product was stronger, but the filings did not cover the features driving adoption. Competitors could avoid the claims without changing much. The company did not have bad IP. It had stale IP.
The correction was to map IP against the current product, customer use cases, roadmap, and competitor alternatives. Only then did the company know what to file, what to keep as trade secret, and what no longer deserved maintenance spend.
Investors Care About Enforceable Advantage
Investors do not want legal decoration. They want confidence that the company's advantage can survive competition.
That does not always mean suing competitors. In fact, most companies never want litigation. But investors need to know that the IP portfolio creates practical friction. Can a competitor copy the product without stepping into claims? Can a strategic buyer gain clear ownership? Can a large incumbent work around the technology with moderate effort? Can a former employee take the real know-how out the door?
Those questions matter because scale attracts attention.
At $3M of revenue, a company may fly under the radar. At $30M, competitors study the model. Customers ask harder procurement questions. Strategic partners request diligence. Acquirers scrutinize ownership and assignment history.
Weak IP hygiene becomes a transaction problem fast.
I have seen diligence slow down because early contractor agreements were incomplete. I have seen acquirers discount value because core algorithms were described broadly in patents while the implementation know-how lived informally with two engineers. I have seen founders assume provisional filings created protection when no continuation strategy existed.
None of those issues made the business worthless. They did create risk that could have been handled earlier at far lower cost.
Trade Secrets Need Operating Discipline
Some of the most valuable defensibility never belongs in a patent filing.
Customer data structures. Manufacturing parameters. Pricing algorithms. Process tolerances. Implementation playbooks. Supplier methods. Model training techniques. These assets may be better protected as trade secrets, but only if the company behaves like they are secret.
That requires discipline.
Access controls. Clean employee agreements. Contractor assignment language. Documentation standards. Exit procedures. Segregation of sensitive repositories. Clear rules for conference talks, sales demos, and customer pilots.
This can sound legalistic. It is operational.
If everyone can access the core process file, if customer data is exported casually, if engineers reuse code from prior employers without review, if sales shares technical detail to win a deal, the trade secret story weakens. A company cannot claim disciplined protection after years of casual handling.
The same applies to open-source software. Many technical companies treat open source as an engineering detail until a buyer or investor asks for a scan. Licensing problems can create real friction. Better to know early, set rules, and keep records.
Defensibility is built through daily habits, not just filing receipts.
The Roadmap Should Drive the Portfolio
A scalable IP strategy looks forward.
The question is not only what the company has invented. The question is what position the company needs to defend three years from now. New verticals. Platform features. Data advantages. International markets. Hardware changes. AI-enabled workflows. Integration layers. Each can change the IP strategy.
I prefer to review IP as part of strategic planning, not as a separate legal update. Product, engineering, commercial, finance, and counsel should share the same map. Where is the margin? Where is the customer lock-in? Where is the switching cost? Where could a competitor attack? Where might a strategic acquirer see unique value?
From there, the company can decide what to patent, what to keep secret, what to publish defensively, what to abandon, and what to monitor in competitor filings.
That is how IP becomes a business asset instead of a binder.
A strong patent list can support valuation. It cannot substitute for a clear connection between invention, customer value, and competitive friction.
Defensibility at scale is not how much IP you own. It is how much of the business your IP actually protects.