Skip to content
Ask Claude about any Chrome extension, answered with Ext Watch data. See how →
Build and launch

Hire a Chrome extension developer: costs and a checklist

Before you hire a Chrome extension developer, check four things: a shipped Manifest V3 extension, permission habits, account ownership and a review plan.

By Ext Watch Research6 min read
Pip, the blue bird mascot, holding a blank clipboard while inspecting a friendly white robot builder holding a wrench

The short answer

Look for a shipped Manifest V3 extension you can install, a habit of asking for few permissions, and a clear plan for review delays. That's the core of how to hire a Chrome extension developer. Cost depends on scope more than rates: a backend, billing and sync can triple a simple build.

  • Ask for a live listing link, then install it yourself.
  • Manifest V3 is the only game now: over 99.9% of extensions in the store.
  • Fewer permissions means faster review and more trust.
  • You must own the developer account and the code repo.
In this guide12 sections
  1. 01What to check before you hire a Chrome extension developer
  2. 02Manifest V3 isn't optional
  3. 03What really drives the price
  4. 04Write the scope as a short brief
  5. 05A small paid trial
  6. 06What to ask for at handover
  7. 07After launch
  8. 08Freelancer, agency or in-house
  9. 09Red flags in proposals
  10. 10Checking a candidate's shipped work
  11. 11Questions worth asking in the call
  12. 12Questions people ask

The demo looked perfect on their laptop. Then review took two weeks, came back with a permissions note, and nobody knew whose account it was under. That's the hire you want to avoid. Here's how to hire a Chrome extension developer without that story.

What to check before you hire a Chrome extension developer

CheckGood signRed flag
Shipped workA live listing link you can installOnly screenshots or a GitHub repo
Manifest versionTalks about service workers comfortablyMentions background pages as current
PermissionsAsks "do we need this?"Requests <all_urls> by default
Account ownershipYou create the account, they get accessThey publish under their own account
Review planBuilds in time for store reviewPromises a fixed launch date

Install their last extension. Five minutes with a real build tells you more than any portfolio page. The build itself is covered in our Chrome extension development guide.

Manifest V3 isn't optional

Across the roughly 270,000 extensions in the store, over 99.9% declare Manifest V3 and only about ten still report V2. Anyone pitching you V2 patterns is pitching old code.

You can check these figures on the Developer Tools category page, each with the day we saw it.

What really drives the price

Hourly rates vary a lot by region, so we won't quote one. Scope is what you control.

  1. Popup or content script onlyNo server. The smallest job.
  2. Plus a backendLogin and stored data. Now it's two codebases, as our Chrome extension SaaS guide shows.
  3. Plus billingStripe or a wrapper, webhooks, plan checks.
  4. Plus sync and teamsAccounts across devices, shared workspaces.

Write the scope as user actions, not features. "User highlights text and saves it to a list they see on their phone" prices itself better than "sync support."

Write the scope as a short brief

A clear brief gets better quotes and fewer surprises. One page is enough.

SectionWhat to write
The jobOne sentence on what the user gets done
User actionsThree to six steps, in the user's words
Sites it works onAll sites, or a named list
DataWhat's stored, where, and for how long
Accounts and billingNeeded or not, and which provider
Done meansLive in the store, with a short handover

The "sites it works on" row affects permissions, review time and price. If the tool only works on a few sites, say so. It keeps the build smaller and the install prompt friendlier.

A small paid trial

For anything beyond a tiny job, a short paid trial saves both sides from a bad fit. Pick a slice of the real work, like the popup or one content script, and pay for a day or two.

Look at how they communicate, not just the code. Did they ask about permissions? Did they flag anything that might slow review? Did they hand over something you could install?

What to ask for at handover

The handover is where projects quietly go wrong. Ask for these before the final payment.

  1. The code in your repo, with a readme that explains how to build it.
  2. A list of every permissionand the feature that uses each one.
  3. Every account and keythe product depends on, in your name.
  4. The store listing textand screenshots as files.
  5. A short note on known limitsand what might break.

If you can't build and publish the extension yourself from what you received, the handover isn't done.

After launch

Extensions need upkeep. Chrome changes, sites change their layout, and users find bugs. Agree up front how you'll handle that.

  • A small monthly retainer for fixes, or an hourly rate for ad hoc work.
  • A response time for anything that breaks the main feature.
  • Who replies to reviews and support email.

You can see how often similar tools ship updates on our niche pages. Across the store, roughly 1 in 7 extensions had an update in the past 30 days, and about two thirds were updated in the last year. Plan for at least that.

Freelancer, agency or in-house

Who you hire changes cost, speed and risk. Here's a rough comparison.

OptionGood forWatch out for
FreelancerSmall, clear scopesAvailability after launch
AgencyLarger builds with design and backendHigher cost, handoffs between people
In-house hireOngoing product workHiring time, full-time cost
Co-founderEarly products with no budgetEquity and alignment

For a first version of a focused extension, a freelancer with shipped extensions is often enough. Bring in more help once the product has users and a clear roadmap.

Red flags in proposals

Proposals tell you a lot before any code is written. Watch for these.

  • No questions about permissions or which sites the tool works on.
  • A fixed launch date that ignores store review.
  • Publishing under their own account.
  • Vague maintenance terms, or none.
  • Remote code or obfuscation proposed to "protect" the code. Store policy bans hidden logic.

A good proposal asks about your users, flags review risks and suggests cutting scope. That last one is the clearest sign of experience.

Checking a candidate's shipped work

Ask for links to live listings, then check them like a user would.

  1. Install itand use the main feature.
  2. Look at the permissionsin chrome://extensions.
  3. Check the update historyon the listing.
  4. Read recent reviewsand the developer's replies.

A developer whose tools are well rated, recently updated and answered in reviews is likely to treat yours the same way. You can look up any listing's version, permissions and update date on our extension pages.

Questions worth asking in the call

  • How would you handle a rejected review?
  • Which permissions does this idea need, and which can we avoid?
  • Where does plan status get checked: client or server?
  • What breaks if Chrome changes an API next quarter?

We're biased toward research before code. If your niche already has well-rated tools, their publishers are often the most experienced developers you can find.

Then ask them about it. How they answer is the demo that matters.

Questions people ask

How much does it cost to hire a Chrome extension developer?

It depends on scope and region. A popup with no server is a small job. Login, billing and sync turn it into a small SaaS build. Get quotes against a written scope.

Where can I find Chrome extension developers?

Freelance marketplaces, developer communities and the store itself. Publishers of well-rated extensions in your niche are worth contacting directly.

Should I hire a web developer instead?

A good web developer can learn it, but extension rules around permissions, service workers and review add real gotchas. Ask for a shipped extension.

Should I pay a fixed price or hourly?

A fixed price suits a small, clearly written scope. Hourly suits work with unknowns, like a backend or tricky site integrations. Either way, split it into milestones.

Who should own the code?

You should. Put it in writing, keep the repo in your account, and make sure the developer account and domain are yours too.

Ext Watch logoExt Watch ResearchBuilt from Ext Watch’s own store data
Developer Tools

31,127 extensions tracked in Developer Tools. See them all.

Start from a niche with proven demand instead of a blank page.Store data, updated today

Ask Claude about this dataPlans from $19/mo