
He feeds expired patents to Claude. $0 for the blueprint. $1.80 to manufacture. $11.99 on Amazon.
AI features
- Views
- 3.4M
- Likes
- 1.8K
- Reposts
- 158
- Comments
- 65
- Bookmarks
- 6.3K
TL;DR
This guide details a system using Claude to scan millions of expired USPTO patents, identifying high-potential consumer products that are now public domain and ready for low-cost manufacturing and resale.
Reading the ENGLISH translation
I feed expired patents to Claude. Found 6 products nobody manufactures anymore. First one is already in production.
Most people use AI to write emails and summarize PDFs.
I pointed it at the US Patent Office.
The idea came from a rabbit hole.
I was reading about a company that got sued for patent infringement on a kitchen gadget. Lost $2.3 million in settlement.
Then I checked the patent filing date.
It expires in 18 months anyway.
That got me thinking.
What happens to all the patents that already expired?
Not the big ones. Not pharma blockbusters or chip designs.
The small ones. The boring ones. The ones filed by a guy in Ohio who invented a better planter insert and then went bankrupt before it mattered.
I looked it up.
Over 4.2 million US patents expired in the last decade alone.
Not rejected. Not failed. Expired.
The owners either went bankrupt, forgot to renew, or decided the product was not worth protecting anymore.
Every single one of those patents is now public domain.
Free to use. Free to manufacture. Free to sell.
Nobody cares. Nobody looks at them.
Part 1 — The Pipeline
The problem was never access.
The USPTO publishes everything through their Bulk Data portal — full text, full drawings, full claims. Every detail you need to rebuild a product from scratch.
USPTO Bulk Data — full patent database, public domain, free
The problem was volume.
Nobody reads 4 million patents for fun.
I decided Claude would.
The first week was just infrastructure. Nothing fancy.
A Python scraper pulling expired utility patents from the Bulk Data API.
The filter logic:
python
1# patent_filter.py — first pass23FILTERS = {4 "status": "expired",5 "type": "utility", # skip design patents6 "assignee_size": "small", # no IBM, no Samsung7 "categories": [8 "household",9 "tools",10 "pet_products",11 "office_supplies",12 "garden",13 "kitchen"14 ],15 "expired_after": "2014-01-01",16 "min_claims": 3,17 "max_claims": 25 # too many claims = too complex18}
I specifically wanted patents from small to mid-size companies.
Not IBM. Not Samsung. Not Qualcomm.
Small companies where the tech is simple enough to manufacture independently. Consumer products. Hardware. Tools. Home goods.
To convert the raw patent files into something Claude could actually process, I used markitdown — strips any document format down to clean Markdown.
microsoft/markitdown — convert any file to Markdown for Claude context, 38K+ stars
That first filter gave me roughly 340,000 candidates.
Still way too many to read manually.
Part 2 — The Claude Filter
This is where it gets interesting.
I built a scoring pipeline. Each patent goes through Claude with a structured prompt.
The system prompt:
plaintext
1ROLE: Patent Commercial Viability Analyst23INPUT: Expired US utility patent (full text + claims)45ANALYZE AND RETURN:6─────────────────────────────────────────71. PLAIN_ENGLISH: What does this actually do?82. CONSUMER_VIABLE: Could a consumer version exist? (yes/no)93. BOM_ESTIMATE: Bill of materials at 1000 MOQ (Alibaba)104. AMAZON_GAP: Does any current listing use this exact mechanism?115. REVIEW_SIGNAL: What do competing product reviews complain about?126. SCORE: Commercial viability 1-101314REJECT IMMEDIATELY:15- Requires FDA/FCC clearance16- Needs custom semiconductor fab17- Chemical formulation patents18- Software/algorithm patents19- Requires tooling over $50K2021RETURN FORMAT: JSON only. No commentary.
I ran batches of 50 patents at a time.
Each batch took about 90 seconds to process.
For batching the files into prompt-ready chunks, I used files-to-prompt.
simonw/files-to-prompt — pack your entire project into a single prompt for Claude, 3K+ stars
Sample output:
json
1{2 "patent_id": "US8,234,811",3 "plain_english": "Self-watering planter insert with passive4 felt wick. Pulls moisture from reservoir to soil via5 capillary action. No pump, no battery.",6 "consumer_viable": true,7 "bom_estimate": "$1.60-2.10 at 1000 MOQ",8 "amazon_gap": true,9 "review_signal": "Competing products: water pools at bottom,10 wicks clog after 2 weeks, not optimized for small pots",11 "score": 812}
The results were mostly noise.
Score 1. Old semiconductor layouts nobody can use.
Score 2. Obscure chemical formulations that require lab equipment.
Score 1. Telecom switching protocols from 2004.
Score 1. Medical imaging calibration tools that need FDA clearance.
Score 1. Score 1. Score 2. Score 1.
Hundreds of patents. All garbage for consumer products.
But roughly 1 in 80 came back with a score of 7 or higher.
Those were the ones.

