Most firms scale IP practices by hiring more paralegals. The cheaper move is making the work visible first. Run the math before the next req.
Visibility before bodies. The first ops director scales the practice once. The runbook they leave scales it every quarter after.
The partners can tell something's wrong. Status answers keep needing follow-ups. One client got correspondence on the same matter under two different docket numbers last quarter. A foreign filing slipped a week because three people each thought someone else was on it.
The easy answer is to hire another paralegal. Maybe two. Volume's up, the team's stretched, more bodies is the lever firms pull. So the firm pulls it. Three months later the same things keep happening, just at a slightly higher volume. There's just more of everyone to confuse. The first ops director the firm hires watches this happen and learns the only thing worth learning: the volume problem was never the volume.
The Scaling Math
Adding people to an opaque practice multiplies coordination cost faster than it adds capacity. Three paralegals can't see each other's queues unless someone built the system that lets them. Six can't see each other's queues twice as well. They just generate twice as many handoffs that nobody's tracking.
This is the math nobody calculates before hiring. Two new paralegals add roughly two paralegals of throughput, minus the time they spend asking who owns what, minus the time existing paralegals spend onboarding them, minus the time the partner spends asking three people for the same answer.
The actual lift is rarely one for one. Sometimes much less. The practice that bills new headcount as full capacity inside ninety days usually didn't measure it. The paralegals already on the team can tell when a new hire is going to spend a month asking the same five questions and another two months learning to read the partner's email tone. That month is theirs to absorb.
The work the new bodies were hired to absorb is the work nobody made visible first.
What Should a New IP Operations Director Do in the First 30 Days?
So the better first hire usually isn't another paralegal. It's an IP operations director. And their first thirty days are visibility.
Not new systems. Not new tools. Visibility into what's already there. Where's the work actually queued, versus where the docket says it is? Which workflows are real and which are aspirational? What lives in one paralegal's head, one practice leader's notebook, one veteran's email folder?
This is what new ops directors find in their first month. The shadow systems sitting alongside the docket are part of it: the recurring spreadsheets, the Friday status tracker, the foreign-agent list. Plus the dozens of one-person-knows-it pieces nobody wrote down.
The day-30 deliverable isn't a plan. It's a map. Where the work actually is, versus where the docket says it is. That gap is the answer to the partner's question about why status takes follow-ups.
Days 30 to 60: Building the Runbook
Once the map exists, the runbook follows. The five recurring decisions only the ops director is positioned to make (the day-in-the-life moves the role walks through every week) get written down so someone else could make them.
Status answers get a template. AI-output review gets a sequence. Foreign-agent loops get a routing rule. Capacity questions get a query. Friday's question for Monday gets a checklist.
The deliverable at day 60 is a runbook a competent hire could follow without the director in the room. That's the test. If the runbook only works when the director is there to explain it, it isn't a runbook. It's an internal monologue.
This is also where the first real headcount conversation starts to look different. Not "we need more paralegals," but "this specific runbook step is constrained by one person, and that's where the next hire goes." The paralegal who owns that step gets a different question from their manager. Not "can you handle more?" but "what would let you handle more?" Those are different questions.
How Do You Know the Operations Role Is Working?
By day 90, the firm has numbers it never had. How many open matters per paralegal. How many days the average response sits in queue before assignment. Which clients generate the most reroutes. Which weeks the foreign-agent queue spikes.
These aren't billing numbers. The firm has those. These are operational numbers, and most firms don't have them because nobody owned the question.
The first time a partner asks status and gets one number instead of three follow-ups is the proof. Not a dashboard with thirty metrics. Just one answer that didn't need three people in a hallway to produce.
That's the practice scaling. Not because anyone was hired. Because the work that used to take three people's time to assemble now takes one person, sometimes zero. That's also the work that used to write off as administrative time. It still costs the same to do. It just doesn't cost a partner's billable hour to find out.
When Should a Firm Hire More Paralegals Instead of an Operations Director?
This isn't an argument against hiring. There's a real volume threshold where bodies are needed. Some practices grew past it three years ago.
The argument is sequence. Visibility, then runbook, then measurement, then hire to a constraint the measurement named. Not hire because the firm feels overloaded.
The difference shows up in the second hire. A firm that hired to a feeling hires the second paralegal the same way it hired the first and gets the same diminishing-return math. A firm that hired to a measurement hires the second paralegal to a different constraint and gets a clean lift.
The trade press has started naming this. "IP firm operations" is now a phrase in the headlines, not a vendor slogan. The math underneath is the same: the practices scaling profitably aren't filing more. They're filing the same with fewer surprises.
How Do You Decide Whether to Build or Hire an IP Operations Function?
If you're a managing partner or COO deciding whether to fund the role at all, three questions answer the build-vs-hire decision.
First: can we name the work the role would do that nobody currently does? If the honest answer is "manage the paralegals better," the role is a senior paralegal title, not a new function.
Second: have we tried to scale by visibility before scaling by bodies? Firms that have never had operational numbers are hiring on instinct, not analysis. That's an expensive way to find a constraint.
Third: are we hiring because we have a measurable constraint, or because the firm feels overloaded? Feels overloaded is real. It's also not a hiring spec a partner can defend at the comp committee.
The Compounding Logic
The first ops director scales the practice once. The runbook they leave scales it every quarter after. That's a one-time investment with recurring returns, in a profession that's used to paying for recurring problems.
The math worth running before the next paralegal req opens.
If what an IP operations practice actually is is the strategic question and what the role actually does day to day is the tactical one, this is the question in between.
Common Questions
How does an IP operations director scale a practice without adding headcount?
By making the work visible before adding bodies. Adding paralegals to an opaque practice multiplies coordination cost faster than it adds capacity. An IP operations director's first 90 days build visibility (where the work actually lives), a runbook (a sequence a successor could follow), and measurement (operational numbers the firm didn't have). After that, hiring happens to a measured constraint instead of a vague feeling of overload, and the next paralegal lifts capacity instead of just adding handoffs.
What should a new IP operations director do in the first 30 days?
Visibility, not new systems or tools. Document where work is actually queued vs. where the docket says it is. Inventory the shadow systems (spreadsheets, status trackers, foreign-agent lists), the workflows that are real vs. aspirational, and the knowledge that lives in one person's head. The day-30 deliverable is a map of the gap between the practice as described and the practice as run.
When should a firm hire more IP paralegals instead of an operations director?
When there's a measured constraint pointing to a specific role. There's a real volume threshold where bodies are needed, and some practices grew past it years ago. The argument isn't "never hire." It's sequence: visibility, then runbook, then measurement, then hire to the constraint the measurement named. A firm hiring to a feeling of overload usually gets diminishing returns. A firm hiring to a measured bottleneck gets a clean lift.
How long until an IP operations director shows measurable results?
Ninety days for the first set of operational numbers the firm has never had: open matters per paralegal, days in queue before assignment, reroute frequency by client, foreign-agent queue spikes. The compounding return comes from the runbook. Once codified, the workflow scales without the director in the room. The role is a one-time investment with recurring returns.
What questions should firm leadership ask before creating an IP operations role?
Three. First: can we name the work the role would do that nobody currently does (if the answer is "manage the paralegals better," it's a senior paralegal title, not a new function). Second: have we tried to scale by visibility before scaling by bodies? Third: are we hiring because we have a measurable constraint or because the firm feels overloaded?