Tell us what it should do. We design it, build it, get it through Chrome Web Store review and keep it working after launch — including payments if you want to charge for it. You own the code and the listing.
All of it our own work — live on the Chrome Web Store, installable in one click.
Most people who write to us are in one of these situations.
You have the idea, not the developer. You know exactly what the extension should do — you just need someone who can actually ship it.
Your extension stopped working. A Chrome update or an API change broke it, users are leaving reviews about it, and nobody is maintaining it.
The Web Store rejected you. You got the email, you are not sure which rule you broke, and resubmitting blindly is not working.
You want it to make money. Free users are fine, but you have no idea how to add accounts, limits and recurring payments without breaking things.
You started it yourself and got stuck. The prototype works on your machine, but shipping it to real users turned out to be a different job.
Nobody is finding it. The extension is live, it works, and it is getting almost no installs because nothing points people to it.
If one of these is you, tell us about it — we will tell you honestly whether we are the right people for it.
From a single-purpose tool to a full product with paying users.
Manifest V3, the permissions reviewers accept, the edge cases users hit. Need it on Firefox and Edge too? That is a build option, not a rewrite.
Sign-in, free vs premium limits, checkout, renewals, failed-payment recovery. If you want your extension to earn, this is the part most people underestimate.
Listing, screenshots, privacy disclosures, permission justifications and the review process itself — including what to do when a submission gets rejected.
A landing page that actually ranks, in as many languages as your market needs. An extension nobody can find does not get installed.
Anyone can write code. The risk is what happens after you pay for it.
We have been through Chrome Web Store review 31 times — permission warnings, privacy requirements, single-purpose rules. We know which ones are negotiable and which ones get you removed.
Our own extensions pay our bills, so we think about the things that decide whether yours survives: retention, refunds, support load — not just shipping a build.
Most of what we build runs entirely in the browser. Fewer permissions means easier review, fewer scary warnings on your listing and more people who actually install.
Platforms tighten rules and APIs shift overnight — extensions break. We have handled exactly that on live products with thousands of daily users watching.
Not case studies from years ago — every one of them is live right now.
No month of silence, no surprise invoice at the end.
What it should do, which sites it touches, what permissions that forces. Most ideas get simpler here — and cheaper. If it cannot pass review, you hear it now, not later.
A working build you load in your own browser before the polish. Changing direction here costs a conversation. Changing it after launch costs a lot more.
Interface, edge cases, error states, billing if you need it. You see it progress as it happens — no month of silence followed by a big reveal.
Listing, assets, privacy disclosures and the submission — handled for you. If it gets rejected, fixing that is part of the job, not a new invoice.
Browsers update, rules change, APIs move. We stay reachable for the part most agencies treat as someone else's problem once the invoice clears.
The questions that come up in almost every first email.
A focused single-purpose extension is usually a matter of weeks; one with accounts, subscriptions and a marketing site takes longer. Scope drives everything, so we would rather look at your idea than quote a number blindly.
Per project, after we understand the scope. We will tell you honestly if what you want is simpler than you think — or if the Chrome Web Store will never approve it.
It happens, even to well-built extensions. We read the rejection, fix the cause and resubmit. Having gone through review 31 times, we usually know the reason before the email finishes loading.
You do. The extension is published under your developer account and the source is yours.
Yes. Broken builds, Manifest V3 migrations and abandoned codebases are familiar territory.
Yes — landing page, multilingual content and the SEO foundation underneath it. This site is the example.
A few sentences is enough to start. We will tell you what it takes — and if we are not the right people for it, we will say that instead of selling you something.
Tell us your idea