Author: PowerPatent Content Team
-
112 Written Description: Showing Support Without Rewriting
There’s one part of the patent rulebook that quietly trips up a lot of smart founders and engineers. It’s not because it’s complicated. It’s because it’s often misunderstood. It’s called the written description requirement under Section 112 of the U.S. patent laws. What Section 112 Really Means (And Why It’s So Easy to Miss) The…
-
112 Indefiniteness: Fixing Fuzzy Terms Fast
Most founders don’t think about it until it’s too late. You file your patent. It seems fine. But later — maybe during funding, acquisition, or a legal review — someone finds it. A vague word. A fuzzy phrase. Something you thought was “clear enough.” What is 112 Indefiniteness — and Why It Can Blow Up…
-
Means-Plus-Function (112(f)): Build Support That Survives
Let’s get right to it. If you’re building something new—an invention, a product, a piece of software—you want protection. Real protection. The kind that actually holds up when someone tries to copy what you’ve built. That’s where patents come in. And there’s one part of patent law that can either be a secret weapon… or…
-
After Final Strategy: AFCP 2.0 vs. RCE vs. Appeal
So you’ve been working on your patent. You filed it. You got that first Office Action. You replied. And then… you got a Final Rejection. Oof. Now what? That’s the moment many founders and inventors hit a wall. You’re building something real. You want to protect it. But now the patent office is saying “No.”…
-
Examiner Interviews That Flip Outcomes: Scripts & Exhibits
Let’s be honest. Patents are hard. They take time. They feel slow. And sometimes, even after you’ve explained your invention in plain English and sent over every detail you can think of, the patent examiner still pushes back. You get an office action. Then maybe another. Suddenly, the whole thing feels stuck. What Most Founders…
-
Predict the Next Office Action: Amend or Argue?
You filed a patent. Great. But now comes the part no one tells you enough about—the pushback. The USPTO comes back with questions. Concerns. Rejections. It’s called an “Office Action.” And when that happens, you’ve got two options: fix it or fight it. Amend the claims or argue your position. What’s Really Going On in…
-
Train Your Team: Dashboards That Matter for Examiner Intel
You’ve probably heard it before: getting a patent approved can feel like a black box. You submit your application, wait, and hope for the best. But behind the scenes, there’s a person who plays a major role in your success—the patent examiner. And the better you understand them, the better your odds. Understanding Examiner Behavior…
-
Build a Firm-Wide Examiner Knowledge Base That Compounds
Most patent teams are flying blind. Every time a new patent examiner comes up, it’s like starting from scratch. You’re guessing what they’ll allow, what they hate, how they think. And that guessing game? It wastes time, burns money, and drags out the process. What Is an Examiner Knowledge Base—and Why Most Firms Don’t Have…
-
101 Rejections Made Simple: A Playbook That Actually Works
If you’re reading this, there’s a good chance your patent got hit with something called a 101 rejection. Or maybe you’re just trying to avoid it. Either way, you’re in the right place. Here’s the deal. Most smart inventors and founders don’t expect to get a 101 rejection. Especially if what they’ve built is actually…
-
Beating Alice: Practical “Practical Application” Arguments
If you’re building something real—writing code, training models, designing systems—you want to protect it. You want to own it. That’s what patents are for. But if your tech touches software, data, or algorithms, you’ve probably heard of Alice. Or maybe you’ve been hit with a rejection under it. What “Practical Application” Actually Means (And Why…