Part 3 — The Hits
Hit #1 — Self-watering planter insert
Passive wicking system. No pump. No battery. No moving parts.
Originally patented in 2009 by a garden tools company out of Ohio. Small operation, 12 employees.
The company went bankrupt in 2016.
Patent renewal fee: $1,600. Nobody paid it. Patent lapsed.
Nobody picked it up.
I checked Amazon.
Plenty of self-watering planters on the market. Dozens of listings.
But none of them used this specific wicking design.
The patented version was simpler to mold, cheaper per unit, and actually performed better for indoor herbs because the wick diameter was optimized for small soil volumes.
The reviews on competing products told the story.
"Water pools at the bottom." "My basil still died." "Wick stopped working after 2 weeks."
The patented design solved exactly those problems. The inventor had clearly tested it.
And the patent document said so — with diagrams, measurements, and material specifications.
I found the original patent on Google Patents, which lets you filter by expiration status and see the full filing with drawings.
Google Patents — searchable patent index with expiration status filters
I contacted three manufacturers on Alibaba.
Sent the patent drawings directly.
Because that is the thing about patents.
They are literally manufacturing instructions written in legal language.
Dimensions. Tolerances. Materials. Assembly order. Everything a factory needs to quote production.
First quote came back: $1.80 per unit at 1,000 MOQ.
Current Amazon average price for "self-watering planter insert": $14 to $22.
Monthly search volume for the category: 118,000.
I ordered samples.

