Preparing for your first conversation with a patent attorney

What to gather before a first patent attorney call, what to hold back until conflicts are cleared, and the questions that make the call worth your time.

By , registered patent attorney. Published . 4 min read.

General information about patent law and practice, not legal advice about your situation. How these rules apply depends on the facts.

A first call with a patent attorney or agent is about fit, scope, and timing, not the details of your invention. Come with the names of the people and companies involved, a one-line description of your technical field, and any dates that matter. Hold the technical details until conflicts have been cleared and you have agreed on an engagement in writing.

Patent attorneys and patent agents are both registered with the USPTO to prepare and prosecute patent applications, and the advice here applies to working with either. This article calls them practitioners.

That can feel backwards. You are there to talk about the invention, and the first call asks you not to. The reasons are practical, and preparing around them makes the call far more useful.

Why the first call stays high level

Before a practitioner can take on your matter, they need to confirm they do not already represent someone on the other side of it: a competitor, a former employer, a collaborator, or an investor with competing interests. That check runs on names, not technology.

Keeping the first conversation general also protects you. Practitioners owe certain duties to prospective clients even before an engagement exists, including duties about information shared in an initial consultation, but those duties are narrower than the duties owed to a client, and they do not make detailed technical disclosure the right first step. The practical course is to share only what is needed to decide whether to work together. Detailed technical information belongs in a structured intake after conflicts are cleared and the engagement is defined, when it can be reviewed properly and kept with your matter.

What to gather before the call

A short list covers almost everything the practitioner will ask.

The people and companies involved. Your company name, the founders, and anyone who may share ownership of the invention. That includes co-founders who have left, contractors who did technical work, universities or former employers whose time or resources were involved, and investors with rights in your intellectual property. These names drive the conflicts check, and they also surface ownership questions early.

Your technical field, in a sentence. “Machine learning for industrial sensors” or “power electronics for electric vehicle charging” is enough. It tells the practitioner whether the work is in their area, without describing what you built.

What you want to accomplish. One application to protect a core product, a first filing before a fundraise, or a plan for several related applications over the next year. You do not need to know yet whether you want a provisional or a non-provisional application. Sorting that out is part of the scoping conversation.

Dates that matter. Planned product launches, public demos, conference talks, papers, investor pitches, and anything you have already shown or offered to people outside the company. Mention the dates and the type of event, not the technical content.

Anything already filed. Whether you or the company have filed patent applications before, even provisional ones, and roughly when.

Why dates come up early

Patent rights are sensitive to timing. Public disclosures, sales, and offers to sell can affect what you can still protect. In the United States, a grace period may exclude certain disclosures made by the inventor within one year before filing, but whether and how it applies depends on what was disclosed and the specific exceptions in 35 U.S.C. 102(b). Many other countries offer no comparable grace period, so a public disclosure can limit foreign rights even when US rights remain available.

The rules have exceptions, and how they apply depends on the facts. That is exactly why the first call asks about dates: a practitioner can evaluate whether timing affects your options, but only if the dates are on the table early.

Questions worth asking the practitioner

The first call is also your chance to evaluate the practitioner. A few questions separate a good fit from a poor one.

Who will do the work? Ask whether the person you are speaking with will interview your inventors and draft the application, or whether the work passes to someone else.

What is their background in your technology? A drafter who understands your field asks better questions and writes a specification that describes how your system actually works.

What is included? Inventor interviews, prior art review, drawings, review rounds, filing, and responses to the patent office after filing are each separate pieces of work. Ask which ones are part of the engagement and which are scoped separately.

How are fees set? Most practices scope the work and agree on fees in writing before drafting begins. Ask what drives the fee for an application like yours, such as the complexity of the technology and the number of variations and figures.

What does the timeline look like? Ask how long a first draft usually takes once the technical material is in hand, and how review rounds work.

What happens after filing? An application is reviewed by an examiner, who often raises objections that need a response. Ask whether the same practitioner handles that stage.

What happens after a good first call

If the call confirms a fit, the usual sequence is straightforward. The practitioner completes the conflicts check, you agree on scope and fees in writing, and only then do you share technical documents. From there, an inventor interview fills in the details, a draft goes to you for review, and the application is filed once you are satisfied with it.

A one-page checklist

Before your first call, write down:

  • Your company name, founders, and anyone else who may own part of the invention
  • Former employers, universities, contractors, and investors who may have rights in it
  • Your technical field, in one sentence
  • What you want to protect, and why now
  • Dates of any past or planned public disclosures, launches, demos, papers, or pitches
  • Any patent applications already filed

Leave the technical documents for later. A clear first call with these answers gets you to a well-scoped engagement faster than a detailed one ever does.