From One Patent Application to a Portfolio: Planning the First Filing

How a first patent application sets up later continuations and follow-on filings, and how founders can plan a portfolio on a startup budget.

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

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

A patent portfolio usually grows from the first application. The specification of that first filing sets the outer limit of what later continuation and divisional applications can claim with the benefit of its filing date, so a first application written with the future in mind can support continuation filings for years, while a narrow one can leave valuable variations unprotected. Planning for that does not require a large budget. It requires describing the invention broadly and thinking about which products and competitors the patents will need to cover.

This guide is for founders and companies filing a first application who expect to build on it.

Why the first specification matters so much

A patent’s claims define what it covers, but the specification is what the claims must be based on. Once an application is filed, new technical content cannot be added to it. Later applications that claim the benefit of its filing date, such as continuations, can obtain that date only for what the original specification already describes. A continuation-in-part can add new material, and an entirely new application can cover later developments, but in both cases the new material receives the later filing date.

That makes the first specification a kind of reserve. Claims filed now might target your current product. Claims filed in two or three years, in a continuation, might target the version a competitor actually ships. Both can rely on the same original filing date, but only if the original specification describes enough to support them.

How continuation applications work

A continuation application is a new application that uses the same specification as an earlier pending application, called the parent, and claims the benefit of its filing date (35 U.S.C. 120). It pursues different claims, often broader, narrower, or aimed at a specific product.

Two practical points matter for planning:

  • A continuation must be filed while the parent is still pending. Once the parent issues as a patent or is abandoned, the opportunity to file a continuation from it ends, unless a qualifying intermediate application in the same chain is still pending.
  • Continuations share the parent’s patent term. Patent term generally runs 20 years from the earliest non-provisional filing date the application relies on (35 U.S.C. 154(a)(2)), so continuations do not extend protection beyond the family’s original term.

Because of the first point, some companies keep at least one application in a family pending while the technology and the market are still developing, to preserve the option to pursue new claims. Whether that is worthwhile depends on the invention and the portfolio: continuations carry prosecution and maintenance costs, and new claims face their own prior art, double patenting, and other patentability questions.

Planning the first application around the roadmap

The most useful planning conversation before the first filing is about where the product and the market are heading. A few questions shape the specification:

Why would someone buy this, or a product containing it? Identify the technical features that actually drive purchasing decisions: what makes the product faster, cheaper, more accurate, or easier to use than the alternatives. Those features deserve the most thorough description, because they are what the claims most need to cover.

What will the next versions do? Features already on the roadmap can often be described in the first application, even before they are built, as long as they can be described in enough technical detail.

How might a competitor do the same thing differently? The specification should describe alternative ways of achieving the same result, so that later claims can reach designs that are not identical to yours.

Where else could the technology apply? A method developed for one industry or device type may apply to others. Describing those applications gives later claims room to cover them.

Which parts of the system could stand alone? A system often contains several separable ideas: a data processing method, a hardware arrangement, a user interface technique. Each can become the focus of its own claims, in the first application or in later continuations or divisional applications.

Planning on a startup budget

Building a portfolio does not mean filing many applications at once. A common, budget-conscious sequence looks like this:

  1. A thorough first filing. Whether it is a provisional or a non-provisional application, the first filing does the most to set up the family. Spending more effort on its specification is usually more efficient than filing several thin applications.
  2. A non-provisional application within 12 months if you started with a provisional, claiming its benefit and adding any further development (though new material gets the later filing date). Limited relief exists if the deadline is missed unintentionally, through a petition to restore the benefit of a non-provisional filed within 14 months (37 C.F.R. 1.78), but it should not be planned around.
  3. Continuations timed to business needs, such as a new product launch, a competitor’s product, a financing round, or a licensing discussion. Filing them as needs become clear spreads cost over time.
  4. New applications for genuinely new developments. Improvements that go beyond what the original specification describes need their own applications with their own filing dates.

If protection outside the United States may matter, international filing decisions generally need to be made within 12 months of the first filing. That deadline is worth putting on the calendar at the start.

What investors and acquirers look at

The central question is simple: does the portfolio protect the reason someone would buy this product, or a product containing it? Claims that cover the features customers pay for generally carry more weight than claims on incidental details of one implementation. If a competitor could deliver the same benefit to customers without using what is claimed, the patent may add less to the company’s position.

Many technologies are sold as part of something larger: an algorithm inside a device, a chip inside a phone, a software module inside a platform. In those cases it helps to claim both the component and the product or system that contains it. The company that makes the end product is often the one whose purchasing or licensing decisions matter, and claims written only at the component level may not reach it, depending on what that company actually makes, uses, sells, or imports, and whether indirect infringement theories apply.

Acquirers ask a related question: would a larger company want to own these patents, either to protect its own products or to keep competitors from offering the same benefit? Patents that cover a capability the market is moving toward are worth more to a buyer than patents tied to one version of one product.

Beyond the claims themselves, reviewers may look at whether a family remains pending, whether there is a clear plan tying filings to products, and claims that are not limited to one implementation. It also helps to be able to explain the portfolio simply: which applications cover which products or technical areas, what is pending, and what is planned. Keeping a short internal summary of that, updated as filings are made, makes those conversations easier.

Common gaps in first applications

A few patterns commonly limit portfolios:

  • Describing only the version that shipped, without alternatives or variations
  • Leaving out the step-by-step technical detail of how the key operation works
  • Describing a single use case when the technology has broader applications
  • Letting every application in a commercially important family issue or lapse without considering whether a continuation is warranted, which closes off new claims on that disclosure

Each of these is far easier to address before the first filing than afterward.

A practical takeaway

Treat the first application as the foundation of a family, not a single filing. Before drafting begins, discuss why customers buy the product, the roadmap, likely competitor alternatives, and other applications of the technology with your patent attorney or agent, and make sure the specification describes them. As each application approaches issuance, you and your patent practitioner can evaluate whether a continuation would provide meaningful additional protection, considering the original disclosure, commercially important claim scope not yet pursued, anticipated product developments, remaining term, prior art, and cost. Keeping a family pending can preserve options, but it is not necessarily appropriate for every invention or portfolio.