How much to charge for a Chrome extension
How much to charge for a Chrome extension comes down to one question: how much faster or cleaner does this make the work the client's people already do in the browser? Nobody buys an extension for the popup. They buy it so a sales rep stops copying details from a profile into the CRM, so a support agent gets the right reply with one click, or so a team stops making the same mistake on a web form. Price the build on a share of that value, add lines for the sites it runs on, the systems it connects to and the store publishing, and quote a monthly plan for upkeep. Do not price it on the size of the code or on hours.
Extensions are good work to sell with Claude Code because the result is right there in front of the user every day. The trap is that a first version can be small and fast to build, so builders price it like a weekend job. Then the client's CRM changes its page layout, the button the extension depends on moves, and the extension quietly stops working with nobody paid to fix it.
Why the popup is the wrong yardstick
An extension that tidies one page for one person and an extension that every rep on a sales team uses dozens of times a day can be close to the same amount of code. Charging the same for both makes no sense. The client is paying for what the extension does to their team's day, not for how many files it has.
Hours are worse. Claude Code makes the first build fast, and if your price follows your hours, every bit of speed you gain becomes a pay cut. I covered this in why I stopped charging hourly for AI builds. The real costs of an extension sit around the code: getting it through the store, rolling it out to the team, and keeping it working when the sites underneath it change.
The CCC Extension Quote
Five parts of a Chrome extension quote
| Part | What it prices | Question to ask the client |
|---|---|---|
| Base build | The value of the workflow it speeds up | Who does this task today, how often, and what goes wrong? |
| Sites | Each website or web app the extension has to work on | Which sites does it need to run on, and which pages? |
| Connections | Each system it reads from or writes to | Where should the data come from and where should it go? |
| Store and rollout | Publishing, the listing, and getting it onto the team's browsers | Public, unlisted, or only for your team? Whose account publishes it? |
| Keep plan | Monthly monitoring, fixes and store updates | What happens to the team's day if it stops working? |
Base build. Work out with the client what the workflow costs today. That is people multiplied by how often multiplied by how long multiplied by what their time costs, plus whatever the mistakes cost when someone copies a field wrong. Price the build at a fraction of one year of that value, so the client can see it pay for itself early.
Sites. Every site is its own line. An extension that reads and changes a page depends on how that page is built, and each site has its own layout and its own way of breaking. One that works on a single CRM is a different job from one that has to work across a CRM, an inbox and a support desk. Pricing per site makes the quote easy to trim. How to build a Chrome extension with Claude Code shows what a single site involves.
Connections. An extension that only changes the page in front of the user is one thing. One that pulls data from the client's database, writes it into their CRM and calls an AI model on the way is three more lines, each with its own keys, permissions and failure points. If it calls a paid API, the key never ships inside the extension. It goes behind a server the client controls, with a login and a spending limit, and that server is part of the quote.
Price the Chrome Web Store work
Getting an extension into the client's browsers is real work, and builders forget to quote it. Publishing through the Chrome Web Store needs a developer account with a one-time registration fee, a listing, and a review by Google before anything goes live. Google's own guidance is that most reviews finish within a few days but some take a few weeks, and that extensions asking for broad access to websites or sensitive permissions can take longer to review.
- Visibility: the store offers public, unlisted (anyone with the link can install it) and private (only named testers or a group the client manages). Most client tools for one team should be private or unlisted. Every option goes through the same review.
- Ownership: publish under the client's own developer account, or move it to them at handoff. An extension living in your account is a problem for both of you the day the project ends. How to hand off a Claude Code project covers the checklist.
- Permissions: ask for only the sites and permissions the extension really needs. It is safer for the client's team, and it keeps the review simpler.
- Timeline: put the review window in the schedule, and never promise a go-live date that depends on the store answering in a day.
Always quote the Keep plan
Extensions break for reasons that have nothing to do with your code. The site the extension runs on changes a page, renames a field or moves a button. A connected tool changes how its data comes back. Chrome itself changes how extensions are allowed to work, which it has done before. None of that is your fault, and all of it stops the tool the team relies on.
Quote a monthly plan in the original proposal. Say what it covers: checking it still works on each site, fixing breakages from site changes, pushing updates through the store, and small tweaks. Say what it does not cover: new sites, new connections and new features, which are quoted separately. How to price a maintenance retainer covers the structure. An extension the whole team uses every day is one of the easiest retainers to justify, because they feel it the first morning it stops working.
How to present the Chrome extension quote
- Lead with the workflow in their words. One line on what the team does today and what it costs them, then the price.
- Itemize it. Base build, each site, each connection, store and rollout, then the Keep plan. Itemized quotes get trimmed, not rejected.
- Gate payments on proof. A deposit to start, a payment when a working version is running in the team's own browsers, and the final payment once it is live through the store. How to structure milestone payments for an AI project covers the schedule.
- Name what breaks it. Say plainly that changes to the sites underneath will break the extension at some point, and that the Keep plan is how it gets fixed fast.
Short, practical drops on skills, MCP, agents, prompts, and more. No spam, unsubscribe anytime.
Frequently asked questions
How much should I charge for a Chrome extension?
Price it on the workflow it speeds up: how many people use it, how often, and the time and mistakes it saves them. Charge a fraction of one year of that value for the build, add a line for each site and each connected system, add the store publishing, and quote a monthly plan for upkeep.
Should I charge hourly for a Chrome extension?
No. Claude Code makes the first build fast, so hourly pricing turns every gain in speed into a pay cut, and it ignores the store work and the upkeep that come after the code. Price on the value of the workflow instead.
Should I charge a monthly fee for a Chrome extension?
Yes. The sites the extension runs on change their pages, connected tools change, and Chrome changes its rules for extensions. A monthly plan covers checks, fixes and store updates, with new sites and features quoted separately.
Who should publish a client's Chrome extension?
The client, under their own Chrome Web Store developer account, or you move it to them at handoff. For a tool used by one team, publish it as private or unlisted rather than public. Every visibility option goes through the same Google review.
How long does Chrome Web Store review take?
Google says most extensions are reviewed within a few days, but it can take up to a few weeks, and extensions that ask for broad access to websites or sensitive permissions can take longer. Build that window into the timeline you quote.
Last reviewed by Duncan Rogoff on October 8, 2026