Hit #2 — Collapsible pet water bowl
Not just any collapsible bowl. This one had a one-hand locking mechanism.
Snap open. Snap closed. No hinges. No silicone folding. No moving parts that break.
Patented in 2011 by a pet products startup out of Austin, Texas.
The startup raised a small seed round. Built the product. Got it into a few stores.
Then ran out of money in 2019. Shut down. Patent lapsed.
I checked Amazon again.
The pet travel bowl category is massive. Thousands of listings.
But every single one uses either cheap silicone folding or plastic hinges.
The reviews on the top sellers are brutal.
"Hinge broke after a month." "Silicone stinks and my dog won't drink from it." "Collapsed in my bag and leaked everywhere."
The patented lock design fixes all of this. One snap. Rigid when open. Flat when closed. No parts to fail.
plaintext
1Product Comparison — Collapsible Pet Bowls2──────────────────────────────────────────────3 Patent Design Amazon Top 54Mechanism: snap-lock silicone fold5Moving parts: 0 2-46Failure rate: ~2% ~31% (per reviews)7Unit cost (1K MOQ): $0.95 $1.40-2.208Holds shape: yes collapses under weight9One-hand use: yes no
Alibaba quote: $0.95 per unit.
Amazon price range for collapsible pet bowls: $8 to $15.
The margins are absurd.
Hit #3 — Cable management clip
Adhesive base. Ratcheting jaw that adjusts to cable width automatically.
Patented in 2007 by an office supplies brand.
The brand got acquired in 2013. The new owner looked at the patent portfolio, decided half of it was not worth renewing, and let it lapse.
Including this one.
The ratchet design holds cables from 2mm to 12mm without swapping clip sizes.
Every cable clip on Amazon right now is either fixed-size or uses a generic flexible rubber slot that loosens after a few months.
I checked the reviews on the top 10 cable clip listings.
Same complaint. Over and over.
"Doesn't hold my thick charging cable." "Too loose for thin earphone wires." "Keeps popping out."
The patented ratchet jaw solves this mechanically. No rubber. No stretching. Just a stepped angle that grips tighter as the cable gets thicker.
plaintext
1Unit Economics — Cable Clip (30-pack)2──────────────────────────────────────────3Production (30x $0.12): $3.604Packaging + label: $0.405Shipping to FBA: $0.856Amazon FBA fee: $3.207PPC (estimated): $1.108─────────────────────────────9Total cost: $9.1510Sale price: $11.9911Net margin: $2.84 (23.7%)1213At 800 units/month: $2,272/mo net
Part 4 — The Results
I found 6 products like this in 3 weeks of running the pipeline.
Three are in sample stage right now.
One — the planter insert — is already approved. Production run started. Amazon listing in prep.
Target price: $11.99.
Projected margin after PPC and FBA fees: 44%.
From an expired patent that cost $0 to access.
Part 5 — The System
The setup looks simple from the outside.
A scraper. A filter. Claude. A prompt. Alibaba.
No proprietary data. No expensive software. No team. No office. No research lab.
The full pipeline:
plaintext
1USPTO Bulk Data API2 │3 ▼4 Python Scraper (filter by category, assignee, date)5 │6 ▼7 markitdown (convert to clean Markdown)8 │9 ▼10 files-to-prompt (batch into context payloads)11 │12 ▼13 Claude Scoring Pipeline14 ┌─────────────────────────────┐15 │ System: Patent Analyst │16 │ Input: 50 patents/batch │17 │ Output: JSON scored 1-10 │18 │ Filter: score >= 7 │19 └─────────────────────────────┘20 │21 ▼22 Google Patents (verify + pull drawings)23 │24 ▼25 Alibaba (send drawings, get quotes)26 │27 ▼28 Amazon Listing
The Claude workflow itself was built using the Skills framework — reusable prompt templates that turn a one-off experiment into a repeatable system.
anthropics/claude-code-skills — official Skills/SKILL.md framework by Anthropic
For connecting Claude to external tools — the scraper, the supplier lookup, the review analysis — I used MCP.
anthropics/model-context-protocol — MCP, the standard for connecting tools to Claude
punkpeye/awesome-mcp-servers — catalog of 500+ ready-made MCP servers, 27K+ stars
And for the overall Claude Code agentic environment:
obra/superpowers — superpowers for Claude Code, 160K+ stars

Part 6 — Why This Works
Here is what most people miss about patents.
They think of patents as legal shields. Something lawyers deal with.
But a patent is also an engineering document.
To get a patent granted, you have to disclose enough technical detail that someone skilled in the field could reproduce the invention.
Dimensions. Materials. Assembly steps. Performance specs.
That is the entire point of the patent system. You get temporary protection. In exchange, you give the public a complete blueprint.
When the patent expires, the blueprint stays.
It becomes a free manufacturing manual.
But nobody reads them.
Because patent documents look like this:
plaintext
1"A fluid-wicking apparatus comprising a porous fibrous2member disposed within a reservoir cavity, wherein said3member maintains capillary continuity with a growth4medium positioned superiorly, characterized in that5the fibrous member exhibits a mean pore diameter of6between 40 and 120 micrometers..."
That is the planter insert.
Normal people see that and close the tab.
Claude reads it and returns:
json
1{2 "plain_english": "Felt wick inside a water tray that3 pulls moisture up into soil. Optimized for small4 indoor pots. Simple to injection-mold.",5 "bom_estimate": "$1.80",6 "score": 87}
That is the entire edge.
Not a better product idea. Not a smarter market thesis. Not some secret Amazon hack.
Just the ability to read documents that humans skip because they look like legal noise.
Four million expired patents.
Each one is a detailed instruction manual for a product that once worked.
Most of them are genuinely useless.
But some of them are products that sold well, had real demand, solved real problems — and simply stopped being made because the company behind them died.
The product did not fail.
The business did.
And nobody went back to check.
Most people search for things to sell by browsing Amazon trending pages.
They look at what is already popular and try to compete.
I do the opposite.
I search for products that were once valuable enough to spend $15,000 protecting — and that nobody remembered to keep making.
The ugly products. The boring products. The ones nobody scrolls back far enough to find.
That is a different game.


