Shipping 43 Chrome extensions with Claude Code: what the numbers showed and why 22 came down
A solo developer used Claude Code to build 43 Chrome extensions from AI-suggested ideas, then published every number: 22 taken down, about $107 plus 3,480 yen in external revenue over nine months.
Evidence: The author reports this. We have not checked it beyond reading the source.
The business problem
A solo builder wants to know whether mass-producing small AI-built products on a store like the Chrome Web Store leads to paying users.
What was tried
The author gave Claude Code instructions in Japanese and wrote no code personally. Extension ideas came from AI-generated candidate lists, chosen mainly because they looked easy to build, with shallow competitor research. Several projects ran in parallel and operations became the main job. User counts were pulled into a database daily. On 28 and 30 September the author reviewed each extension and decided to keep it free, run a four-week paid test, or take it down; 17 of the 22 takedowns were a batch removal on 1 September for zero lifetime revenue. One idea (DataPick) was dropped before launch because only 4 of 12 tested sites returned named rows. The author then narrowed to two extensions for a four-week test and will post the result.
What was reported (mixed)
43 extensions shipped, 22 removed, 21 live. Weekly users on live ones ranged from 2 to 435 (the top one is free by design). External revenue for live extensions from January to September 2026 was 3,480 yen plus $106.75, with four active subscriptions in total. Installs did not turn into use, and billing and upgrade flows broke when the author had close to 40 extensions.
Limitations
Self-reported figures with no inspectable dashboards; one developer in one market. The author says too much judgment was handed to AI and too little research was done, so this is as much a cautionary account as a method. The two-extension paid test had no result yet. Originally published in Japanese on Zenn and cross-posted.
What you need
Claude Code or similar, a Chrome Web Store developer account, a way to count users and revenue.
Sources
- DEV Community (ktg0215) ↗ Firsthand write-up, published October 20, 2026
Source published: October 20, 2026. Last reviewed here: October 20, 2026. Spot a mistake? Tell us.
Tools in this workflow
- Claude Code: Wrote all the extension codeTry Claude Code
- Chrome Web Store: Distribution channelTry Chrome Web Store
Get new workflows like this by email
A short selection of the most useful new workflows, including the ones that did not work. Free, and you can unsubscribe at any time.
Related workflows
Run an AI vector-art stock asset pipeline but keep four human checkpoints: keywords, upload go-ahead, image review and pricing
A solo seller produced 39 vector asset packs for Adobe Stock, Vecteezy and Dreamstime with an AI prompt engine and Python scripts, and explains which steps they automated and which stayed manual after costly mistakes.
Get a weekly Claude Code report that links shipped pull requests to KPI changes and scores the likely impact
A product lead connects Claude Code to Metabase and GitHub so each week it compares 5 to 10 KPIs with last week, maps the week's pull requests to them with a confidence score, and recommends next steps.
Stress-test a go/no-go decision on your company idea with two AI memos and a written kill criterion
A developer with 21 months of work behind a trading system had Claude and Cursor's agent each write a verdict memo against five pre-set gates, then tried 25 counterarguments. Both said not to found a company.
Connect an AI agent to a merchant-of-record so it can create products and checkout links without owning tax
A vendor tutorial for letting Claude or another agent create a product and a checkout link through a merchant-of-record, so VAT and sales tax are not the founder's filing job.