A Chrome extension company that ships can prove it: live extensions in the Web Store they still maintain, Manifest V3 in production, and a plan for the day Chrome breaks the service worker. Here's the evidence to demand, the company types compared, and how to avoid the abandon trap.
A Chrome extension development company that actually ships can hand you three proofs: a live extension in the Web Store they built and still maintain, a straight story about a submission that got held for manual review and how they cleared it, and a Manifest V3 back end they secured. If a company can't point to something running today — only launch screenshots and a portfolio page — you're hiring for the demo, not the ship.
"Who do I hire for a Chrome extension" is really the question "who has done this on the platform, through review, and kept it alive after Chrome changed the rules." That's a narrow skill, and most companies bidding on extension work are generalists treating it as a checkbox. Below is the shipping evidence to demand, how the realistic company types compare, and how to avoid paying for an extension that gets abandoned the day it launches. If you'd rather hire an individual, see how to hire a Chrome extension developer; for the numbers, see what a Chrome extension costs. Duskel builds Chrome extensions and ships its own.
"We ship" is easy to say. Make a company prove it against the specific things that break extension projects. Every row here is evidence a company that genuinely ships can produce on request — and a gap a slide-deck agency can't paper over.
| What to demand | What "ships" looks like | What abandonment looks like |
|---|---|---|
| A live, maintained extension | A Web Store listing they built that's still updated, with recent version history | A launch screenshot and a case study for something no longer running |
| Web Store review scars | A specific story of a submission held or rejected, and how they fixed it | "We've never had a rejection" — usually means never shipped anything with real permissions |
| MV3 in production | They talk about the service worker dying mid-task, losing state, and the ban on remote code | They describe the popup and options page and stop there |
| The back-end half | A secured server, auth inside a service worker, and AI proxied so the key never ships | "The extension will just handle it" — accounts and syncing never scoped |
| A maintenance relationship | A retainer or paid-fix plan for when Chrome updates or a site redesign breaks selectors | Silence on upkeep — you're buying a launch, not a working product |
The most expensive company is the cheap one that ships an extension which passes review, then vanishes when Chrome's next update silently breaks the service worker for a third of your users. Rescuing an abandoned extension can cost more than building it right the first time.
Three kinds of company will pitch you, and they ship differently. A studio that specialises in extensions — ideally one that runs its own — has already paid for the platform's mistakes. A generalist software agency can build the back end but often underestimates the content script that is the whole point. An offshore body shop is cheapest per hour and can be fine for a bounded tool, but MV3's quirks and Web Store review are exactly where a rotating cast learns on your budget.
| What you're buying | Specialist extension studio | Generalist software agency | Offshore body shop |
|---|---|---|---|
| MV3 lifecycle expertise | Core competency — cold-start bugs designed out | Usually shallow; learned on your project | Hit or miss; verify hard |
| Web Store review | Been through it repeatedly; scopes permissions to pass first time | Sometimes; often first hits rejection at submission | Frequently learns the process on your timeline |
| Back end + auth | Built to production standard, secured | Yes — this is their strength | Varies widely by who's staffed |
| Continuity after launch | Expects to maintain it | Contract-dependent | Often gone once the invoice clears |
| Best fit | The extension is the product, or has a back end/AI | Extension is one piece of a larger platform build | A simple, bounded, front-end-only tool on a budget |
None of these is wrong. If your idea genuinely fits in a popup and touches only the current tab, don't overpay a specialist studio for it. The mismatch that costs money is hiring a body shop for something that needs a secured server, or a generalist agency for something whose entire value is a tricky content script they'll wave off.
Most extension projects that stall showed the warning signs in the first call. Slow down when you hear these from a company:
We build Manifest V3 extensions, and — the part that matters — we run two of our own in the Web Store. KeepChats is our Reddit power-suite; Gwora is an AI co-pilot for Upwork freelancers. Every trap on this platform, from service-worker lifecycles to content-script clashes to a submission held for manual review, we've already hit on our own products, on our own dime, before it ever reached a client build. That's what "a company that ships" means: not a case study, software we personally depend on and keep alive.
Practically, that changes how we scope. We argue you down to the narrowest permissions that survive review, we treat the service worker as disposable so it doesn't fail silently, and we build the back end to the standard we hold our own products to. We're a small senior team, so the person you talk to is the person who builds it — no handoff to a junior after you sign. If you have an extension idea and want a straight answer on who should build it and what it costs, tell us what you're trying to do — even when the honest answer is "a freelancer is fine for this one."
Demand evidence, not a portfolio. Ask for a live extension they built that's still in the Web Store and still updated, with recent version history. Ask for a specific story of a submission that was held for manual review or rejected, and how they cleared it. And ask what they do the day Chrome's update breaks the service worker. A company that ships answers all three concretely; one that only has launch screenshots is selling the demo.
It depends on the extension. For a genuinely simple, front-end-only tool that lives in the current tab, a good freelancer or an offshore body shop is the cheaper, right call. For anything with a back end, auth, AI, or that simply has to pass Web Store review the first time and stay working, a specialist extension studio is usually cheaper overall — MV3's service-worker lifecycle and the review process are where generalists lose weeks. Hire a company that can point to a live extension it still maintains.
A genuinely simple extension — one job, one browser, no server — starts around $1k. Full-featured extensions with accounts, a back end, synced data, or AI start at $5k and climb with how much server sits behind them. Migrating or rescuing a broken or Manifest V2 extension is priced case by case. Budget separately for maintenance, since an extension is software on a platform that keeps changing, not a one-time deliverable.
That's the abandon trap, and it's expensive. Chrome ships updates, the sites your extension touches get redesigned and break your selectors, and MV3 policy keeps tightening. An unmaintained extension tends to fail silently for a share of users after the next platform change, and rescuing abandoned code can cost more than building it right. Hire a company that expects to maintain it and puts a retainer or paid-fix plan in the proposal rather than treating launch as the finish line.
A software studio that ships and maintains its own products — KeepChats, Gwora and Cairn — and builds the same way for clients. Founded and led by codewithumar.
Talk to the studio →Send the problem. You get one fixed number and a plan back within a business day.
We build software worth keeping — for clients, and for ourselves.
Founded & led by codewithumar