Finding Leverage with an IP Team of One

A role without a manual

The Head of IP at a fast-growing deeptech company sits down on Monday morning to three patent disclosures waiting for review, a maintenance fee deadline, an urgent docketing task, and an outside counsel invoice that has tripled the quarter’s budget. The role was created to be strategic. Little in the queue qualifies.

This is the job for the first Head of IP at almost any early-stage company. Whoever takes it arrives to find a portfolio already in motion, an outside counsel relationship someone else set up, and no predecessor to explain how any of it works. There is no operating manual because none was ever written. The traditional in-house playbook assumes a department large enough to specialize. The fully outsourced model assumes a general counsel content to receive monthly status reports and approve invoices. Neither describes the team of one, who handles invention intake, filing decisions, outside counsel, portfolio maintenance, board reporting, budget, and strategy alone. The teams that do well at this size are not simply working harder than their peers. They have made different decisions about what the job is.

Mapping the time before changing it

Start by measuring where the time goes. Take a typical week and divide the hours into four buckets: harvesting inventions from R&D, filing through outside counsel, managing the portfolio, and strategy. At most startups the first three take 70 to 80 percent of the week. Strategy gets whatever is left once the operational fires are out.

Carlo Cotrone, writing in IPWatchdog, argues that effective IP teams measure themselves by impact rather than activity. For a team of one the distinction is not academic. Every hour spent on work that does not change a business outcome is an hour taken from the work the role exists to do.

Harvesting inventions without chasing inventors

The usual complaint is that engineers do not invent enough, or do not write up what they invent. The real problem is that the disclosure process was built for an IP team with enough people to chase inventors. With one person, that process breaks.

Three changes help. First, let engineers disclose from what they already produce: slides, design reviews, engineering tickets. A rough disclosure costs far less than a missed invention. Second, recruit one person on each technical team as an informal IP liaison. That person needs no patent training, only enough awareness to flag a colleague’s work when it looks patentable. Third, use AI at intake. Current tools can turn raw inventor material into an attorney-ready disclosure, run a preliminary patentability search, and check the invention against the company’s strategic priorities. That moves the IP leader from processing documents to reviewing decisions.

Using outside counsel deliberately

Most first Heads of IP inherit their outside counsel. The relationship was set up by a founder, a former general counsel, or whoever handled patents before, and it continues by default. Revisiting it is one of the most valuable things a new IP leader can do, and one of the least comfortable.

Three decisions deserve to be made on purpose. First, reserve premium firms for complex, high-stakes prosecution where the value of the asset justifies the rate. Well-defined inventions in settled prior art can go through less expensive channels; mid-sized corporate IP departments now routinely mix in-house drafting, boutique firms, and managed filing services. Second, get off hourly billing where you can. Hourly work is the largest source of budget surprises for a small team, and the latest AIPLA Report of the Economic Survey notes a continuing shift toward flat-rate prosecution. A predictable cost is worth more than a slightly lower one when there is no slack to absorb an overrun. Third, own the record. If prosecution history lives only in the firm’s docketing system, the company depends on that firm for status, data, and memory. Keep a system of record of your own, whichever firm files the work.

Seeing the portfolio

At this scale, portfolio data is scattered. Some sits in the law firm’s portal, some in spreadsheets, some in email. It gets pulled together by hand when leadership asks a question, and not otherwise. The company owns the portfolio but cannot see it.

An IP leader should be able to answer the basic questions in minutes: how many active filings there are, what annual maintenance costs, which patents cover which products. Reporting belongs inside the working process, so a board update takes an hour rather than a week. Pruning belongs there too. Most small teams avoid it and treat abandonment as an admission of failure. It is closer to housekeeping. Fewer than five percent of issued patents are ever licensed, by most industry accounts, and National Science Foundation analysis finds that most patented inventions are never commercialized. Some share of every maintenance budget is paying for assets that no longer earn it. Ask three questions of each one: does it cover a current or planned product, would the company file it again today, and is it worth what it will cost to carry through the next renewal? An asset that fails two of the three is a candidate for abandonment. The savings usually pay for the other changes in this playbook.

The strategic work the role was created to do

Once harvesting, filing, and portfolio management run without constant attention, three things deserve the time that frees up. They are the reasons the role exists.

First, treat each filing as an investment. Weigh fit with current or planned products, competitive significance, commercial potential, and timing, and be willing to say no. A clear no is what makes the budget available for a confident yes. Second, talk to leadership about IP in business terms. IAM’s much-cited guidance on world-class IP management holds that the head of the function must above all build trusted relationships across the company, beginning with the CEO. Third, get to R&D early. Dolby and Nokia built their licensing businesses by aligning IP strategy with R&D priorities years before any patent issued. A small team cannot work at that scale, but it can map portfolio gaps against the product roadmap and raise them in planning, rather than discovering them after a competitor files.

Tools, systems, and the function as a whole

One distinction runs under everything above. A tool makes a task faster. A system connects tasks into a workflow. A function is the people, the system, and the execution together, and it is judged by business outcomes rather than by the efficiency of any one step. Most small IP teams buy tools and hope they add up to a function. The ones that do well design the function first and pick the infrastructure to fit. That is the shift behind integrated platforms like Tradespace, which combine software, AI, and on-demand attorneys in one place.

The constraint as a design principle

A team of one is a constraint, and it forces decisions about the operating model that larger departments can avoid by adding people. The teams that take the constraint seriously, replacing the inherited model instead of tuning it, build IP functions that run well beyond their headcount. The role becomes what it was meant to be: strategic, tied to the business, and hard to do without. The IP leaders writing this playbook are the ones who stopped trying to do the old job faster and started doing a different one.

A note from Tradespace

Everything in this playbook describes the situation Tradespace Counsel was built for: one person, a growing portfolio, and no room for a process that assumes a department. Counsel pairs the Tradespace platform with IP attorneys from top law firms and boutiques who draft and file at flat fees, working from the company’s own system of record. The company keeps the function and the data. The attorneys do the drafting. If that is your Monday morning, talk to an attorney.