Jesse J. Camacho

What is a patent, really?

It is a time-limited right to stop other people from making, using, or selling what it describes.

Notice what that does not say. A patent is not permission to build the thing yourself. A company can hold a patent on its own product and still be blocked by someone else's patent covering one component inside it. Those are two separate questions, and a patent only answers one of them.

It is also not a prize for having the idea first, and it is not a general claim over a field. It is a legal instrument with a boundary, and that boundary is written down in one specific place.

The place is the very end of the document. After all the drawings and the long description, a patent finishes with a set of numbered sentences called claims. Everything before them is scenery. The claims are the property line, and almost every patent fight is a fight about them.

Can they sue me if I never copied anything?

Yes. Copying is not required, and inventing it yourself is not a defense.

This is the fact that surprises people most, and it is the reason an accusation can feel so unjust. If your product does what one of those numbered claims describes, it can infringe even if your team designed it from scratch, in a different state, having never heard of the patent or the company that owns it.

Being angry about that is a reasonable response. It is still the rule. The useful move is to stop arguing about where your idea came from, because that question is mostly beside the point, and start on the question that decides the case: what do the claims actually say, word by word, and does your product do all of it.

All of it matters. A claim is read as a whole sentence, not as a general feeling of similarity. If your product does not do one of the elements a claim lists, that claim is usually not infringed, however close the two things look side by side.

What actually decides who wins?

Very often the meaning of a handful of disputed words, settled by a judge before a jury hears anything at all.

That step is called claim construction, or a Markman hearing. Each side argues what the contested terms in the claims mean. The judge rules. Cases are frequently decided in substance right there, because once a word has a definition, either the product does that thing or it does not.

So where does the judge look for the meaning? At the patent itself, and heavily at its prosecution history: the public written record of the back and forth between the applicant's lawyers and the patent office. To get a patent granted, applicants very often narrow what they were claiming. Those narrowings are permanent, and they limit what the patent can be argued to mean years later.

That record is called the file wrapper. It is public, anyone can pull it, and it is usually very long and very dull. Reading all of it is unglamorous work that people skip. A great deal of quiet leverage lives in the part everyone skipped.

What happens if I ignore this?

If it is a filed complaint, ignoring it can lose you the case before anyone has looked at whether you were right.

A complaint is one side's allegation. Nothing has been found, nothing has been decided, and companies of every size and every degree of care receive them. It is normal to feel judged by a document that has not yet judged anything.

The deadline is the part that does not wait. In federal court, a response to a complaint is generally due 21 days after service. That date can shift with waivers and extensions, and it belongs to your particular court and your particular case, which is exactly why the first thing to do is confirm it rather than assume it.

A demand letter is different. It arrives before any lawsuit and carries no such deadline, but it is not nothing either. It opens a range of outcomes from a license negotiation to litigation, and it starts real obligations, including preserving documents. Whether silence is a sound strategy or an expensive one depends on who sent it and what they actually want, and that is knowable.

What should I not do right now?

Do not delete anything, and do not speculate in writing.

Routine automatic deletion of email and files touching the accused product should be suspended today, not after you have picked a lawyer. Courts treat destroyed documents very seriously, and that problem can end up doing a company more harm than the underlying dispute would have.

Do not write internal email theorizing about whether you infringe. Founders and engineers do this instinctively and in complete good faith, and those messages are discoverable by the other side. Have that conversation with counsel, where it is protected.

Do not call the other side to sort it out yourself, and do not redesign the product overnight in a panic. Both feel like action. Both can narrow your options before anyone has read the claims carefully.

One thing to do rather than avoid: call your insurance broker early. Some business policies cover intellectual property defense, and late notice can forfeit that coverage entirely. Asking costs nothing.

How long is this going to take?

Longer than feels reasonable, and no honest answer comes with a date attached to it.

Anyone who hands you a number in a first meeting is guessing, and you should hear the guess as what it is. Schedules are set by courts, and courts move them. The shape is knowable even when the length is not: an early stretch of pleadings and document preservation, a long technical middle of document exchange and depositions and expert work, claim construction somewhere inside that, and then a pressure point where a great many matters resolve.

The more useful question is not how long it runs but when it takes your attention, because the demand is very uneven. There are quiet months where nothing reaches you at all. Then there is a week where engineers are pulled off the roadmap to sit for depositions, and preparation swallows a founder's whole schedule.

Planning around that unevenness is most of what makes a long case survivable for a small company.

Do I have to go to court?

Probably not in the way you are picturing, and some patent fights are not held in a courtroom at all.

Most patent disputes end in a negotiated resolution rather than a trial verdict. That is context, not a prediction about yours, and nobody honest will promise you an outcome. If people from your company do appear in person, it is more likely to be for a deposition at a conference table, or a hearing that one or two of them attend, than for a jury trial with everyone watching.

There is also more than one venue. Some patent fights are argued at the Patent Trial and Appeal Board, in a proceeding called an inter partes review, which asks a different question altogether: whether the patent should have been granted in the first place. It runs on a different clock and a different budget than a district court case.

Whether that route is available, and whether it is wise, depends on specifics that nobody can assess from the outside. It is worth knowing it exists, because plenty of people facing a complaint have never heard of it.

What will this cost me?

Nobody can quote you a real number today, and understanding what drives the cost will serve you better than a number would.

Cost here is mostly a function of scope. How many patents and how many claims are in play. How much document discovery is demanded, and how hard it is resisted. How many experts get retained. How many motions get fought rather than conceded. Much of that is chosen rather than fated, and it is chosen by both sides, repeatedly, over the life of the matter.

Which means the question to press a lawyer on is not the hourly rate. It is what they would decline to spend your money on, and how they intend to create pressure without letting the matter expand for its own sake. Those are answerable questions, and the quality of the answers tells you a great deal.

Ask early, too, about the other routes. A challenge at the Patent Trial and Appeal Board runs on a different clock and a different budget than a district court case, and whether that is available or sensible in your matter is worth raising before the discovery bills start rather than after.

How do I know if a lawyer actually understands my technology?

Ask them to explain your own product back to you, and listen carefully to how they do it.

A patent trial lawyer spends the working day explaining a technology to people who have never seen it. A judge. A jury. Sometimes your own board. If a lawyer can only discuss your product using the vocabulary you handed them an hour ago, they will need an expert to translate at every step, and that dependence shows up in the bill and in the result.

The second test is the file wrapper. Ask whether they will read the whole prosecution history themselves rather than work from a summary someone else prepared. It is tedious, it is where a case is often quietly won, and the answer tells you what kind of preparation you are buying.

The third test is whether the explanation you receive is one you could repeat to your board without rehearsing it. If it only makes sense while the lawyer is in the room, it will not survive contact with a jury either.