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.
The shipping evidence to demand
"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 |
A shipping-evidence checklist for a Chrome extension company. Ask for the left column; accept nothing vaguer than the middle.
In-house extension studio vs generalist agency vs offshore body shop
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 |
How the three company types compare on what decides whether an extension actually ships and stays shipped.
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.
Red flags that predict an abandoned extension
Most extension projects that stall showed the warning signs in the first call. Slow down when you hear these from a company:
- A firm price before they ask what permissions you need. Permissions are the biggest driver of cost and review risk. A number quoted before that question is a number that will change.
- No live extension they'll point you to. A company that ships has something running you can install today. Portfolio thumbnails for extensions no longer in the store are a tell.
- They still talk in Manifest V2 terms — persistent background pages, blocking webRequest, loading scripts from a CDN. That knowledge is out of date and the store will reject it.
- Maintenance never comes up. An extension is software on a platform that keeps moving. If upkeep isn't in the proposal, you're buying a launch that will quietly rot.
- They promise all four browsers on day one. Firefox and Safari are near-separate projects. Eagerness to build them all before you have a single user optimises for scope, not your outcome.
Why hire Duskel
We build Manifest V3 extensions, and — the part that matters — we run two of our own in the Web Store. Redkit is our Reddit power-suite; Upwora 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."