Five systems run a modern IP practice and none of them talk to each other. Here's what breaks at the seams, and what an orchestration layer fixes.
Five systems, one matter, no handoff.
The client called at 4:30 PM. A general counsel at a public company, calm but specific. "Where are we on the Cline family?"
The IP operations manager opens five systems to answer her.
She opens the docketing system for the next deadline. She opens the document management system for the last draft. Three versions, the most recent saved Tuesday by an associate. She opens the time and billing system. Flat fee, sixty percent burned. She opens the AI drafting tool the firm rolled out in February. It generated a response yesterday against a claim set she's not certain matches the current amendment. She opens her email. The foreign agent in Tokyo sent a status update on Friday she hasn't read.
The answer to the client's question lives across five systems. None of them know each other.
The reply goes out at 5:15 PM. It took forty minutes to write three sentences. None of those forty minutes will land on a bill.
Why Didn't This Happen Ten Years Ago?
Ten years ago an IP practice ran on two systems and a binder. The systems weren't better; there were fewer of them. A status request took longer to answer, but the question of where to look was simpler.
The modern stack is genuinely better. The DMS finds files in seconds. The billing system catches write-offs the firm used to absorb without noticing. The AI tool drafts in twenty seconds what used to take an associate forty minutes. Every one of those tools is an improvement. The cost is that there are now five places to look, and none of them check the others.
What Are the Five Systems That Run an IP Practice?
Each one is a source of truth for one thing. None of them are a source of truth for the matter as a whole.
The docketing system. Source of truth for when. FoundationIP, CPi, Inprotech, or whatever your docketing system is, they all do this well. None of them know which version of the draft is current, or whether the AI tool used the right one, or what the foreign agent said last week.
The document management system. Source of truth for files. iManage, netDocuments, or whatever your DMS is, it knows every version and every author. It doesn't know which version got billed against, which version matches the docketed deadline, or which version the AI tool worked from.
The time and billing system. Source of truth for hours. It knows what got captured against the matter. It doesn't know whether the time landed on the current version, whether the AI tool saved hours that never got billed, or whether the foreign agent's invoice arrived.
The AI drafting tool. Source of truth for the draft it just generated. It doesn't know whether the response is against the current claim set, whether the docket reflects the deadline, or whether the partner has reviewed it. It adds output. It doesn't route it.
The foreign agent email thread. Source of truth for the work happening outside the firm. It knows what got sent and what Tokyo flagged about the local examiner. It lives in Outlook. None of the other four systems read Outlook.
Five systems. Five sources of truth. Zero overlap.
Where Does the Work Actually Break?
The seam between two systems is where context drops.
The AI tool drafts a response. Where does it go? The associate moves it to the DMS by hand. He checks the docket in another tab to confirm the deadline. He emails the partner with the draft attached and the deadline in the subject line. He emails the foreign agent if the draft references their input. The handoff between the AI tool and the next four systems is the associate. Twenty minutes per handoff. Not a single one of those minutes shows up on a time sheet.
The deadline in the docket moves. Does the foreign agent know? Only if someone emailed them. Does the AI tool know? It doesn't ask. The next draft will be generated against whatever it was given.
Each seam is twenty minutes that doesn't get billed. By month-end the seams add up to a write-off.
What Does an Orchestration Layer Actually Do?
Three sentences.
It reads from the five systems. It moves work between them so the seam stops being a person. It hands context to whichever system, person, or AI tool does the next step.
It doesn't replace the five. It doesn't add a sixth. It sits above them.
Why Won't a Sixth System Fix It?
The two pitches in the market right now both add a sixth tool.
The marketplace pitch sources outside counsel through a platform. Useful for finding work, not for moving work through the firm once it's found.
The "AI operating system" pitch replaces your docketing, DMS, and billing. It replaces one or two systems and leaves the AI tools and foreign agents where they are.
The work isn't to consolidate the stack. The work is to coordinate it.
What This Looks Like on a Tuesday That Works
The client calls. The IP operations manager opens one screen.
The docketing deadline surfaces. The current version of the draft is linked next to it. The hours billed against this version are summed beneath it. The AI tool's last output is timestamped against the current claim set. The foreign agent's Friday status sits at the top of the thread, flagged as unread.
The reply goes out in four minutes. The associate's twenty-minute handoff is twenty seconds. The attorney opens the matter and the current draft is already there.
The five systems didn't change. What sits between them did.
Where to Start
If you run an IP practice, the question to ask your operations team on Monday is not "which of these systems should we replace?" It's "name the five systems we run on, and for each one, name the seam where work gets dropped." The answer is the operations layer's job description. The cost of not asking shows up where the partners read it: write-offs, late matters, clients calling for a status the firm took forty minutes to assemble.
PracticeLink is the orchestration layer. It reads from the docketing system, the DMS, the billing system, the AI tools, and the email threads the firm already runs on. It doesn't replace any of them. It coordinates them.
Part of our Pillar 2 series on the IP Operations Orchestration Layer. See also: The IP Operations Orchestration Layer, Why AI Tools Fail Without an Orchestration Layer, and Why Your Docketing System Needs an Operations Layer.