Stop Patenting Your Invention. Start Patenting Your Competitor’s Product.
You spent $50,000 describing what you built. Your competitor read it, built something different, and kept competing.
You filed a patent on your product. The claims describe exactly what you built — your architecture, your process, your implementation. The patent issued. You celebrated.
Then your competitor launched. Same feature. Same customer benefit. Different implementation.
Your patent is technically valid and commercially useless.
The competitor’s attorney read your claims, identified every implementation-specific element, and confirmed: “No risk. Their claims describe their architecture, not ours.”
You did not just fail to constrain your competitor. You published a technical manual teaching them exactly how you solved the problem — and got nothing in return.
“What Did We Build?” Is the Wrong Question
Most invention disclosure meetings start the same way. The inventor walks in, describes what they built, and the attorney writes it down. The claims that emerge from that meeting describe the company’s product — its architecture, its data flow, its implementation choices.
That is the wrong starting point.
A valuable patent does not read on your product. It reads on your competitor’s product.1
Those are fundamentally different objectives producing fundamentally different claims.
When the lens stays on your product, claims become an implementation diary — a detailed record of every decision you made, every architecture you chose, every constraint you worked around. The claims describe you. They protect nothing.
When the lens shifts to the competitor, claims become a constraint on the market. They describe the thing a competitor must do to deliver the same benefit to the same customer. They block the path, not document the journey.
Most patent applications never make this shift. Not because the attorney is incompetent. Not because the inventor is careless. Because nobody in the room asked the question that actually matters: what does the competitor’s product look like?
The inventor described what they built. The attorney drafted claims around what was described. And the patent reads on exactly one product in the world — yours.
Why Inventors Cannot See It
Inventors are myopic. Not because they lack intelligence — because they work inside constraints.
Legacy systems. Existing hardware. Software stack limitations. Vendor lock-in. Integration requirements with three other products that nobody outside the company has ever heard of. The inventor’s solution was shaped by all of these forces. It is optimized for their environment.
And because it is optimized, it feels inevitable.
The myopic inventor sees their solution as the only possible, the only logical, and the only rational approach. Ask them if there is another way to solve the problem and they bristle. Of course there is not. This is the way.
They are not wrong — about their own context. The solution is probably optimal given their constraints.
But their constraints are not universal.
The competitor does not have your legacy database. The competitor did not inherit your middleware from an acquisition four years ago. The competitor is not building on top of a platform that was designed in 2014 for a different use case.
A patent built around a workaround to your legacy database architecture is commercially useless. Nobody else has your legacy database.
The inventor is too close to their own environment to separate what is essential from what is incidental. The attorney does not know the competitive landscape well enough to push back. Someone with both IP expertise and market knowledge has to sit in the middle — someone who can look at the inventor’s solution and ask: what part of this is universal, and what part of this is just you?
The Revenue Mapping Filter
Patent value does not start with the technology. It starts with the customer’s buying decision.2
A patent covering why someone buys the product has value. A patent covering features unrelated to the buying decision is worthless.
Not less valuable. Worthless.
Nobody buys technology. Customers buy a solution to a problem. They buy the outcome. They buy the benefit. The technology is the delivery mechanism — and unless the patent covers the mechanism that delivers the benefit the customer is paying for, the patent has no commercial teeth.
Edison did not patent the light bulb. Twenty people had patents on light bulbs before him. His patent was on the carbon filament — the last piece that made incandescent lighting actually work at commercial scale. The filament was the reason a customer would choose his product. The patent sat on top of the buying decision.
Apple’s Slide to Unlock did not come from a brainstorming session. No whiteboard exercise would have generated it. It was the kind of insight that only surfaces from the heavy lifting of actually building the product — from watching real users interact with a real device and understanding what mattered.
File your second patent, not your first.
The first patent is a guess. It is filed before you have customer data, before you understand the competitive landscape, before the market has told you what matters. The second patent is based on data — from customers, from competitors, from the reality of what people actually pay for.
Revenue mapping connects patent investment to customer purchasing decisions. If you cannot draw a line from the claim to the feature to the revenue, the patent does not serve the business.2
How to Actually Do It
The process starts with competitors, not with your product.
Name specific competitors. Not “the market.” Not “potential entrants.” Actual companies with actual products competing for your customers right now.
For each competitor, describe how they would implement the same feature. What does their version look like? What technology stack are they using? What constraints do they face that differ from yours?
Now strip away everything specific to your implementation. Your database. Your API. Your manufacturing line. Your software framework.
What remains — the common thread across all implementations, yours and every competitor’s — becomes your independent claim. That common thread is the constraint. Everything else is noise.3
Key questions for the analysis:
- How would Competitor X build this feature with their technology stack?
- What constraints do they face that differ from yours?
- What would the market look like in two or three years — and would the claim still cover the dominant approach?
- If a competitor tried to avoid this claim, what would they have to change, and would that change be commercially viable?
Every unnecessary implementation detail narrows scope and creates an avenue for the competitor to circumvent.
Consider Amazon’s One-Click patent. E-commerce in the late 1990s faced a contradiction: customers abandoned carts because checkout was painful, but the standard solution — multi-page forms, re-entering shipping and payment information — was the only approach anyone used. Amazon went the other direction. One button. One click. Purchase complete.
Barnes and Noble spent millions in legal fees just to keep using the feature. They could not design around it — not because the technology was complex, but because the patent captured the single best way to solve the customer’s problem. Any alternative was meaningfully worse.
The patent did not describe Amazon’s server architecture. It described the customer experience that every competitor needed to offer.
A useful lens for evaluating design-around risk is a simple scoring scale. At one end: a superior alternative exists and the competitor can switch easily — the patent has no teeth. At the other end: your claim covers a ten-times advantage, competitors are locked in, and any workaround degrades the product. Most patents should aim for the high end of that scale. If a competitor can design around your claim without meaningful cost or degradation, the patent is a filing fee, not a business asset.
Every Word Narrows
Every word in a patent claim narrows the scope. Every element is one more thing a competitor must practice to infringe — and one more thing they can change to design around.
There is an old joke in the Patent Office: when a claim is longer than your hand, it must be allowable — because it is so narrow that nothing in the prior art could possibly match all those limitations.
Long claims are worthless.
An independent claim over 150 to 200 words is almost always over-specified. It names specific materials when the invention works with any material. It recites specific temperatures when the range does not matter. It calls out specific software languages, specific protocols, specific database structures — elements that feel precise and technical but add nothing except narrowness.
The functional test for each element is simple: would a competitor need to include this exact element to achieve the same customer benefit?
If no, it should not be in the independent claim.
Every element you remove is one less thing a competitor can change to design around you. Every element you keep is a gift to the competitor’s attorney — one more axis of freedom for them to exploit.
The competitor perspective strips those extra words out. When you draft from the competitor’s viewpoint — what must they do to deliver the same benefit? — the unnecessary elements become obvious. The specific materials, the specific temperatures, the specific protocols. None of them are part of the competitive constraint. They are artifacts of your implementation. They belong in the dependent claims at most, not in the independent claim that defines the scope of your exclusionary right.
Your Attorney Cannot Do This Alone
Your attorney sits nowhere on your sales calls. Does not see the CRM. Does not know which competitors are gaining ground or which features drive purchasing decisions.
The hardest parts of patent value lie upstream of drafting. Revenue mapping. Competitive analysis. The voice of the customer. Understanding which features matter commercially and which are table stakes. Knowing what the market will look like in three years — not what it looked like when the inventor started building.
These are business questions, not legal questions.
The attorney’s job starts when the strategic target is defined. They take a named competitor, a described product, a clear constraint — and they draft claims that read on the competitor’s product. Claims that survive design-around attempts. Claims that hold up during prosecution. Claims with commercial teeth.
Without that upstream work, the attorney drafts in the dark. The inventor describes what they built. The attorney writes what was described. And the default output — a patent on your product, not your competitor’s — is the inevitable result of a process that never asked the right question.4
The inventor came in with a product.
A Chief IP Officer turns it into a constraint on the market.
Then — and only then — does outside counsel start drafting.
1 The distinction between documenting your product and constraining a competitor’s is covered in Characteristics of Patents for Designing Good Business Assets in Investing in Patents.
2 Revenue mapping — connecting patent investment to customer purchasing decisions — is covered in detail in The Tradeoffs and Considerations for Patents in Investing in Patents.
3 The reframe from “what did we build?” to “what will they copy?” — and the analytical process behind it — is covered in Describe the Competitor’s Product in Investing in Patents.
4 Why attorneys cannot perform this analysis alone — and the structural gap between business strategy and patent execution — is explored in Your Patent Attorney Is NOT Giving Business Advice.