After serving our first set of customers, we learned something simple: nobody starts out wanting to build a Chrome extension.

What people actually tell us is the thing they do in their browser every week that eats their time. Copying data into a spreadsheet. Checking the same pages for changes. Researching leads, listings or competitors. Tidying up text before it goes out.

That chore is the starting point. The extension is just how you get the time back, and we can guide you through building it, or build it alongside you.

So here's our bet: tell us one workflow you do by hand, and we'll show you how to get at least 2 to 3 hours a week back.

Email [email protected] with:

- what you do, step by step

- which sites you use

- roughly how long it takes you each week

We'll reply with whether an extension can do it and exactly how to build it with PlugThis. If an extension can't do it, we'll tell you that straight.

This week one buyer sent us exactly that: every image in a website saved, with their own naming convention with list of source files. Hours of copy-paste by hand. Now the extension collects the whole data and hands over the file.

What we've shipped since launch:

- A long list of fixes to the builder

- Discover, a library of free ready-made extensions you can download or clone and make your own: https://plugthis.ai/discover

Take the bet. One chore, one email.

Udaya

Founder, PlugThis

Hi Sumolings,

I have made a Loom video showing all the updates in our roadmap that we have completed. If there is something that you would like to see in our roadmap, please leave it as a question, and I will have it added to our roadmap. We will pick up things that the community votes.

https://www.loom.com/share/ccf4965e122d421fa29fe38170ebd6c5

If you face any challenges while building , email [email protected]. I will read and respond.

Hi Sumolings,

Some of you tried to download an extension this weekend and got an error saying the package asked for broader site access than the builder had shown you.

That was our mistake.

Here is what happened. When an extension puts its code into a page only at the moment you click it, it needs no website permissions at all. Our packaging step was adding "can read every website" anyway. A safety check we shipped last week spotted the mismatch and refused to hand over the file.

The check was doing its job. We were the ones creating the problem for it to catch.

Four people wrote in about it. Every one of them tried seven or eight times first, and very grateful they bothered, because that is how it got found. If you hit this and gave up without telling us, I am sorry. You were not doing anything wrong.

It was fixed and deployed this morning. If you were blocked, open your project, build again, and Test and Download should go straight through.

I have added 10 generations to every account, whether this affected you or not. They will appear EOD. They are top-up generations, so they never expire and they sit on top of your monthly allowance.

If anything is still not working, leave a comment here or email [email protected]. I will read and respond.

🎉 Every single thing in Next up goes live in the next 24 hours. All eight of them.

Here is what is landing:
*********************************

✏️ Allow code change in editor — edit your extension's code directly, no generation spent.

🐞 AI to fix a runtime bug — paste the error, it fixes the project.

⚠️ Tell me when Chrome breaks my extension — we watch Chrome's changes so you do not have to.

🔀 Add OpenRouter support — bring your own model (For AI generations).

🎚️ Per-user and per-workspace generation limits — stop one person spending the whole month.

📖 Plain-English change history — version history that says what changed, in words.

🧹 Memory leak guard for sidebar extensions — side panels clean up after themselves now.

⭐ A quality bar for the Marketplace — a floor on what gets listed.

______________________________

Now the part that matters.
______________________________

🙏 Not one of these was Our idea.

Every single one came from somebody on this page. A question in the Q&A, an email at two in the morning, a review that was honest about what was annoying.

One of them came from a customer who had built more extensions than anyone else and told me plainly that he could not tell his versions apart.

Eight days ago this product did not have a roadmap worth reading. You wrote it. We just built it.

🗳️ So please keep going. feedback.plugthis.ai/roadmap — vote for what you need. Email us at [email protected] or reply to me in comments and I will add them to the list.

Thank you, genuinely. This has been the best week of building we have had.

PlugThis builds Chrome extensions. That is the only thing it does.

People use it for screenshot tools, QR code generators, CSS inspectors, and
anything that reads the page you're on and does something with it: pull data out
of a dashboard, summarise an article, fill a form, add a side panel to software
your team already uses.

You can also wire in APIs you already pay for. Open a LinkedIn profile, send it
to an enrichment service, get the contact details back in the page. Same for
anything else that has an API and a key.

It works like a conversation. You describe the extension you want, PlugThis
builds it, and every build gets loaded into a real Chrome before you download it
so you know it runs. If something is wrong, you say what to change and it
rebuilds.

You get all the code. Change it, sell it, or publish it to the Chrome Web Store
under your own name. If your extension uses AI, it runs on your own API key.

Udaya Prakash
Founder